Why a WhatsApp pipeline differs from a normal CRM pipeline
Traditional CRMs were designed for selling over email and phone, with long cycles and infrequent contact. WhatsApp selling behaves differently: contact is frequent, replies are expected within minutes, and most decisions happen inside a single thread.
An effective WhatsApp pipeline therefore needs two properties general CRMs rarely have: cards must be created automatically from conversations, and moving stages must not add work for the people already replying to chats.
Choosing stages without overdoing it
- Inbound. New conversation, not yet handled.
- Qualified. Need is clear and fits what you sell.
- Quoted. Price or proposal has been sent.
- Negotiation. The customer responded and terms are being discussed.
- Won or lost. The transaction happened or was declared dead.
Every stage needs an objective exit criterion. A card may move to Quoted only when a price was actually sent, not when a rep feels the customer is interested. Feeling based criteria make pipeline data incomparable between people.
Rules that keep a pipeline clean
- One conversation, one card. A customer asking about two products stays one card with notes, not two cards racing each other.
- Every card has an owner. Ownerless cards get ignored by everyone.
- Set an age limit per stage. Cards older than the limit surface automatically in a review list.
- Record loss reasons. Without them you lose your most valuable improvement source.
- Do not delete lost cards. Move them to nurturing, because some will return.
Automation that genuinely helps
- Automatic card creation from every new conversation, including ad source where available.
- Automatic assignment by rotation, territory, or product type so nothing waits without an owner.
- Follow-up reminders for cards past the inactivity threshold.
- Automatic conversation summaries on the card so managers do not open full threads.
- Stage history recording, which enables velocity analysis and bottleneck identification.
Metrics read from the pipeline
- Stage to stage conversion, to find where most deals die.
- Average duration per stage, to find the slowest step.
- Weighted pipeline value, deal value times stage probability.
- Cards with no activity, the highest yielding daily work list.
- Top loss reasons, which usually reshape pricing or marketing material.
Mistakes that make teams abandon a pipeline
- Too many required fields. If moving a card needs seven inputs, people stop moving cards.
- Used for judgement, not help. Once it becomes a reprimand tool, the data gets polished.
- Never discussed. A pipeline absent from weekly meetings stops being filled within a month.
Frequently asked questions
How many stages are ideal?
Four to five for most businesses. Add a stage only when the team genuinely performs a different action there.
How do you handle repeat customers?
Create a new card per transaction rather than reusing the old one. Customer history stays on the contact while cards measure transactions.
Should stage probabilities be defined?
Useful for forecasting, but do not guess them. Derive them from your own historical data after a few months.
What if the team refuses to use the pipeline?
Usually because it adds work without giving anything back. Make sure the team gets something from it, such as a daily priority list that genuinely helps them close.
Next step
Define five stages with written exit criteria, run one sales cycle, then review stage conversion. The biggest improvement is usually concentrated in a single stage. See it in action at WhatsCRM Hub.
