Kanban CRM for WhatsApp: the method that doubles conversion
How to build a Kanban funnel inside WhatsApp Web so you stop losing leads. Stages, triggers, and the SLA table per stage.
The biggest source of lost sales on WhatsApp isn't price or product — it's leads vanishing in the scroll. Customer messaged yesterday, agent replied, three days later no one remembers where it stood. Kanban CRM fixes this visually, without pulling your team out of WhatsApp.
Why Kanban beats a spreadsheet
A spreadsheet is blind: it doesn't warn you a lead has been stuck for 3 days. Kanban is visual: each lead is a card, each column a stage. One look and you see the bottleneck.
The 5 minimum columns of your funnel
- New: first contact. SLA: respond in < 5 minutes.
- Qualified: showed real intent (asked price, deadline, booked). SLA: advance within 24h.
- In negotiation: proposal sent, awaiting decision. SLA: follow-up in 48h.
- Closed: sale confirmed. Post-sale starts here.
- Lost: reason logged (price, timing, competitor). Goes back to nurture.
Automatic triggers per column
The secret to a productive Kanban is tying every move to an automation. Real examples:
- New → Qualified: fires catalog link and tags "interest-X"
- Qualified → In negotiation: generates Stripe proposal / payment link
- In negotiation for 48h without reply: auto follow-up
- Closed: welcome message + NPS scheduled for 7 days out
The weekly review ritual
Every Monday, 30 minutes: the team opens Kanban, sweeps every card, and answers:
- Stuck in this column for more than X days? Why?
- Should it move up, down, or be archived?
- Is there a pattern of losses at a specific stage?
This ritual is what separates teams that USE a CRM from teams that HAVE one and ignore it.
Why inside WhatsApp Web?
External CRMs (HubSpot, Pipedrive) have two problems: agents have to switch tabs and the real conversation lives elsewhere. Result: nobody updates the CRM. The Zapext solution fixes this by placing the Kanban inside WhatsApp Web — moving a card is drag-and-drop.
Table: SLA per funnel stage
| Stage | First-action SLA | Follow-up SLA | Key metric |
|---|---|---|---|
| New | < 5 min | 4h | % replied in 5min |
| Qualified | < 1h | 24h | Advance rate |
| In negotiation | < 2h | 48h | Time in stage |
| Closed | immediate (receipt) | 7 days (NPS) | NPS |
| Lost | log reason | 30 days (re-engage) | % recovery |
Conclusion
After 90 days of disciplined use, Zapext customers report lead-to-sale conversion rising from 8-12% to 18-25%. It's not magic — it's no longer losing leads in the WhatsApp scroll.
Frequently asked questions
How many columns should my Kanban have?
Between 4 and 6. Fewer than 4 hides visibility; more than 6 turns to chaos. Start with 5 (New, Qualified, Negotiation, Closed, Lost) and tune to your real funnel.
Can multiple agents share a Kanban?
Yes. Zapext supports multiple users per number, with lead assignment and card handoff between agents.
How do I know if a lead has been stuck too long?
Set SLA alerts: lead in 'New' for more than 1h fires a notification. In 'Negotiation' for more than 48h, automatic follow-up.