WhatsApp Workflows: Organize Your Post-Sale With a Kanban Board

Your customer bought, you sent the order into production, and three days later nobody remembered to chase the payment that was still pending. The quote you sent on Monday vanished into fifty other chats. The client who asked to reschedule is still waiting on a callback that never came. And your so-called "follow-up" lives in a notebook, a stray spreadsheet, or — worse — only in your head.

Customer service doesn't end when the conversation does. It keeps going: there's the post-sale, the order in progress, the appointment, that repeat customer you need to win back. That's exactly where things slip through the cracks — in the ongoing work after the first reply. And that's what WhatsApp Workflows in LewFlow are built for.

What a Workflow Is (Your Kanban Pipeline)

Picture a board split into columns. Each column is a stage in your process. Inside each column sit cards — every card is a customer, a contact, or a record. When something moves forward, you drag the card from its current column to the next one. That simple: one glance and you know exactly where every customer stands.

The most important part: the stages are fully configurable. The neutral default is "New, In Progress, Done," but that's just a starting point. Every business builds its own pipeline, with the names that make sense for its work. The logic reads your company's configuration — there's no "correct" workflow handed down from above.

Every Card Carries the Whole Story

A card isn't just a name. It pulls together, in one place, everything that has happened with that customer:

• History: what was done, with date, time, and author — you can see who said what, and when.
• Attachments: a photo of the finished product, a receipt, the service file, a screenshot of the chat. It all lives right there, as proof, in the right place.
• Spreadsheet export (CSV): whenever you want, pull the cards and their history out of the system with one click.

How to Build Your WhatsApp Workflow

None of the pipelines below come ready-made: you create the stages using your own business's names. These are just examples put together by five kinds of company to show how far the board bends to fit:

• E-commerce / wholesale: First Contact → Quote Sent → Awaiting Payment → In Production → Shipped → Post-Sale. That "order in production nobody remembered to chase" stops slipping, because it stays visible in the "Awaiting Payment" column until someone handles it.
• Clinic or practice: Pre-booking → Appointment Set → Awaiting Follow-Up → Done. The patient who asked to reschedule doesn't fall through — they stay visible in the "Awaiting Follow-Up" column until you get back to them, with the full history of everything already discussed.
• Service provider (repair, remodeling, installation): Request → Quote → Job Scheduled → In Progress → Completed. The photo of the finished job goes in as an attachment on the card, becoming proof of delivery.
• Shop with a customer base: New Customer → Onboarding → Active → Win-Back. You can keep track of who bought once and hasn't come back, without relying on memory.
• Support / recurring service: Ticket Opened → Under Review → Awaiting Customer → Resolved. No ticket stays "open forever" without anyone noticing.

Notice that "In Production," "Awaiting Follow-Up," and "Onboarding" are just names each business gave its own columns. The board works for any kind of ongoing customer service — a stage is whatever you decide it is.

What Actually Ties Into WhatsApp

And here's the part that changes the game. The same contact you're helping in WhatsApp can become a card in a workflow. The post-sale stops living in a notebook separate from the chat — it's born out of the conversation itself. You help the customer, close the sale, and that contact drops into the pipeline so the follow-up comes back onto your radar exactly when it needs to.

And because all of this happens inside LewFlow, you keep the same organized inbox you already rely on: multiple agents on a single number, queues and departments, accept and transfer (one conversation per agent at a time, so two people never reply in the dark), tags, quick replies, and the Active / Waiting / Closed tabs. Every conversation gets a ticket number and a closing message, the history is permanent, you can follow the check/check and read receipts, and each company stays isolated from the next, with data handled in line with privacy law.

To triage who comes in, the visual menu chatbot handles the basics and — if you want — an optional AI agent steps in as a fallback to the menu. Either way, it always offers to hand off to a human: nothing decides on its own in the dark.

Dragging is the visual way, but you can also move a card by command from the chat, without taking your hands off the conversation. And you can sort each stage by newest or oldest — handy when a column fills up and you want to tackle whoever has been waiting longest first.

Always Within Meta's Rules

Organizing your pipeline is no excuse to pester customers. LewFlow respects the 24-hour window — outside of it, it warns you and blocks free-form text, requiring an approved template. No mass blasts, no spam. The board helps you remember the customer; the communication stays on the right cadence and within the rules.

Workflows: Get the Post-Sale Out of Your Head

If your post-sale, your appointments, and your orders in progress are scattered today across chats, spreadsheets, and your own memory, Workflows put it all on a board you can read at a glance. Build the stages your way, drag the cards, keep the proof, and export whenever you need — without switching tools and without losing anyone along the way.

Want to see the pipeline running on your own process? Take a look at LewFlow and try WhatsApp Workflows for free alongside multi-agent customer service.