If your operation sells via WhatsApp, Kommo CRM only reduces CAC (customer acquisition cost) when you design an operable funnel with SLA, Routing and Automatic follow-up. Without these three pillars, you’ll just “organize conversations” — and that doesn’t pay the bills. I’ve implemented Kommo in Brazil for years and the pattern is clear: when a company turns WhatsApp into a process (not just a seller’s habit), CAC drops because you lose fewer leads, respond faster, and convert more with the same team.
This post is a practical guide of what I do in the field to unlock ROI: where to adjust Kommo, what decisions to make, and especially, who this is for and Who it’s NOT for.
The “secret” to CAC on WhatsApp isn’t a pretty message. It’s time + distribution + consistency
CAC doesn’t drop with a “better script” if the basics are broken:
- First response time high (lead cools off and you pay for ads for nothing).
- Poor distribution (one seller overloaded, another idle; client waiting; opportunity dying).
- Inconsistent follow-up (depends on human discipline; discipline doesn’t scale).
Kommo is powerful because it’s not just a “registration” CRM. It allows you to combine funnel + chat + automation. But you need to design it like engineering: inputs, outputs, queues, exceptions, metrics.
If you want an overview of how Kommo works day-to-day, I’ve already detailed the basics here: How Kommo CRM works in practice: from lead to closing.
Who this model works for (and who it DOESN’T work for)
Works very well if you have:
- Paid traffic or constant lead generation (Meta/Google/portals/structured referrals).
- Fast or medium consultative sales (real estate, clinic, services, education, consortium, maintenance, light B2B).
- Sales team with 2+ people (or 1 person but with high volume and real organizational pain).
- WhatsApp as the central channel (or at least one of the top 2 channels).
Does NOT work (or becomes overkill) If you:
- Has very few leads per month and the problem is offer and demand, not process.
- Doesn’t accept standardizing stages (each seller “sells their own way” and you don’t want to change that).
- Wants “magic AI” that closes sales by itself. That doesn’t exist.
If you’re unsure whether Kommo is too much for your size, I was very direct here: Is Kommo worth it for small businesses and freelancers? When does it pay off and when is it overkill?.
Architecture I implement: 1 WhatsApp, 1 funnel, N agents — with real SLA
The goal is simple: every incoming lead has an owner, a deadline, and a next action. This prevents “disappearing conversations.” In practice, I design it like this:
- Input: lead coming from form, Instagram, website, campaign, call, or import.
- Screening: minimum qualification (e.g., city, budget, urgency, product).
- Distribution: routing rule (round robin, by portfolio, by region, by skill).
- execution: human service + targeted automations (without annoying the lead).
- Follow-up: automatic cadence based on status and idle time.
- Measurement: SLA dashboard + conversion by stage + idle time per responsible person.
What changes the game is the SLA. I don’t say “respond quickly” generically. I set a rule: maximum time for first response and maximum time without next action.
SLA in Kommo: what I consider “minimum viable”
You don’t need to start perfect. But you need to start measurable. A minimum viable SLA I use:
- First response: up to 5 minutes during business hours (when the lead is from paid traffic).
- No response from the lead: follow-up at 2h, 24h, 72h (adjustable by niche).
- Opportunity in negotiation: no opportunity stays more than 48h without a next task.
This isn’t “theory.” It’s queue management. If your team can’t comply, you find out with data and fix it (process, scale, offer, schedule, prioritization). Guesswork ends here.
Want to dive deeper specifically into SLA, queues, and routing inside Kommo? I’ve already published a very practical playbook: Kommo CRM with WhatsApp: how to design SLA, queues, and routing to sell more (without expanding the team).
Routing (for real): stop “passing leads by shouting”
Good routing isn’t just “distributing equally.” It’s distributing with ROI logic. The models I use most:
- Round robin (rotation): good for homogeneous teams and high volume.
- By region: real estate, technical support, multi-unit clinics.
- By product/line: when there is specialization (e.g., implant vs orthodontics; auto consortium vs property).
- By priority: hot lead (high intent) goes to the fast queue; cold lead enters nurturance.
Common mistake: routing without governance. The seller “takes” the lead, doesn’t respond, and no one sees it. I prevent this with 2 rules:
- Lead without interaction for X minutes returns to the queue (or changes owner).
- Lead stalled Y hours in the stage triggers alert + creates task + (in critical cases) reassigns.
Automatic follow-up that doesn’t annoy (and increases conversion)
Bad automatic follow-up is spam. Good automatic follow-up is cadence with context. I apply 3 principles:
- Event triggers message, not a “blind calendar.” Ex.: “lead requested a quote and disappeared.”
- Short message + clear action. Ex.: “Can I send you the options with prices now?”
- Automatic exit: if the lead responds, the automation stops and returns to a human.
Want a more complete view on cadences and classic mistakes? I detailed it here: Automatic sales follow-up: what it is, why almost everyone does it wrong, and how to set it up.
My ROI gauge: what I measure to prove CAC dropped
CAC can drop in two ways: (1) you pay less per lead; (2) you convert more with the same media cost. Kommo mainly targets item (2). So I measure:
- Time to first response (TFR) by channel and by agent.
- % of leads attended within up to X minutes.
- Advancement rate between stages (e.g., new lead → qualified → meeting → proposal → won).
- Time per stage (where the lead dies).
- Recovery rate via follow-up (leads that respond again).
When you improve TFR and increase advancement rate, your effective CAC drops because you need fewer leads to generate the same number of sales. This is math, not motivation.
If you want a more “spreadsheet-friendly” method to tie this together, I show the reasoning here: How to measure the ROI of business automations.
What it really costs to implement this model (no fluff)
Let’s separate two things: License and Deployment.
Kommo license: Kommo charges in US$ per user/month (prices vary by plan and promotions). I keep the numbers updated in specific posts because prices change. To avoid making up numbers here (that would be dishonest), I prefer to point you to the source I update frequently: How much does Kommo CRM cost? Prices and plans in 2026 and Kommo plans and prices in Brazil in 2026: which plan is worth it.
WhatsApp: if you want scale and security, you need to consider WhatsApp Business Platform (official API), which charges per conversation (categories and prices depend on the current Meta table and your BSP). Again: I won’t “guess” prices here. What I do is project cost per conversation, forecast volume, and only then design SLA and automations to reduce unnecessary conversation. If you want to enter this layer, read: Kommo + WhatsApp API: the real cost (in BRL) and what blocks ROI when you scale customer service.
Deployment: cost depends on scope. A funnel with SLA + routing + follow-up, integrated with lead sources, is usually a smaller project than “complete CRM with BI, multiple teams and ERP integrations.” I explain ranges and what is included (without fluff) here: How much it costs to implement Kommo (implementation service): real price ranges and what’s included in the project.
Execution checklist (what I implement in 7 steps)
- 1) Map the real funnel: stages that exist today (not the ones you wish existed).
- 2) Define minimum fields: what is needed to qualify without blocking customer service.
- 3) Define SLA: TPR + deadlines per stage + exception rules.
- 4) Configure queues and responsible parties: routing + redistribution due to inactivity.
- 5) Create cadences: automatic follow-up by status and idle time.
- 6) Instrument metrics: conversion reports + time per stage + productivity.
- 7) Train and lock the standard: simple playbook, weekly audit, continuous improvement.
Where many people go wrong (and think “Kommo doesn’t work”)
- They put 25 stages in the funnel and no one updates it. A good funnel is the one the team uses.
- Automates before standardizing. Automation in a bad process only scales errors.
- Does not measure time. Without time measurement, you can’t see bottlenecks or prove ROI.
- Leaves WhatsApp “tied to the seller’s CPF”. The company pays for media and the asset becomes personal.
- Does not define lead owner. Lead without an owner is a lost lead.
A simple calculation model for you to feel the impact on CAC
I use a straightforward reasoning (and you can run it in a spreadsheet):
| variable | before | after | Impact |
|---|---|---|---|
| Leads/Month | L | L | same investment |
| % served within X minutes | a% | b% | less lost leads |
| Lead to sale conversion rate | c% | d% | more sales with the same L |
| Effective CAC | Investment / (L*c%) | Investment / (L*d%) | falls when d% rises |
The point is: you don’t need to double conversion to see ROI. Sometimes going from 1.2% to 1.6% already changes everything — because media is expensive and waste is invisible when there is no SLA.
If I were to start from scratch today (without losing 90 days): my 14-day plan
- Days 1-3: minimum funnel + minimum fields + integrated lead sources.
- Days 4-7: SLA + routing + redistribution due to inactivity.
- Days 8-10: 3-layer follow-up cadence (new lead, qualified, proposal).
- Days 11-14: monitoring dashboard + weekly (30 min) correction ritual.
This is execution. No “eternal project.” The goal is to get the operation running and improve based on real data.
Conclusion: Kommo reduces CAC when it becomes a customer service system, not just CRM
If you want to reduce CAC on WhatsApp, stop looking for “message templates” as the main solution. Build SLA, implement rule-based routing and activate automatic follow-up with context. Kommo provides the infrastructure — but ROI only appears when there is a method.
If you want me to design this with you (funnel + SLA + queues + automation + metrics) and get your operation running with an execution standard, the next step is simple: request a project.
FAQ
The questions below are the ones I answer most in Kommo implementation with WhatsApp.