AI Assistants for amoCRM: What They Do, How to Choose (2026)
"AI assistant for amoCRM" means four different kinds of tools in 2026: the built-in amoAI (Copilot and AI agent on Kommo), which helps write replies and summarize chats; customer-facing chatbots; no-code connectors that move data between services; and setup assistants like Kai that build pipelines, fields and automations from a chat message. Pick the one that matches the job — selling in chats, wiring services together, or configuring the CRM itself — not the one with the biggest "AI" badge.
TL;DR
- amoAI and Kommo Copilot live inside conversations (summaries, suggested replies, text edits) and never touch CRM structure. amoAI needs the amoCRM "Профессиональный" or "Enterprise" plan; Copilot ships with Kommo plans from Base up.
- Chatbots (Salesbot, Salebot, ChatAI) talk to customers; no-code connectors (Albato, ApiX-Drive, Make, Zapier, n8n) move data. Neither designs your pipeline.
- Kai, a setup assistant, connects to amoCRM or Kommo in one click via OAuth and runs 60+ API actions: pipelines, fields, automations, integrations, analytics.
- Money: Kai from €29/month, 3-day free trial, no card; an integrator typically takes 3–5 weeks and, in Russia, 150–400k RUB; bots and connectors bill on their own plans.
- Decide on four things: OAuth access without API keys, what exactly the tool changes, whether there is a plan and report to roll back from, and how limits are counted.
The four kinds of "AI for amoCRM"
1. Built-in: amoAI, Kommo Copilot and AI agent
In amoCRM, amoAI is a button in the message composer: it rewrites text, fixes typos, changes tone, summarizes a thread into a note and suggests replies. Admins switch it on under Настройки → amoAI. On Kommo, Copilot writes lead summaries, suggests replies and offers to fill empty fields; the AI agent answers incoming customer messages and qualifies leads. None of them creates pipelines, fields or automations — they are helpers inside an already configured CRM.
2. Customer-facing chatbots
Salesbot inside amoCRM and Kommo, external Salebot and ChatAI, plus Wazzup and Umnico, which bring WhatsApp and Telegram chats into the CRM. Their job is to reply to customers, capture requests, follow a script and tag leads. Pipeline structure stays your problem.
3. No-code connectors
Albato, ApiX-Drive, Make, Zapier, n8n. Typical recipes: "website form → lead in amoCRM", "deal won → row in Google Sheets". Great for moving data, but you assemble every link by hand and they do not design the CRM.
4. Setup assistants
Kai works differently: you describe your business in a Telegram bot or web chat, it asks follow-up questions, agrees a plan, then creates pipelines, stages, fields, automations and integrations through the API and sends a report. It is a diagnosis, not a form — and it replaces the integrator on routine work, not your sales team.
How to choose
- Access. A good sign: installation from amoМаркет or Kommo Marketplace via OAuth, no API keys; tokens are encrypted and access is revoked in one click. A bad sign: being asked for your login and password.
- What it changes in the CRM. Ask directly: does the tool only read data, write to leads, or create structure (pipelines, fields, triggers)? The wider the permissions, the more the next point matters.
- Rollback and reporting. Every structural change should be listed: what was created, what was renamed. Kai agrees a plan before touching anything and reports afterwards; an integrator fixes scope in a spec; bots and connectors usually leave structure alone.
- Price and limits. Per request (Kai), per operation (connectors), per conversation (bots) or a one-off project (integrator). Compare the cost of the outcome, not the plan: a pipeline for €29 and one for 200k RUB are different amounts of work.
- Language and jurisdiction. Kai speaks English and Russian, understands voice messages, is run by a company registered in Poland (EU) and does not store your deal data.
Worked example: pipeline, required field, automation
By hand in amoCRM
- Сделки (Leads) → Настроить (Setup) → click the pipeline name in the top-left corner → add a new pipeline. Add stages with the "+" button, rename by clicking a stage.
- Open any lead card → Настроить → Добавить поле (Add field) → choose type and name; the same dialog makes the field required on specific stages.
- Сделки → Настроить → Digital Pipeline → on the needed stage add an action: create task, add tags, change stage, send webhook. Digital Pipeline needs the "Расширенный" plan or higher.
On Kommo: "…" in the top menu → Edit pipeline → Add stage → Save. Fields: Pipelines → All leads → + New lead → Setup tab → + Add field, with an option to mark it required on specific stages.
With Kai
- Install the Kai widget from amoМаркет or Kommo Marketplace and approve access via OAuth. No keys, no passwords.
- Send the bot one message:
Dental clinic, 2 front-desk admins. I need a "New patients" pipeline: Request → Consultation booked → Visited → Treatment plan → Paid. On "Consultation booked" the field "Visit date" must be required. If a lead sits 3 days without movement, create a task for the admin.
- Kai asks two or three clarifying questions, shows the plan, and after your "yes" creates the pipeline, field and trigger, then sends a report listing every change.
Comparison
| Tool | What it changes in the CRM | Access | Rollback and control | Price |
|---|---|---|---|---|
| amoAI / Kommo Copilot | Text, summaries, suggestions. No structural changes | Built in, enabled by an admin | Nothing to roll back | Included in the CRM plan ("Профессиональный", "Enterprise" on amoCRM) |
| Chatbots (Salesbot, Salebot, ChatAI) | Customer conversations, requests, tags | Built in or via API | You edit the script yourself | Bot subscription |
| No-code connectors (Albato, ApiX-Drive, Make, Zapier, n8n) | Move data between services | API key or the service's OAuth | You switch the link off | Subscription per operation |
| Setup assistant Kai | Pipelines, fields, automations, integrations, analytics | One-click OAuth, no keys | Plan before, report after | From €29/month, 3-day free trial |
| Integrator | Everything, including custom work | Usually admin access | Spec and sign-off | Typically 150–400k RUB, 3–5 weeks |
Honest limitations
- No AI knows your sales process better than you. Kai asks the questions, you supply the answers; if the process is vague, the pipeline comes out "average for the niche".
- Kai works through the public amoCRM API. Whatever the API does not expose (some permission settings, visual widgets) is done by hand or by an integrator; for non-standard requests there is a fixed €30 add-on.
- Request limits: ~100 per month on Start is enough to set up and adjust one account, not for daily chatting about everything.
- amoAI and Copilot depend on the CRM plan: on lower amoCRM plans amoAI is simply not there.
- Bots and connectors need upkeep: rename a stage and check that the link did not break.
FAQ
How is amoAI different from Kai?
amoAI helps inside conversations: summaries, suggested replies, text edits. Kai is a setup assistant: it creates pipelines, fields and automations through the API. They do not compete and can be used together.
Do I have to give the assistant my amoCRM login and password?
No. Kai connects through a widget in amoМаркет or Kommo Marketplace via OAuth; tokens are encrypted, and access is revoked from the installed-integrations tab of the marketplace.
Can I undo what the assistant did?
Kai shows the plan before changing anything and sends a report afterwards, so every action is known. There is no "undo all" button in amoCRM or Kommo: anything created is removed or renamed from the report, by hand or with a new Kai command.
Does a setup assistant replace an integrator?
For routine work — pipelines, fields, triggers, integrations with Telegram, Slack and Google Sheets — yes. Complex custom widgets, migrations and team training are still integrator work.
Does Kai work with Kommo and Bitrix24?
Yes. amoCRM and Kommo via marketplace widgets, Bitrix24 via an app, and a custom CRM from its API documentation with a sandbox to test in. One account and one history across Telegram and the web chat.
What does it cost?
Start — €29/month (~100 requests, 1 CRM account), Pro — €59/month (~500 requests, up to 3 accounts, automations), Max — €119/month (fair-use requests, up to 10 accounts, priority support). Non-standard customization is a fixed +€30. The first 3 days are free, no card; pay by card, Telegram Stars or USDT.
What next
Describe your business in two or three sentences and see what plan Kai proposes. Three days free, no card required.