Kanban CRM on WhatsApp: how to build your sales funnel
How to set up a Kanban funnel within WhatsApp Web to stop losing leads. Stages, triggers and the SLA table per stage.
The biggest source of lost sales on WhatsApp is not price or product — it’s lead that disappears when scrolling. The customer sent a message yesterday, the attendant responded, and three days later no one remembers what happened. CRM Kanban solves this visually, without taking your team off WhatsApp.
Why Kanban works better than a spreadsheet
Spreadsheet is blind: it doesn't warn you when a lead has been idle for 3 days. Kanban is visual: each lead is a card and each column is a step. Take a look and see where the bottleneck is.
The minimum 5 columns of your funnel
- New: first contact. SLA: respond in < 5 minutes.
- Qualified: demonstrated real intention (asked price, deadline, scheduled). SLA: advance within 24 hours.
- Under negotiation: proposal sent, awaiting decision. SLA: follow-up in 48 hours.
- Closed: sale confirmed. After-sales starts here.
- Lost: registered reason (price, timing, competitor). Back to nurturing.
SLAs are not arbitrary: leads responded within an hour have 7 times more chance of qualifying than those who wait longer[1], and about 80% of sales require 5 or more follow-ups[2]. That's why "New" has a deadline of minutes and "In negotiation" has a mandatory follow-up within 48 hours.
Automatic triggers per column
The secret to productive Kanban is to tie each movement to automation. Real examples:
- New → Qualified: triggers message with catalog link and "interest-X" tag
- Qualified → Under negotiation: generates automatic proposal on Stripe / payment link
- Under negotiation for 48 hours without response: triggers automatic follow-up
- Closed: sends welcome message + schedules NPS survey for 7 days later
The Weekly Review Method
Every Monday, 30 minutes: the team opens Kanban, scans card by card, and responds:
- Has the column been stopped for more than X days? Why?
- Need to go up, down or archived?
- Is there a pattern of loss at a specific stage?
This ritualization is what separates the team that uses CRM for those who have CRM and ignore it.
Why within WhatsApp Web?
External CRM (HubSpot, Pipedrive, RD) has two problems in Brazil: attendant needs to switch between tabs and real conversation is somewhere else. Result: no one updates the CRM. A Zapext solution solves this by placing Kanban within the WhatsApp Web interface itself — updating the card is drag and drop.
Table: SLA per funnel stage
| Step | SLA first action | SLA follow-up | Key Metric |
|---|---|---|---|
| New | < 5 min | 4h | % answered in 5min |
| Qualified | < 1h | 24h | Feed rate |
| Under negotiation | < 2h | 48h | Time on internship |
| Closed | immediate (receipt) | 7 days (NPS) | NPS |
| Lost | register reason | 30 days (re-engage) | % recovery |
Conclusion
Within 90 days of disciplined use, Zapext customers report lead→sale conversion rising from 8-12% to 18-25%. It's not magic — it's stopping losing leads when scrolling through WhatsApp.
Sources
- [1] The Short Life of Online Sales Leads — Harvard Business Review (2011-03). accessed 2026-05-19.
- [2] Why you must follow up leads (archived copy) — Marketing Donut (via Internet Archive) (2023). accessed 2026-10-25.
Frequently asked questions
How many columns should my Kanban have?
Between 4 and 6. Less than 4 does not give visibility; more than 6 becomes chaos. Start with 5 (New, Qualified, Dealing, Closed, Lost) and adjust for your actual funnel.
Can I use Kanban with multiple agents?
Yes. Zapext supports multiple users per number, with lead assignment and card transfer between agents.
How do you know if a lead has been sitting idle for too long?
Configure alerts by SLA: lead in the 'New' column for more than 1h triggers notification. In the 'Under negotiation' column for more than 48 hours, automatic follow-up.
