Before → after: amoCRM and Kommo set up with one message
Each example is a typical picture people bring to Kai: one pipeline for everything, fields in notes, tasks from memory. Below: the message people write to Kai, what it does in the CRM and the result. No client numbers here, only the configuration and the time.
amoCRMDental clinic
Half of the requests were lost between the call and the booking
One “Main” pipeline for everything: website, Instagram and phone requests land in “New”, then “In progress” and “Closed”. The doctor and the visit date live in notes, nobody reminds about the visit.
Before
Pipeline stages
New→In progress→Closed
Deal fields
- no fields — everything in notes
Rules
- no rules — everything from memory
What was breaking
- no “Reached” stage — unclear who was called back
- visit date in a note, the front desk searches by eye
- visits are not confirmed — patients do not show up
After
Pipeline stages
Request→Reached→Booked→Visit confirmed→Appointment→Treatment plan
Deal fields
- Servicelist
- Doctor
- Visit daterequired at “Booked”
- Plan amountnumber
Rules
New requesttask “call back” in 15 minutesMoved to “Booked”task the day before: confirm the visit“Reached” idle for 2 daystask “call again”
What changed
- every request gets a call in the first 15 minutes — a rule, not the front desk’s memory
- the visit date cannot be skipped: without it the deal will not move to “Booked”
- a confirmation task appears the day before — fewer no-shows
Message to KaiCreate a “New patients” pipeline: Request → Reached → Booked → Visit confirmed → Appointment → Treatment plan. Deal fields: Service (list: therapy, prosthetics, implants, pediatric), Doctor, Visit date, Plan amount. Visit date is required at the “Booked” stage. Rules: new request — task for the front desk to call back within 15 minutes; deal moved to “Booked” — task the day before to confirm the visit; no movement in “Reached” for 2 days — task “call again”.
KaiDone. “New patients” pipeline created, 6 stages. Added 4 fields, “Visit date” is required at “Booked”. Three rules are on: call back within 15 minutes, confirm the visit the day before, call again after 2 days. System stages “Won” and “Lost” untouched.
What Kai did
create pipelinecreate field ×4make field requiredcreate rule ×3
One message, about two minutes. An integrator does the same in 2–5 business days.
KommoReal estate agency
Budget and district were typed into the deal name
All leads in “Incoming”, no stages. Budget, district and property type typed into the deal name: “John, 2BR, up to 90k, downtown”. A selection is sent and forgotten, nobody follows up after a viewing.
Before
Pipeline stages
Incoming→Working→Deal
Deal fields
- no fields — everything in notes
Rules
- no rules — everything from memory
What was breaking
- no filtering by budget or district — everything is text
- deals stall after a viewing with no next step
- no loss reasons — unclear why buyers leave
After
Pipeline stages
Request→Qualification→Selection→Viewing→Reservation→Contract
Deal fields
- Property typelist
- Budgetnumber · required at “Qualification”
- Districtrequired at “Qualification”
- Payment methodlist
Rules
New requesttask “call back” in 15 minutesMoved to “Selection”task for tomorrow: schedule a viewing“Viewing” idle for 3 daystask “ask for the decision”
What changed
- filter “2BR up to 90,000 downtown” in a second, by fields
- every viewing gets a next step and a deadline
- losses with reasons: you see where you lose — price or speed
Message to KaiIn Kommo create a “Buyers” pipeline: Request → Qualification → Selection → Viewing → Reservation → Contract. Fields: Property type (list: studio, 1BR, 2BR, 3BR+, house), Budget (number), District, Payment method (mortgage, cash, instalments). Budget and District are required at “Qualification”. Rules: new request — task to call back within 15 minutes; deal in “Selection” — task for tomorrow to schedule a viewing; no movement after “Viewing” for 3 days — task “ask for the decision”. Loss reasons: bought elsewhere, too expensive, changed mind, no answer.
KaiDone. “Buyers” pipeline, 6 stages. Fields: Property type, Budget, District, Payment method; Budget and District are required at “Qualification”. Three rules are on, four loss reasons added — loss analytics will now count.
What Kai did
create pipelinecreate field ×4make field required ×2create rule ×3loss reasons
One message, about two minutes. Fields, stages and rules go into Kommo via the API, no widgets.
amoCRMApartment renovation
The pipeline existed, but deals sat in “Measurement” for months
The “Contract sale” pipeline was set up long ago, but estimates go out when someone remembers, amounts are empty, no loss reasons — the pipeline report is blank. The owner cannot see where the money is stuck.
Before
Pipeline stages
Request→Qualification→Measurement→Estimate→Contract→Deposit
Deal fields
- Work type
- Area, m²
- Budget
- Estimate amountempty in 8 of 10 deals
Rules
- no rules — everything from memory
What was breaking
- 23 deals idle for over two weeks in “Measurement”
- estimate amount empty — revenue forecast impossible
- without loss reasons you cannot tell why clients leave
After
Pipeline stages
Request→Qualification→Measurement→Estimate→Contract→Deposit
Deal fields
- Work type
- Area, m²
- Budget
- Estimate amountrequired at “Estimate”
Rules
“Measurement” idle for 5 daystask for the foreman “send the estimate”
What changed
- estimates no longer stall: after 5 days a task with an owner appears
- estimate amount is required — the revenue forecast is computed from fields
- losses with reasons, a dashboard any time with one word: “dashboard”
Message to KaiAudit the “Contract sale” pipeline. Then fix it: make “Estimate amount” required at the “Estimate” stage, add loss reasons (too expensive, chose others, postponed, no answer), rule: no movement in “Measurement” for 5 days — task for the foreman “send the estimate”. And show me the pipeline dashboard.
KaiAudit: 23 deals have been in “Measurement” for over 14 days, “Estimate amount” is empty in 80% of deals, no loss reasons, no automations. Fixed: the field is required at “Estimate”, 4 loss reasons added, the 5-day rule is on. Dashboard: 61 open, 23 in “Measurement” (bottleneck), 9 won this month, 4 lost.
What Kai did
pipeline auditmake field requiredloss reasonscreate ruledashboard
Audit, fixes and summary — one message. Kai deleted nothing: existing deals and stages stayed.
KommoOnline school
Registrations lived in a spreadsheet, price deadlines were reminded from memory
Landing-page registrations land in a spreadsheet, managers sort them by hand. Cohorts get mixed up, an invoice is sent — and the reminder is forgotten. The team learns about a payment from accounting a day later.
Before
Pipeline stages
Lead→Payment
Deal fields
- no fields — everything in notes
Rules
- no rules — everything from memory
What was breaking
- nothing between “Lead” and “Payment” — unclear who is at which step
- no Product and Cohort fields — lists are compiled by hand
- payments are noticed late, the welcome and access are delayed
After
Pipeline stages
Registration→Qualification→Call scheduled→Call done→Invoice sent→Payment
Deal fields
- Productlist
- Planlist
- Cohort
- Instalmentsyes/no
Rules
Registrationtask: write and offer a diagnostic call“Invoice sent”task for tomorrow: remind about the price deadline“Payment”tag “student” + Telegram notification
What changed
- every registration gets a first touch — the task is created automatically
- the price-deadline reminder is scheduled the next day by itself
- the team sees the payment at once, in Telegram, without accounting
Message to KaiIn Kommo create a “Course sales” pipeline: Registration → Qualification → Call scheduled → Call done → Invoice sent → Payment. Fields: Product (list), Plan (list: basic, with mentor, VIP), Cohort, Instalments (yes/no). Rules: Registration — task to write and offer a diagnostic call; “Invoice sent” — task for tomorrow to remind about the price deadline; “Payment” — tag “student” and a Telegram notification to the sales team.
KaiDone. “Course sales” pipeline, 6 stages, 4 fields. Rules are on: a task on registration, a deadline reminder the day after the invoice, the “student” tag and a Telegram notification on payment. Colleagues subscribe to notifications with a link from the account page.
What Kai did
create pipelinecreate field ×4create rule ×3tag
One message. Telegram notifications are built into Kai, no Zapier or webhooks.
Step-by-step amoCRM and Kommo guides →