WhatsApp Flows, and when to use them
Flows put a structured, form-like experience inside a WhatsApp chat: pickers, inputs and multi-step screens without leaving the conversation. They solve a narrow problem well.
Published
What they are for
Anything where you need specific, structured data and free text would be ambiguous. Appointment slots, sizes, dates, addresses, survey answers.
The value is that the customer never leaves WhatsApp, so you avoid the drop-off that comes with sending someone to a web form.
- Booking a slot from a list of times
- Collecting a delivery address in usable fields
- Structured surveys and lead qualification
- Selecting a variant, size or plan
Where they are the wrong tool
Flows are rigid. If the customer's situation does not match the form, they have no way to say so, and a form that cannot accommodate an exception frustrates people faster than a slow reply does.
Open-ended questions, negotiation and anything requiring judgement belong in conversation, not a form.
The strongest pattern is conversation first, flow second: let the agent understand what the customer wants, then present a flow only for the structured part.
Frequently asked questions
Do Flows replace a chatbot?
No. A flow collects structured input; it does not understand a question. They complement each other, with the agent deciding when a flow is appropriate.
Do Flows work on all devices?
They require a reasonably current WhatsApp version. Always design a conversational fallback for customers whose client cannot render one.
Keep reading
See it answer, in your own words
Tap the mic on our homepage and talk to the same AI your customers would. No form, no scheduling, no sales call first.