An AI agent that keeps your Kommo deals up to date

What the Kommo connection does

Kommo is a messaging-first CRM, and every chat that turns into a sale still needs a deal, a contact and the right pipeline stage. The native Kommo integration lets your MyChatBot agent do that work: while it talks to a customer, it creates and updates Deals and Contacts in your Kommo account, with no manual data entry.

The connection is set up per assistant. You link an agent to your Kommo domain with a long-lived API token, then decide in Entities & Data Fields Configuration what it may touch: deals (Use Deals), which standard and custom fields, and which Deals Pipeline new deals land in. Fields you leave off are never changed.

Sync statuses pulls your Kommo stages into the agent’s pipeline in MyChatBot, so the agent uses real stage names, and those statuses can drive labels and statuses and follow-ups.

What the AI agent does inside Kommo

Once fields are applied, the agent gets two tools and calls them based on your plain-language instructions.

edit_crm_deal: create or update a deal

• full_name (the contact name) is required; phone and price are optional, together with Status and any custom fields you enabled.
• A contact is found or created automatically from the phone number and linked to the deal.
• The deal is created in the pipeline you selected, and the agent moves it through your stages by updating Status.
• MyChatBot keeps the deal tied to the conversation and the order.

add_crm_client_contact: add or update a contact

• full_name and phone are both required, plus any other fields you enabled.
• If a deal already exists for that client, it is linked to the contact, and the client details in MyChatBot are updated too.

Fields the integration fills for you

• Source is set to AI- plus your assistant’s name, so you can filter the deals your AI created.
• Chat Link is added as a comment on each deal and opens the conversation that produced it.
• Status must match a stage in your Kommo pipeline exactly.

Which channels feed your Kommo pipeline

Any customer channel connected to the same Sales Platform assistant can end in a Kommo deal:

• Messaging: WhatsApp Business, personal WhatsApp, Telegram bot and Telegram account, Viber bot and E-Chat Viber.
• Social: Instagram DMs and comments, Facebook Messenger, TikTok.
• Web, email and text: the website widget, Gmail, SMS through Twilio or Quo, and OLX buyer chats.
• Voice and custom systems: AI calls and the Webhooks API.

Kommo contacts are found or created by phone number. If a conversation has not yet given you the customer’s phone, tell the agent to ask for one before it creates the deal.

From first message to Kommo deal: an example

A typical conversation with instructions based on the docs examples. Stage names are illustrative; yours must exist in your Kommo funnel.

1. A customer writes in Instagram DMs asking about one of your services. The agent answers from your knowledge base and asks a qualifying question.
2. The customer shows interest and shares a name and phone number. Following the instruction to create a deal when a customer expresses interest, the agent calls edit_crm_deal with full_name, phone, the quoted price and the status New.
3. Kommo now holds a deal in the selected pipeline, linked to a contact found or created by that phone, with Source set to AI- plus the assistant name and a Chat Link comment.
4. The customer asks for a call back tomorrow morning. The agent updates the deal to Callback Requested and adds the preferred time to the comments.
5. A manager takes over. They open the Chat Link from the deal and step in; depending on the mode set in Handoff Control, an operator reply or the stop word switches the chat to operator mode.
6. The outcome is recorded. If the customer pays, the agent moves the deal to Closed Won and sets the amount to the final purchase value; if they decline, it moves the deal to Closed Lost with the reason in the comments.

Set it up in four steps

1. Create an integration in Kommo. As an administrator, open Settings, click Create Integration, enter the Redirect URI and name from the guide, upload the widget.zip file, then click Generate long-lived token and select a 5-year expiry.
2. Connect Kommo in MyChatBot. Open Integrations, pick the agent, find Kommo CRM, click Connect, paste your Domain (for example your-company.kommo.com) and the token as API Key, then Submit.
3. Choose entities and fields. Turn on Use Deals, tick standard and custom fields, select the Deals Pipeline, click Apply fields and run Sync statuses.
4. Write the instructions. Say when to create or update a deal, change its status or add a contact, using real stage names.

Screenshots and ready-to-paste instruction examples are in the Kommo setup guide and in the Kommo integration docs. For the other CRMs we support, see CRM sync.

Requirements and limits

• Plan. Kommo is listed among the CRM and ERP integrations of the Pro plan and higher on the pricing page. On the Standard plan, CRM cards show PRO and cannot be connected.
• Kommo access. Creating the integration and the long-lived token requires administrator access to your Kommo account.
• One CRM per assistant. Once Kommo shows Connected, the other CRMs gray out for that assistant. Another assistant can reuse the connection as its own copy.
• Exact status names. The agent can only set statuses that exist in your Kommo funnel. Run Sync statuses after every pipeline change; sync matches stages by name.
• One-way stage import. Sync statuses copies stages into MyChatBot and changes nothing in Kommo. Dragging a card on the MyChatBot Leads board does not move the deal in Kommo; the deal stage changes when the agent updates it.
• Test on purpose. In the Test Dialog, status and label changes are simulated, but writes to a connected system run for real, so test deals can reach Kommo.