Skip to main content
A good WhatsApp conversation is designed, not just written. The difference between a flow people finish and one they abandon usually isn’t the technology — it’s the shape: what you ask first, how much you ask at once, and whether tapping is easier than typing. This page is about that thinking. It’s not about the buttons in the builder — for how to actually create, preview, and publish flows in Paige, see Flows Builder. Here we’re one level up: how to decide what the conversation should look like before you build it.
“Flow” is used two ways. Broadly, it means the shape of a whole conversation — the order you take someone through. Specifically, a WhatsApp Flow is a multi-screen form that opens inside the chat. This page is mostly about the first sense, and it’ll tell you when to reach for the second.

​
When a flow beats free text — and when it doesn’t

Structure helps when the answer needs to be specific. It gets in the way when the question is open.

Reach for structure

  • You need a specific value — a date, a choice from a set, a valid email.
  • There’s a right set of options and you want to prevent typos and dead ends.
  • The same information gets collected every time (bookings, intake, sign-ups).
  • You want the data clean enough to save straight to a database.

Leave it open

  • The customer has a question you can’t predict.
  • You’re offering support, advice, or anything conversational.
  • Forcing buttons would feel robotic or block what they’re trying to say.
  • One free-text reply is genuinely faster than three taps.
A strong pattern is to lead with free text (“Hi, how can I help?”), understand intent, and only then drop into a structured flow once you know the person wants to book, sign up, or file something. Structure is a tool you reach for at the right moment — not a cage you put every conversation in.

​
How to structure the steps

Once you’ve decided a stretch of the conversation should be structured, the order and size of the steps decide whether people finish.
1

Ask the easy, motivating thing first

Open with a low-effort choice that moves things forward — a “Book a table” button, a “Get started” tap. Momentum early makes people more likely to stay. Save anything that feels like work (long text fields, personal details) for after they’re committed.
2

One idea per screen

Don’t stack five questions on one screen. Ask for a little, confirm it, move on. Short steps feel fast even when there are several of them; one crowded step feels like a form and gets abandoned.
3

Order by drop-off risk

People leave when effort spikes. Put the highest-friction step (payment details, a long note) as late as you can, so anyone who was going to drop off has already got value from the earlier steps.
4

Confirm at the end

Close with a short summary of what you captured and a clear confirmation. It reassures the person it worked, and it’s your last chance to catch a wrong date before it becomes a problem.
If a flow starts feeling long, that’s a design signal, not a reason to cram. Cut optional steps, combine related fields, or split one long journey into two shorter flows triggered in sequence. Fewer, cleaner steps almost always beat one exhaustive form.

​
How to craft the messages

WhatsApp is not email. The whole thing is read on a phone, in a thread that’s mostly friends and family, in a few seconds. Write for that.
  • Keep it short. A sentence or two per message. If you’re scrolling to read it, it’s too long. Break a big idea into two messages rather than one wall of text.
  • Match the register. Warm and direct, the way a helpful person texts — not the way a company writes a policy. Contractions are fine. A well-placed emoji is fine. A paragraph of legalese is not.
  • Make the next step obvious. Every message should make it clear what to do next. If you’re asking a question, ask one.
  • Write buttons as actions. A button gets tapped when its label says exactly what happens — “Book a table”, “See today’s menu”, “Talk to a person”. Vague labels like “OK” or “Continue” make people hesitate. Keep them short; long labels get truncated.

​
Buttons vs. a list

Both let people tap instead of type. Which one depends on how many options there are.
If you can phrase it as two or three options, use buttons — they’re visible without a tap, so people act faster. Reach for a list only when the choices genuinely outgrow that. See Message Types for what each looks like in a chat.

​
Common shapes

Most useful conversations are a variation on a handful of shapes. Recognising which one you’re building tells you how to order the steps.

Capture

Turn a stranger into a known contact. Get the few details you need — name, and one way to reach them — and nothing more. Short is the whole point; every extra field costs you completions.

Qualify

Work out who this person is and what they need before spending time on them. A couple of routing questions — what are you after, how soon, what budget — then branch to the right next step.

Book

Get someone to a confirmed slot. Choose a service, pick a date and time, confirm. A WhatsApp Flow shines here because dates and time slots want proper pickers, not typed text.

Confirm

Close the loop after something happened — an order, a booking, a submission. Summarise what you’ve got, confirm it back, and tell them what comes next. Short, reassuring, done.
Most real conversations chain these together: qualify to find out someone wants to book, book them in, confirm the slot, then capture anything you’ll need for next time.

​
Where to next

Flows Builder

Ready to build one? This is the hands-on guide to generating, previewing, and publishing flows.

Message types

The full set of building blocks — buttons, lists, media, and more — with what each is for.