--- url: 'https://docs.mychatbot.app/sales.md' description: >- The customer-conversation and CRM runtime: configure it with Claude or Codex, then orchestrate higher-level repeatable work from Agents Platform routines. --- # Sales Platform The Sales Platform is the **customer-conversation and CRM runtime**. Its assistants answer customers across channels, use your product catalog, maintain client and pipeline state, and run native follow-ups. Customer chats stay here even when an Agents routine reads or changes the surrounding Sales records. For a non-trivial setup, use Claude Code or Codex with the account-scoped **Sales-Management MCP**. The coding agent can inspect and configure assistants, clients, channels, CRM resources, knowledge, outreach, orders, and related primitives while you review changes. Use the app for credentials, OAuth, direct inspection, and small manual edits. When the same higher-level process must run repeatedly, promote it to an [Agents Platform routine](/agents/operating-model). The routine executes on MyChatBot and reaches Sales through the enabled Sales tools of its agents; Claude or Codex does not stay in the production loop. ## Configuration and runtime flow ```text Claude / Codex + Sales-Management MCP → configure and test Sales primitives Claude / Codex + Agents MCP → build and preview the routine Validated, disabled routine → review and activate Agents Platform routine → orchestrates through Sales tools Sales Platform → owns customer conversations and CRM state ``` Start with the [MCP surface map](/agents/mcp-overview), then follow [Build routines with Claude or Codex](/guides/build-routines-with-claude) for the copilot-to-autopilot promotion path. ## What's in it | Area | What it does | Start here | |---|---|---| | **Inventory & Product Search** | Load your catalog and make the assistant find the exact item a customer asks for — by description, attributes, or a photo. | [How search works](/search/) | | **Channels** | Meet customers where they are: Website Widget, WhatsApp, Telegram, Instagram, TikTok, Facebook, Viber, Gmail, and more. | [Channels](/channels/) | | **CRM & Integrations** | Sync leads, contacts, and orders into your CRM (KeyCRM, Bitrix24, Salesforce, HubSpot, Zoho, and others) and connect the tools your team already uses. | [Integrations overview](/integrations/overview) | | **Lead Processing** | Organize and act on leads with labels, pipeline statuses, and automated follow-ups. | [Labels & statuses](/integrations/labels-and-statuses) | | **Team & notifications** | Roles and the permission matrix, per-operator Access scope, automatic manager assignment, and every alert path — bell, push, Telegram, email. | [Team & access](/sales/team-and-access), [Notifications](/sales/notifications) | | **Balance & plans** | What an AI message is, what is charged, what happens at zero balance, and how assistants come back. | [Balance & billing](/sales/balance-and-billing) | | **Catalog & orders** | Products with stock and marketplace feeds; orders that reserve and ship that stock. | [Products catalog](/sales/products), [Orders](/sales/orders) | | **When something is off** | Symptom-first checklists for silent assistants, follow-ups that never fired, failed outreach, and numbers that disagree. | [Sales troubleshooting](/sales/troubleshooting) | ## A typical setup 1. **Connect Claude or Codex** to the narrowest Sales-Management MCP area that covers the setup; use the combined surface only when the work crosses several domains. 2. **Inspect before changing** existing assistants, channels, knowledge, and CRM state. 3. **Connect a channel** so customers can reach the assistant → [Channels](/channels/). 4. **Load your product catalog** so it can answer product questions → [Getting inventory in](/search/getting-inventory-in). 5. **Connect your CRM** so conversations turn into tracked leads → [Integrations](/integrations/overview). 6. **Set up native follow-ups** for per-lead customer-conversation behavior → [Follow-ups](/integrations/follow-ups). 7. **Build an Agents routine** only for the higher-level process that must run repeatedly across records or systems. ::: tip Where this happens Claude or Codex is the primary configuration workspace for complex systems. The app remains the authority and is required for secret entry, OAuth consent, visual review, and small manual changes: channels under **Channels**, product knowledge under **Knowledge base**, and CRM/app connections under **Integrations**. ::: ::: warning Sales events do not start Agents routines today There is no native Sales Platform → Agents Platform event bridge yet. A customer reply, new Sales chat, lead-stage change, or Sales order does not fire an Agents trigger. For that feedback loop, run a scheduled routine that reads paginated changes and tracks a cursor or high-water mark. Supported external apps and secret webhooks can still trigger routines directly. See [Feedback loops today](/agents/operating-model#feedback-loops-today). ::: ## See also * [Agents Platform](/agents/) — build custom agents for open-ended work. * [Agents Platform operating model](/agents/operating-model) — platform ownership and the routine-first production flow. * [MCP surface map](/agents/mcp-overview) — connect Claude or Codex to Agents and Sales configuration surfaces. * [Working with the Sales Platform](/agents/with-sales-platform) — how agents build, operate, and report on your Sales Platform (with scenarios). * [Cheat sheets](/cheat-sheets) — quick references for every area.