An AI agent that writes leads and orders into KeyCRM

What the KeyCRM connection does

The MyChatBot integration links one of your sales assistants to your KeyCRM account, so CRM work happens inside the conversation, not after it. When a customer shows interest, confirms a purchase or shares a phone number, the assistant writes the record itself.

The connection is authorised with a KeyCRM API key that an administrator creates under Settings → General. In MyChatBot you paste it as the Access Token, then decide which entities and fields the assistant may use. KeyCRM works with three entity types: Leads (potential sales), Orders (sales in progress) and Contacts (client details).

Three fields are handled for you. Status maps to a stage in your KeyCRM pipeline. Source is set to the channel the chat came from, such as Telegram or WhatsApp, or to AI if no channel is specified. Chat Link is added to every lead and order and stored in the manager comment field.

What the AI agent does inside KeyCRM

After connecting, the assistant gets four tools. Every field you tick in Entities & Data Fields Configuration becomes something it can fill in.

• create_crm_lead (Create a lead): full_name (required), phone, Status and your custom fields. A contact is created or found by phone number, the lead is linked to it, and the chat link and source are added.
• edit_crm_lead (Update a lead): updates the name, phone, Status or custom fields on the client’s existing lead, keeping the chat link and source.
• create_crm_deal (Create an order): full_name and phone (both required), shipping with shipping_address_city and shipping_receive_point (required), and products, each with sku, name, price and quantity (required), plus custom fields. Products are matched to existing ones or created, and MyChatBot keeps its own record of the order in sync.
• add_crm_client_contact (Add or update a contact): full_name and phone, both required. An existing lead, the MyChatBot client card and related orders are updated too.

Instructions do not need tool names: describe in plain language when to create a lead and which status to set. With the optional KeyCRM Products panel on, your catalog is imported and indexed so the assistant can recommend products in the chat, with Agentic Search for complex product discoveries.

Which channels feed KeyCRM

Integrations are set per assistant, so every channel connected to it can produce KeyCRM leads and orders: the website widget, WhatsApp Business or a linked personal number, a Telegram bot or Telegram account, Instagram DMs and comments, Facebook Messenger, TikTok, Viber, Gmail, SMS, OLX buyer chats and the Webhooks API.

Because the Source field carries the channel name, KeyCRM shows which messenger each lead came from. For AI phone calls, the Calls channel supports Post-Call Functions, actions such as writing a lead to your CRM after the call. They add a small fixed charge to each call that actually runs them.

Example: from first message to a KeyCRM order

Assuming Use Leads and Use Deals are on, the KeyCRM Products panel is enabled and your instructions cover leads and orders, a typical chat runs like this.

1. A customer writes to your Telegram bot and asks whether a jacket is available in their size. The assistant searches the KeyCRM Products catalog and suggests matching options.
2. The customer shares a name and phone number. The assistant calls create_crm_lead with full_name, phone and the Status from your instructions, for example New if that stage exists in KeyCRM. The contact is found or created by phone, Source is set to Telegram and the chat link goes into the manager comment.
3. The customer decides to buy, and edit_crm_lead moves the lead to the matching stage.
4. The purchase is confirmed. The assistant collects the delivery city and the branch or address for pickup, then calls create_crm_deal with shipping_address_city, shipping_receive_point and the product line: sku, name, price and quantity.
5. The order lands on the contact with its shipping details, and a manager follows the chat link to read the whole conversation.

If the chat needs a person at any step, Handoff Control lets an operator take over by typing a stop word or, with implicit handoff, simply by replying. With Silent handoff on, the client is not notified about the switch.

Setup in four steps

1. In KeyCRM, log in as an administrator, open Settings → General, click Create New API Key and then Save.
2. In MyChatBot, open Integrations, pick the assistant in the header dropdown, find KeyCRM and click Connect.
3. Paste the key as the Access Token and click Submit. The KeyCRM card now shows Connected for that assistant.
4. In Entities & Data Fields Configuration, turn on Use Leads and/or Use Deals, tick the standard and custom fields, choose the pipeline for new leads and click Apply fields. Then click Sync statuses to pull your funnel stages.

Then add plain-language rules to the instructions, send a test message with contact details and check that the lead appears in KeyCRM. The KeyCRM integration guide walks through each screen.

Requirements and limits

• Plan. KeyCRM is one of the CRM and ERP integrations on the Pro plan ($99 a month, or $89 a month billed annually) and the plans above it. On Standard, or without an active plan, the card shows PRO and cannot be selected.
• Statuses must match exactly. The Status value must match a KeyCRM status character for character. After you change pipelines or stages in KeyCRM, click Sync statuses again, or creating and updating leads will fail to set the stage.
• Stage lists sync one way. Sync statuses copies stages into MyChatBot and changes nothing in KeyCRM. Dragging a card on the Leads board does not move the lead in KeyCRM; only the agent’s updates through the integration do.
• One CRM per assistant. While KeyCRM is connected, other CRM systems are greyed out for that assistant. Other assistants can copy the connection without re-entering the key.
• Admin access. A KeyCRM administrator must create the API key.