Forms and Bookings,
Filled Inside the Chat.

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.

Native Meta FlowsValidated fieldsStructured answersNo landing page needed
Flows Search anything…⌘K GSGauravOwner
Lead qualification Live1,284 runs today
TriggerNew inbound messageany connected numberAsk · quick replyWhat is your budget?Under 50L50L–1Cr1Cr+
If 1Cr+Assign senior repthen place a callElseSend listingstag: nurture
POST https://api.yourcrm.com/leads · 200 OK

Run history

Runs today
1,284
+9% vs yesterday
Completion
88%
1,130 finished
Recent runs
#48213 · 1Cr+Assigned
#48212 · 50LNurture
#48211 · 1Cr+Assigned
#48210 · Under 50LNurture
#48209 · 50LNurture
01

Fewer drop offs

People finish a form inside the chat far more often than one behind a link on a slow page.

02

Clean data, not free text

Dropdowns, dates and validated fields mean you get answers you can filter on, not paragraphs to read.

03

Straight onto the record

Every submission writes to the contact as custom fields, ready for a segment or an automation.

The builder

Design the screens, map the fields, publish

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.

  • Multi screen forms with conditional next screens
  • Field validation before the customer can submit
  • Mapping to custom contact fields
  • Submission webhook for your own systems
Flow · Site visit booking68% completion
ScreenFieldState
WelcomeIntro textlive
DetailsName, phonelive
SlotDate pickerlive
ConfirmOpt in toggledraft
Submissions today 214 · avg 41s to complete4 screens

How it works

From zero to live,
in four steps.

01Pick a Flow typeStart from a lead form, a booking, a survey or a blank canvas.
02Build the screensAdd fields, set validation and choose what happens after submit.
03Map to contact fieldsEach answer writes to a property you can segment on later.
04Publish and attachPut it on a template button, an automation step or a QR code.

What is inside,
in detail.

Screen builder

Multiple screens with conditional routing based on earlier answers.

Field types

Text, number, dropdown, multi select, date, checkbox and opt in toggle.

Validation

Required fields and format checks run before the customer can move on.

Contact mapping

Answers land as custom fields on the contact, not as loose text.

Submission webhook

Post every completed Flow to your own endpoint the moment it lands.

Completion analytics

See where people drop off, screen by screen.

Where rivals say no

The same feature,
across four platforms.

FeatureWBIZWATIInteraktAiSensy
Native Meta Flows supportPartialPartial—
Multi screen conditional routing———
Field mapping to contact propertiesLimitedLimited—
Per screen drop off analytics———
Submission webhook includedHigher tierHigher tierHigher tier

Competitor entries are indicative, from public 2026 pages. See the full 89-row benchmark.

FAQ

WhatsApp Flows questions

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

The rest of the platform

Automations

Trigger a Flow from a keyword, a campaign reply or an inbound message.

See automations

Lead forms

Capture leads from a page or an ad and continue the conversation on WhatsApp.

See lead forms

Contacts CRM

The record every Flow answer writes to, with tags and segments.

See contacts

Build your first Flow this week

Start free, publish a booking Flow on your own number, and watch the completion rate against your old form.