Kommo AI agent, Copilot, Salesbot or Kai: which one you need
Kommo's built-in AI agent and Copilot answer customers in chats and assist managers in the lead card; Salesbot and the Digital Pipeline click together automations; Albato, Make and n8n move data between apps; Wazzup and Umnico bring messengers into the CRM. None of them builds a pipeline, fields and automations from a description of your business: that takes you by hand, a partner over 3–5 weeks, or Kai from one chat message.
TL;DR
- Kommo AI agent needs Advanced or higher and spends AI credits per reply; it talks to customers, it does not configure the CRM.
- Copilot is on every plan, including Base: answers Kommo questions, suggests values for empty fields, summarises chats.
- Salesbot and 12 Digital Pipeline triggers (task, tag, stage change, webhook, field change…) are included under Leads → Automate.
- Partner: typically 3–5 weeks (in Russia, 150–400k RUB is a common quote). Kai: from €29/month, 3 free days, no card, a full pipeline in one conversation.
- Kai runs 60+ actions via the Kommo and amoCRM APIs: pipelines, fields, automations, integrations, self-healing audit, lead scoring, PDF spec.
What each tool actually does
Kommo AI agent is a virtual employee for chats, created under AI agents → AI agent list → Add a new agent, with tabs for knowledge sources, products, up to 20 actions (Set field, stage changes…) and persona. It replies 24/7, qualifies leads, books appointments. Advanced or higher; each reply spends AI credits.
Kommo Copilot is an in-app helper: answers "how do I do this in Kommo", fills empty fields from chats, writes summaries and draft replies. It assists; it does not build pipelines.
Salesbot and the Digital Pipeline are the native no-code builder: bots from blocks, triggers on stages. No extra cost, but six stages with five automations is an evening's work.
Albato, ApiX-Drive, Make, Zapier, n8n move data between Kommo, your website, spreadsheets and ad accounts. No CRM structure; pricing usually scales with operations, n8n can be self-hosted.
Wazzup, Umnico are chat hubs: they connect WhatsApp, Telegram and Instagram and drop conversations into the lead card, nothing more.
Kai configures the CRM from a message. Describe the business in the Telegram bot @aiicrm_bot or the web chat; Kai asks clarifying questions, agrees a plan and applies it via the API: pipelines, fields with per-stage required rules, automations, integrations, audit, lead scoring, PDF spec. Kommo connects via a Marketplace widget in one click, no keys.
An implementation partner does the same by hand and trains the team: worth it for unusual processes or a person on call.
Task by task: who covers what
| Task | Kommo AI agent / Copilot | Salesbot + Digital Pipeline | Albato / Make / n8n | Wazzup / Umnico | Kai |
|---|---|---|---|---|---|
| Pipeline and stages | No (AI agent only moves leads between stages) | No, built by hand | No | No | Yes, from a business description |
| Custom fields and required rules | Copilot suggests values, no field creation | No | Fills existing fields | No | Yes, with types and per-stage rules |
| In-CRM automations | AI agent: up to 20 actions in chat | Yes, by clicking on stages | Partly, via API | No | Yes: trigger → task, tag, stage, notification |
| External integrations | A limited list | Webhook, email | Yes, hundreds of apps | Messengers only | Telegram, Slack, Discord, Sheets, webhook |
| Pipeline analytics | AI analyst on Pro | Standard Kommo reports | Export to BI | Chat statistics | Stage conversion, drop-off, 24/7 audit |
Step by step: the manual way and the Kai way
UI paths follow the official Kommo help centre.
Step 1. Pipeline and stages
Manual Leads → "⋯" menu top right → Edit pipeline → Add stage → Save. Closed-won and Closed-lost can be renamed, not deleted.
Kai One message creates the pipeline, a field, an automation and an integration:
Set up a pipeline for a renovation studio: Inquiry → Site visit → Estimate → Contract → Work → Payment. Make the number field "Area, m²" required from Estimate. If a lead sits in Site visit over 3 days, task the owner and tag it "overdue". When a lead moves to Contract, post to the sales team's Telegram chat.
Step 2. Fields and required rules
Manual Open any lead → Setup tab → + Add field → choose type and name. To make it mandatory, click Optional in the field settings and pick the stage it is required from → Save.
Kai "Add a number field 'Budget', required from Estimate." Kai checks for an existing similar field first.
Step 3. Automations
Manual Leads → Automate → "+" under the stage → pick a trigger (Add Task, Add Tags, Change Lead Stage, Send Webhook, Change Field, Send Email, Salesbot) and conditions. Bots: Settings → Communication tools → Salesbots → Create a new bot.
Kai In words: "If a lead has no open task for a day, create a 'Call back' task for the owner." Included from Pro.
Step 4. Integrations and chats
Manual Wazzup or Umnico install from the Kommo Marketplace and connect messengers to lead cards. Albato, Make or n8n need their own account and an "event in Kommo → action in app" scenario built step by step.
Kai "When a lead moves to Contract, post to Slack and add a row to Google Sheets." Telegram, Slack, Discord and Sheets are in Pro; a custom webhook is Max, €30 fixed. Kai is not a chat hub: messengers still come via Wazzup, Umnico or Kommo.
Step 5. Analytics
Manual Kommo's reports show conversion; where and why leads are lost, you work out by hand.
Kai "Show stage conversion for the last 30 days and the biggest drop-off." Plus a daily audit: leads without tasks, overdue stages, empty required fields, auto-fixed and reported in chat.
Cost and time: manual, partner, Kai
| Criterion | Manual | Implementation partner | Kai |
|---|---|---|---|
| Time to a working pipeline | An evening to a week | Typically 3–5 weeks | One conversation: plan, then API changes in minutes |
| Cost | Kommo plan plus your time | Region-dependent; in Russia 150–400k RUB is common | Start €29, Pro €59, Max €119/month; 3 free days, no card |
| Who learns your business | You | An analyst on calls | Kai asks questions and agrees a plan before changes |
| What you get | What you had time for | Pipeline, fields, bots, training, documentation | Pipeline, fields, automations, integrations, PDF spec, 24/7 audit |
| Best fit | 1–3 managers, simple process | Unusual processes, accounting/telephony links, a human on call | SMBs with standard or moderately complex processes |
FAQ
Does Kai replace the built-in Kommo AI agent?
No, they do different jobs: Kommo AI agent talks to customers in chats and qualifies leads; Kai configures the CRM itself: pipelines, fields, automations, integrations, analytics. Kai builds the pipeline, the AI agent handles conversations inside it.
Do I still need Albato, Make or n8n if I use Kai?
Not for common cases: on Pro, Kai itself connects lead events to Telegram, Slack, Discord and Google Sheets; on Max it builds a custom webhook for a fixed €30. Connectors win for long multi-step scenarios across many services.
What do I need to connect Kai to Kommo?
The Kai widget is in the Kommo Marketplace: one click via OAuth, no API keys. Then you talk to Kai in the Telegram bot @aiicrm_bot or the web chat; both share one account and history.
How much does Kai cost and is there a trial?
Start €29/month (about 100 requests, 1 CRM account), Pro €59/month (about 500 requests, up to 3 accounts, automations, standard integrations), Max €119/month (fair-use requests, up to 10 accounts, custom work at a fixed €30 each). First 3 days free, no card. Pay by card, Apple Pay, Google Pay, Telegram Stars or USDT.
Is it safe to give an assistant access to my CRM?
Access goes through OAuth, tokens are stored encrypted, and Kai does not keep your lead data. The company is registered in Poland (EU). Revoke access any time in Kommo's integration settings.
What if I use amoCRM instead of Kommo?
Same flow: the Kai widget is also in the amoCRM marketplace with one-click OAuth. amoCRM's built-in amoAI is Kommo's Copilot equivalent: it assists inside the interface but does not build a pipeline from a business description. Bitrix24 and custom CRMs with API docs work too.
What next
Describe your process in one message: Kai asks 3–5 questions, shows the plan and configures Kommo or amoCRM. First 3 days free, no card.