Fewer drop offs
People finish a form inside the chat far more often than one behind a link on a slow page.
A Flow is a native WhatsApp form. The customer taps, fills the fields and submits, all without leaving the conversation, and the structured answers land on their contact record.
People finish a form inside the chat far more often than one behind a link on a slow page.
Dropdowns, dates and validated fields mean you get answers you can filter on, not paragraphs to read.
Every submission writes to the contact as custom fields, ready for a segment or an automation.
The builder
Add screens, drop in text inputs, dropdowns, date pickers, checkboxes and opt in toggles, then map each field to a contact property so the answer has somewhere to live.
Flows can be attached to a template button, triggered from an automation, or opened from a QR code, and every submission fires a webhook if you want it elsewhere.
How it works
Multiple screens with conditional routing based on earlier answers.
Text, number, dropdown, multi select, date, checkbox and opt in toggle.
Required fields and format checks run before the customer can move on.
Answers land as custom fields on the contact, not as loose text.
Post every completed Flow to your own endpoint the moment it lands.
See where people drop off, screen by screen.
Where rivals say no
Competitor entries are indicative, from public 2026 pages. See the full 89-row benchmark.
FAQ
Anything missing, a founder will answer directly.
A Flow is Meta’s native in chat form. The customer fills it inside WhatsApp and you receive structured answers instead of free text.
Flows are published through your WhatsApp Business Account, and templates that launch them follow the normal template review.
Yes. A date and slot picker plus a confirmation screen covers most booking cases, and the answer can trigger an automation.
Onto the contact record as custom fields, and to your webhook endpoint if you set one.
Yes, completion analytics break down views and exits screen by screen.
A lead form, a booking, a survey, a feedback screen or a short application, all inside the chat.
Text, numbers, dates, single and multiple choice, and dropdowns, with validation on each.
No. The Flow opens inside WhatsApp, so there is no browser tab and no link to lose people at.
Yes. Details like a name or a number can be filled in so the customer types less.
From a template button, an automation step, a quick reply or a QR code.
Yes. Each answer can start an automation, tag the contact or assign the chat.
Yes, on current WhatsApp versions on both, with a graceful fallback if a device is too old.
Yes. You publish a new version, and new sessions use it while open ones finish.
On the contact record as fields you can segment on, and at your webhook if you set one.
You can chain several screens. Shorter Flows finish more often, so keep it to what you need.
Explore more
Trigger a Flow from a keyword, a campaign reply or an inbound message.
See automationsCapture leads from a page or an ad and continue the conversation on WhatsApp.
See lead formsThe record every Flow answer writes to, with tags and segments.
See contactsStart free, publish a booking Flow on your own number, and watch the completion rate against your old form.