Appearance
Working with the Sales Platform β
MyChatBot has two platforms that are stronger together. Understanding who does what is the key to wiring them up.
| Sales Platform | Agents Platform | |
|---|---|---|
| Role | Your front office | Your back office |
| What it does | Always-on sales assistants that hold customer conversations across channels (WhatsApp, Telegram, Instagram, web widgetβ¦), qualify leads, move them through pipelines, and run follow-ups | Agents that do open-ended work β and that can build, operate, and report on your Sales Platform |
| Who it talks to | Your customers | You (and, on your behalf, the Sales Platform) |
The short version: an Agents-Platform agent is the operator β it sets things up, kicks off campaigns, and pulls reports. The Sales Platform is the runtime β it holds the ongoing customer conversations and keeps chasing leads. You drive from Agents; the Sales Platform does the always-on customer work.
The three ways they connect β
| Connection | What it lets an agent do | Turn it on |
|---|---|---|
| Sales Platform capability | Operate your Sales Platform β create & configure sales assistants, connect channels, build pipelines, manage leads, trigger outreach, read chats | Enable the Sales Platform tool on an agent (the Sales Platform Wizard has it by default) |
| Sales-Platform knowledge as agent knowledge | Read your live FAQ, product catalog, feed, spreadsheet, and business documents β the same content your sales assistant uses | Attach them under the agent's Knowledge β From your sales platform, then turn on Business knowledge |
| Shared product search | Look up products from the same catalog your sales assistant searches | Attach the product source as knowledge (above) β see How search works |
Start with the Sales Platform Wizard
Your workspace ships with a Sales Platform Wizard agent built for exactly this. Open its Tasks tab and you'll find ready-to-run cards β Create my first AI sales agent, Connect WhatsApp to a sales agent, Build a sales pipeline, Index my product catalog, Schedule a follow-up automation, and more. Run one and it walks you through the setup in plain language.
Scenario 1 β Stand up a sales assistant from a chat β
Instead of clicking through setup screens, describe your business to an agent and let it configure the Sales Platform for you.
- Open the Sales Platform Wizard and run Create my first AI sales agent.
- It asks what you sell and who your customers are, then writes the sales assistant's instructions for you using sales best practices.
- Run Connect WhatsApp to a sales agent (or another channel) to put it live.
- Run Index my product catalog and Add an FAQ entry so it can answer product and policy questions.
- Run Build a sales pipeline to give it stages to move leads through.
You now have a live, customer-facing sales assistant β built entirely from chat.
Scenario 2 β Kick off outreach, hand the conversation over β
This is the classic hand-off: an agent starts the conversation, the Sales Platform runs it.
- From an agent with the Sales Platform capability, trigger a one-off outreach message to a lead (or preview an audience and send a small campaign).
- The sales assistant sends the first message on the channel.
- The customer replies β and the sales assistant takes over: it answers questions from your catalog and FAQ, qualifies the lead, and moves it along the pipeline.
- If the lead goes quiet, a follow-up automation chases them β e.g. "if a lead in the Contacted stage hasn't replied in 3 days, send a check-in." (Set this up once with the Wizard's Schedule a follow-up automation task.)
You triggered one message; the Sales Platform handled the entire back-and-forth and the follow-ups on its own.
Where the reply shows up
The customer's reply and the whole conversation live on the Sales Platform (in Leads / Active chats), on whatever channel they came in on β not in the agent's chat. The agent's job was to start it and, if you like, report on it later (Scenario 4).
Scenario 3 β One source of product truth β
Build your product catalog and FAQ once, on the Sales Platform, and use it everywhere.
- Your customer-facing sales assistant already searches it.
- Attach the same sources to your Agents-Platform agents (Knowledge β From your sales platform) so an internal research or content agent answers from the exact same live catalog β no second copy to maintain.
Update the catalog once and every agent, on both platforms, reflects it on the next answer. See Knowledge bases and How search works.
Scenario 4 β A scheduled ops digest β
Point a scheduled agent at your Sales Platform to run your morning review for you.
- Give an agent the Sales Platform capability and a schedule (e.g. every weekday at 9am β see Tasks & schedules).
- Each morning it summarizes recent customer chats, reviews your pipelines and stages, and flags leads that went quiet.
- It posts the digest into a conversation β and can draft follow-ups for your review before anything goes out.
The Wizard's Summarize recent customer chats, Review my pipelines and stages, and Find leads matching a filter tasks are good starting points to schedule.
Which platform for which job β
Rule of thumb
- Ongoing customer conversations, across channels, day and night β Sales Platform.
- Setup, one-off triggers, reporting, content, and any open-ended work β Agents Platform (which can reach into the Sales Platform to do it).
- Product & FAQ knowledge β build it once on the Sales Platform, reuse on both.
See also β
- Custom connectors β the Sales Platform capability and the per-domain connectors an agent can use
- Knowledge bases β attaching your Sales-Platform FAQ/catalog as agent knowledge
- Tasks & schedules β running ops agents on a cadence and scheduling follow-ups
- Best practices & agent design β keep each agent focused; use delegation and teams
- Sales Platform β the customer-facing side