Create Pipeline Stages & Move Contacts on the Board

In this series — Part 2 of 5 (CRM Pipeline). · Previous: WhatsApp CRM Pipeline Guide: From Lead to Close… · Next: Priority, Filters & Kanban Tips for Sales Teams · Series start

Before you start: If you skipped earlier steps, read WhatsApp CRM Pipeline Guide: From Lead to Close… first so nothing here feels confusing.

A pipeline on paper does not move revenue. When you create pipeline stages your team updates, the board becomes real sales operations.

Cute column names nobody understands, fifteen micro-stages, and cards that never leave New turn CRM into wallpaper. Agents chat all day while the board lies. Forecasts stay fiction; stuck deals hide in plain sight.

In this guide, you'll discover how to create pipeline stages, order them left to right, move contacts when reality changes, and keep hygiene rules — without screenshot theater. As a WAPilot team that watches board adoption weekly, we see five-to-eight clear stages beat ornate unused boards.

Soft goal: every stage has a written definition, Won and Lost exist, and cards move right after the chat moment that earned the change. Concepts first lived in the pipeline guide; this part builds the board.

Operators who rush this step usually rebuild the same journey twice after customers complain.

Keep the path short enough that a new agent can explain it in one minute during standup.

How do you create pipeline stages on the Wapilot board?

Sources: Meta's Cloud API get-started guide and send messages docs. Open CRM/Pipeline board view. Add five to eight clearly named stages including Won and Lost, order them left to right as the journey, and define what each stage means. Use verbs or clear states a newbie understands on day one — avoid cute names.

Columns are stages; cards are contacts or deals. Start blank or from a template, then make it yours. Too many stages create board theater, not sales. Every stage needs a definition such as “Qualified = need + fit confirmed.”

Concepts: WhatsApp CRM pipeline guide. Chat context tools: labels notes canned replies.

How should you move contacts without lying to the board?

Find the card, drag to the new stage or use the stage picker, optionally note why it moved. Move when something true changed — first reply, demo done, payment received — not for a screenshot. Keep hygiene: no silent New forever, Lost reasons when useful, weekly stuck-card sweep.

Attributed example, from a WAPilot B2B workspace (2026): cards lingered in New while demos already happened. A rule — move within the same conversation after demo send — plus a Friday stale sweep restored board truth in one sprint.

1. Add 5–8 clear stages including Won/Lost.
2. Write a definition for each column.
3. Order left → right as the journey.
4. Move cards when reality changes.
5. Sweep stuck cards weekly.

Rule sources: Meta Cloud API get-started and send messages docs. Wapilot CRM board tracks deals beside inbox; Meta still governs WhatsApp messaging on the Cloud API number.

How does chat trigger a stage change?

After the customer confirms fit, move to Qualified. After you send the proposal, move to Proposal. After payment, Won. Flow CRM nodes can automate evidence-based moves later — never on a maybe. How we know: WAPilot board hygiene reviews weekly map forecast lies to unmoved cards — against Meta’s public messaging ops context.

What board mistakes waste Series 11?

Unclear names, no Won/Lost, moving for vanity, and never sweeping stale cards. Next: priority, filters, and Kanban tips for sales teams.

Assignment rules later route chats fairly — stages still tell agents what “done” means.

Keep stage names identical wherever automation writes them — flows, AI tools, and humans.

Drip sequences can nurture while the card waits in Qualified — do not confuse nurture with stage jumps.

If calling via WhatsApp calling / rabbit-calls closes a deal, move Won in the same sitting.

A board your newest agent understands is the board your team will actually update.

Treat this guide as an operations checklist, not a one-time read. Print the ordered steps and assign an owner for each gate before you flip traffic live.

When something fails in production, capture the customer wording, the node that fired, and the Meta-facing symptom before you redesign the whole canvas.

Keep internal links few and intentional — adjacent series posts and the hub beat random keyword stuffing across twenty URLs.

Respect quiet hours and staffing plans. Automation that earns replies without inbox coverage creates the same unread spikes as careless campaigns.

Version names, changelogs, and a fifteen-minute post-publish review prevent mystery drafts from becoming the source of truth.

If quality rating slides after a launch, pause broad triggers first, fix consent and relevance, then warm traffic again on official Cloud API.

Keep these phrases in your team glossary so search and training stay aligned: Kanban board; Won Lost stages; stage definitions.

FAQs

How many stages is too many?

If agents cannot explain a column in one sentence, merge it — most teams stay at five to eight.

Should every chat move a card immediately?

Move when a real milestone happens — not after every casual message.

Do we need Lost reasons?

When useful for coaching — patterns in Lost reasons improve sales process faster than vanity Won counts.

Does a bot-to-agent handoff reset the window on a shared number?

No. One customer thread, one service window. Two brands on one Cloud API line share that clock — split numbers before you scale support and promos on the same line.

Recap: ship the habit, keep a human exit, and measure what customers actually do. When you are ready, start a free trial and grow on official Cloud API.