Solutions overview
Choose a core Sales, Support, or Marketing system, or open a small blueprint for a repeated implementation request.
Choose the system or small deliverable you want to ship.
Start with Sales, Support, or Marketing for a full operating system. Use Quick blueprints when the request is specific and should be repeatable without another implementation call.
Deals pipeline with Lead, In Progress, Won, and Lost stages, amounts, people, companies, and stage totals
Tickets pipeline with New, On You, On Customer, On Hold, and Closed support states
Channels page with WhatsApp connected plus Instagram and Messenger connection paths
Business system Max state · Tasks automation for Pre-Meeting Brief with schedule, Email, and WhatsApp channels enabled
Quick blueprint knowledge state · Agent settings with knowledge base controls for FAQ answers
Quick blueprint tool state · Create tool form for an external payment-link actionSummary
Choose a core Sales, Support, or Marketing system, or open a small blueprint for a repeated implementation request.
Concepts covered
Step breakdown
- Choose the requestStart with the thing the team needs working: sales pipeline, support answers, marketing capture, payment reminders, FAQ handling, or payment links.
- Open the matching blueprintUse the page that names the required agent, workflow, channel, CRM context, tool, owner, and verification step.
- Ship the narrow versionCreate one working path first, test it in the product, and expand only after the output is trustworthy.
Choose by the request
If the request is broad, start with Sales, Support, or Marketing. If the request is specific, use a Quick blueprint.
The goal is to leave with something working: an automation, an agent, a tool, or a workflow that can be verified in the product.
Core systems
Sales: one AI SDR system that can capture a lead, qualify it, and hand off a visible next step.
Support: one support operation that can receive a customer message, use context, route or escalate, and leave evidence.
Marketing: one capture-and-follow-up system that turns a signal into a segment, record, workflow, or owner task.
Quick blueprints
Use quick blueprints when the request is specific: send a payment reminder, answer FAQs with an agent, create a payment link, create a task, or connect a tool.
Each quick blueprint should name the exact product surfaces to open, the minimum fields to configure, a usable prompt or workflow shape, and the final state to verify.
How to route daily questions
When someone asks for a common implementation, send the matching blueprint first. If the request is broader, send the Sales, Support, or Marketing system page.
If a question repeats more than twice in operations, turn it into a quick blueprint with screenshots, required fields, and the smallest working version.
How to use the section
Build the smallest useful version first: one channel, one workflow or agent, one owner, one record or table, one way to verify the result.
Then expand only after the team can see the output in CRM, Max Activity, the workflow logs, or the customer channel.
Transcript
Open searchable transcript
FAQs
What is Solutions overview?
It is the routing page for implementation questions. Pick Sales, Support, Marketing, or a quick blueprint and build the smallest working version.
Why are there fewer sidebar items now?
The sidebar highlights deliverables people are most likely to ask operations or implementation for. Supporting ideas belong inside those blueprints or product tutorials.
How should I choose a blueprint?
Choose by the result you need this week: pipeline, support resolution, demand capture, payment reminders, FAQ answers, or payment links.