Skip to content
BitByteCore ConnectBook a demo
Open the product menu
ProductSolutionsPricingHow it worksFAQCompany

Guide · Flows · For the owner choosing between a chat form and a web form

WhatsApp Flows: forms inside the chat, and Meta's rules for making customers finish them

A WhatsApp Flow is a small form that opens inside the chat: a few screens with fields, choices and a button, which the customer fills in without leaving WhatsApp. Meta built it for the moments when free text is clumsy, such as booking an appointment, asking for a quote or collecting a lead's details. Meta's own pages describe what Flows are for and, more usefully, the habits that decide whether customers finish one or close it halfway. Here is both, for the owner deciding whether a form belongs in the chat.

Published 1 October 2026 · Updated 8 October 2026

What a Flow is, and what Meta says it is for

Meta describes Flows as structured interactions for business messaging: instead of asking a customer to type their name, date and preference as three separate messages, the business sends one message with a button, and the button opens screens where the customer taps and types in order. Meta names lead generation and product recommendation as the headline uses, and packages four worked examples: a pre-approved loan offer, an insurance quote built from the customer's answers, a short purchase-intent survey before a campaign, and a personalised offer picked from budget and interests. Meta adds that local data regulations and its Business Messaging Policy apply to whatever a Flow collects.

Two kinds of Flow

Meta distinguishes a Flow that runs on its own, with everything the customer needs already inside it, from one connected live to your system while the customer fills it in. Meta prefers the first: it opens faster, is quicker to build, and can still carry details that change per customer, filled in at sending time. It recommends the live connection only where the answer depends on data that changes minute to minute, such as which seats are still free when booking a ticket.

Meta's WhatsApp Business site lists three ways to start. A simple Flow can be made without code by choosing a message template in WhatsApp Manager. A provider can build one for you. And a developer can build more advanced screens with Meta's Flow Builder or its programming interface.

The rules that decide whether customers finish

Short
Meta's ceiling is a task of no more than 5 minutes. One task per screen; if the job has several parts, spread them over several screens rather than crowding one. Fewer parts on a screen also means it loads faster.
Saved screen by screen
What a customer enters is kept once they move to the next screen. If a single screen asks for everything and the customer leaves halfway, all of it is lost, which Meta flags as a frustration to design out.
Buttons that say what happens
Every button should name the result, such as Confirm booking, in sentence case, and the first screen must do exactly what the button in the chat promised. Meta says any surprise there makes customers close the Flow.
The right field for the job
A date picker for a date of birth, a larger text box where the answer is long, questions in a sensible order such as first name then last name, non-essential fields marked optional, and a line of helper text showing the expected format for a phone number, date or email.
Choices
No more than 10 options on a screen. A dropdown only from 8 options up; otherwise round buttons for a single choice and tick boxes where several are allowed, with the top option pre-selected.
Where the customer is
Say up front how long it takes, use short action titles such as Book appointment, show progress in the title where you can, such as Question 1 of 3, and end with a summary screen the customer can review before submitting.

Logins, errors and side-paths

Login screens put people off
Meta's research found that a login screen inside a Flow confuses customers, some of whom think they are being sent out of WhatsApp. Its advice: ask for a login only when you must, warn the customer that it is coming, show the benefit first, and place it as one of the last steps.
Errors in plain words
Say what went wrong and how to fix it, and state the rules before the customer breaks them, such as how long a password must be. If a live-connected screen stops being valid, for instance a slot taken while the customer was deciding, send them back one screen rather than ending the Flow.
Side-paths of three screens at most
A detour such as a forgotten-password path should be at most 3 screens and must return the customer to the main task.
The link should not expire overnight
Meta suggests keeping a Flow message usable for 2 to 3 days after it is sent, so a customer who opens it the next evening is not met with an error. Where that cannot be done, the error should tell them how to get a fresh one.

After the customer submits

Meta asks for two things. First, the last screen should say what happens next, and the business should reply with a confirmation that names the next step and who to contact to change or cancel. Second, since Flows version 5.1 the customer can open a summary of everything they submitted from the message itself. Password and passcode fields are left out automatically; any other field the business marks as sensitive is left out too. For a Flow that collects an identity-document number or a card detail, marking those fields sensitive is the difference between a tidy receipt and a record sitting in the customer's chat history.

Meta also wants the business logo visible in the Flow's footer, so the customer knows who is asking, and a way to get in touch from inside the Flow or in the follow-up message. A Flow sent cold to a customer is a template, and the rules in the 24-hour window guide and the opt-in guide apply to it as to any other.

A Flow on an ad

Meta's Business Help Center describes a Flow attached to a Facebook or Instagram ad that opens WhatsApp. The person who taps the ad can fill in the form, or skip it and start a chat with the business instead. Meta suggests it for screening new leads on need, budget or timeline, for booking appointments and service calls, and for sign-ups to events and offers. Meta says the feature may not be available to every advertiser yet, and that it does not work when the ad's chat runs through a third-party app's message template.

What you need first
A WhatsApp Business account connected to the business's Facebook Page, a campaign for an ad that opens WhatsApp with an objective such as awareness, traffic, engagement, leads or sales, and WhatsApp as the only messaging destination on the ad.
Where it is set
In Ads Manager, at the ad set level under Message template, choose the option to collect information with a form in WhatsApp. Edit lets you write the welcome message and change the questions. Preview the WhatsApp experience, then publish.
Where the answers land
On the WhatsApp Business app, each response appears in that customer's chat, and you can download that one or every response from the campaign. On the Cloud API, the answers are delivered to the business's own system, which has to store them.
When the option is missing
Meta gives three reasons: WhatsApp is not chosen as the message destination for the ad set, the WhatsApp account is not connected to the Facebook Page, or the feature has not reached your ad account yet.

Meta's tips for better leads are short: ask only what you need to qualify someone, put the most important questions first so a half-finished form still tells you something, match the questions to how your team will follow up, make the first button say plainly what happens next, and proofread before publishing.

Our reading: keep the answers with the chat

A form answer is only useful if whoever replies can see it. On the Cloud API, that means the system receiving the answers should keep them beside the customer's conversation and the ad that brought them in, so nobody asks the same questions twice.

Questions

Can we put a form on our ad that opens WhatsApp?

Yes, where Meta has made it available to your ad account. Meta's Business Help Center says a Flow can be attached to a Facebook or Instagram ad that opens WhatsApp, at the ad set level under Message template. The customer can fill it in or just start a chat. WhatsApp has to be the ad's only messaging destination, and the WhatsApp account must be connected to your Facebook Page.

Why would we use a Flow instead of sending the customer to our website form?

Because the customer never leaves the chat, answers are kept screen by screen, and the result lands in the same thread the conversation is in. Meta's own use cases are lead capture, quotes and preference surveys, which are exactly the forms people abandon on a slow mobile website.

Do we need a developer to build a Flow?

Not for a simple one. Meta's WhatsApp Business site says a basic Flow can be created by choosing a message template in WhatsApp Manager. Anything that has to talk to your own systems while the customer fills it in needs a developer or a provider.

How long can a Flow be?

Meta's ceiling is a task of no more than 5 minutes, one task per screen, at most 10 options on any screen, and any side-path at most 3 screens.

Will the customer see what they typed afterwards?

Yes, since Flows version 5.1: a summary of their submitted answers is available from the message. Password and passcode fields are excluded automatically, and the business can mark other fields sensitive so they are excluded too.

Does a Flow need to be connected to our booking system?

Only when the screens depend on live data, such as which slots are free right now. Meta prefers Flows that run on their own and recommends the live connection only for the screens that truly need it.

Sources

More plain-language notes like this one are on the guides page.

Want bookings, quotes or lead details collected inside the chat?

We set up a business's WhatsApp number on a proper system and build the Flow to Meta's own rules: short screens, the right field for each answer, sensitive fields hidden from the receipt, and every submission landing in one place the business owns. A short call is the easiest way to see whether it fits your business.

Book a demo