Build a WhatsApp sales pipeline your team will actually use
A pipeline is useful only when its stages represent observable customer progress and tell the team what to do next. This guide provides a practical model for moving WhatsApp conversations from new inquiry to a measurable outcome.
- Use a small number of decision-oriented lifecycle stages.
- Define entry, exit and next-action criteria for every stage.
- Protect deliberate ownership while automating routine routing.
- Review stage age and conversion to find process bottlenecks.
Start with customer progress, not internal activity
Stages such as Contacted or Followed Up describe what the team did. Stages such as Qualified, Proposal Requested or Negotiation describe what changed in the buying process. Customer-progress stages produce clearer reporting and better next actions.
A simple model might use New inquiry, Qualified, Proposal, Negotiation, Won and Lost. Add a stage only when it changes ownership, required information, follow-up or reporting.
Define every stage operationally
For each stage, write the evidence required to enter it, the condition required to leave it, the accountable owner and the default next action. This prevents one agent’s Qualified from meaning another agent’s New inquiry.
In Aixun, lifecycle stages can be ordered within pipelines and connected to workflows. Conversation events retain a history of how and why the stage changed.
- Entry evidence
- Required customer information
- Default owner or routing rule
- Expected next action
- Maximum healthy time in the stage
- Exit and loss reasons
Connect assignment and workflow carefully
New inquiries can use a default routing policy such as round robin, least loaded, team, skill or VIP routing. Once an agent deliberately owns the relationship, workflows should not overwrite that decision unless reassignment is explicitly allowed.
Workflows can create tasks, propose stage changes and apply routing policy from normalized events. Keep the priority order clear when several rules could respond to the same event.
Run a weekly pipeline review
Review conversion between stages, median age, overdue next steps, reassignment patterns and loss reasons. Open the underlying conversations for a small sample; numbers show where to look, while conversation context explains why.
Update the lifecycle only when the new definition produces a clearer decision. Constantly changing stage names makes trend reporting and agent adoption worse.
Frequently asked questions
How many pipeline stages should we use?
Use the fewest stages that represent meaningful customer progress. Many teams can begin with five or six and add complexity only when it changes the operating process.
Can we have more than one pipeline?
Yes. Separate pipelines can support materially different products or processes, but avoid splitting them when only a label or one field differs.
Who should be allowed to change stages?
Agents can manage active conversations, while administrators define the lifecycle. AI and workflows can propose or perform changes according to explicit approval policy.