WhatsApp Flows — app-like forms inside chat
Meta's newest product. Render multi-step, structured journeys — bookings, KYC, lead capture, returns, surveys — inside WhatsApp itself. No redirects. No app installs. Completion rates 2–4x higher than web forms.
- Drag-and-drop Flow Builder
- Native CRM & webhook sync
- Templates for every vertical
- Cloud API powered
Key things to know
Visual Flow Builder
Drag-and-drop screens, conditional logic, validation rules — no code required.
All input types
Text, number, date, dropdown, radio, multi-select, image carousel, embedded media.
E-commerce ready
Size pickers, address forms, COD confirmation and product catalogues inline.
Booking flows
Service + slot pickers with availability pulled live from your calendar or CRM.
People also ask
Q.What are WhatsApp Flows?
WhatsApp Flows is Meta's native interactive surface — multi-step, app-like forms and journeys that run inside the WhatsApp chat. Customers can complete lead capture, bookings, KYC, surveys, address collection and product browsing without ever leaving WhatsApp.
Q.How are Flows different from a regular chatbot?
Chatbots send messages and read replies. Flows render structured screens — dropdowns, date pickers, multi-select, image carousels, conditional logic — inside WhatsApp. Completion rates are 2–4x higher than equivalent web forms because there's no redirect, no app install and no login.
Q.Do I need to code to build a Flow?
No. LandinChat ships a drag-and-drop Flow Builder with templates for lead capture, booking, KYC, NPS, returns and onboarding. Developers can also author Flows in JSON and connect them to internal APIs via webhook.
Q.Which industries get the most lift from Flows?
D2C / e-commerce (abandoned cart + size pickers), real estate (site-visit booking), fintech (KYC + EMI quotes), healthcare (appointments), edtech (demo booking) and travel (booking flows).
Q.Are Flows available on Cloud API only?
Yes. WhatsApp Flows requires the Cloud API (or supported BSPs on top of it). We provision Cloud API as part of LandinChat onboarding.
Q.Can Flows submit data into my CRM or backend?
Yes. Every Flow submit fires a webhook with structured JSON. LandinChat ships native syncs for HubSpot, Salesforce, Zoho, Shopify, Pipedrive, Google Sheets and a generic webhook for everything else.
What WhatsApp Flows are — and why early adopters are winning
WhatsApp Flows is a Meta product launched on the WhatsApp Business Platform that lets brands render structured screens — dropdowns, multi-select, date pickers, image carousels, conditional logic — directly inside a WhatsApp conversation.
From a customer's point of view, a Flow looks like a mini-app inside their chat. They tap a button in your message, complete a 2–5 screen form, and submit — all without leaving WhatsApp, installing anything or logging in.
Because there's no app install, no redirect and no login, completion rates on Flows are typically 2–4x what brands see on equivalent web landing pages — especially in markets where WhatsApp is the primary internet surface (India, Brazil, Mexico, Indonesia, MENA).
LandinChat ships a visual Flow Builder, a JSON-source mode for developers, and templates for the highest-converting use cases: lead capture, booking, KYC, returns, NPS surveys, address collection and product browsing.
Built for serious growth teams
Visual Flow Builder
Drag-and-drop screens, conditional logic, validation rules — no code required.
All input types
Text, number, date, dropdown, radio, multi-select, image carousel, embedded media.
E-commerce ready
Size pickers, address forms, COD confirmation and product catalogues inline.
Booking flows
Service + slot pickers with availability pulled live from your calendar or CRM.
Lead capture & KYC
Multi-step lead qualification, document upload, OTP verification inside chat.
Pay inside the flow
Combine Flows with WhatsApp Pay / payment links to close the loop without leaving chat.
Get live in days, not months
- 1
Pick a template
Start from a vetted template — lead capture, booking, KYC, returns or NPS — or build from scratch.
- 2
Design screens visually
Drag inputs, set validation rules and conditional logic in the Flow Builder.
- 3
Wire to your stack
Connect the Flow submit to your CRM, helpdesk, calendar, payment or generic webhook.
- 4
Trigger from anywhere
Launch Flows from broadcasts, click-to-WhatsApp ads, keywords, chatbot intents or auto-replies.
- 5
Measure & iterate
Track completion, step drop-off and downstream conversion in LandinChat analytics.
What teams ship with this
Lead capture for ads
Replace ugly web lead forms with a 30-second WhatsApp Flow on every click-to-WhatsApp ad.
Appointment booking
Service + slot picker for clinics, salons, real-estate visits and consultations.
KYC & onboarding
Collect documents, photos and structured data for fintech, lending and insurance journeys.
Returns & RTO reduction
Confirm COD orders and capture reason-for-return in a structured 2-screen flow.
NPS & CSAT surveys
1–10 ratings, multi-select drivers and free-text feedback in under a minute.
Catalogue browsing
Show categories, products and add-to-cart inline with native image carousels.
Frequently asked questions
Why WhatsApp Flows — app-like forms inside chat is the highest-leverage move for growth teams
WhatsApp is where growth teams customers actually reply. Open rates sit at 85–98% inside 15 minutes versus 18–22% on email and sub-2% on SMS, and the medium is conversational — a customer can ask a follow-up, share a photo, or pay without leaving the thread. That is the entire premise behind whatsapp flows — app-like forms inside chat: stop losing the conversation to slow channels and let intent convert while it is warm.
Most growth teams teams treat WhatsApp as a broadcast megaphone. The teams that win treat it as a workflow surface — every notification is also a decision point where the customer can act. The capabilities below are wired to do exactly that: each one collapses a multi-step off-platform detour into a single in-thread reply.
The impact numbers on this page — 2–4x completion vs web forms, <60s average completion time, 0 app installs required, 10+ native crm integrations — are pulled from LandinChat customers running this workflow for at least 90 days. They are directional; your mileage depends on list quality, template approval speed, and how aggressively you route qualified conversations to a live agent.
Each capability, in plain terms
Visual Flow Builder
Drag-and-drop screens, conditional logic, validation rules — no code required. In practice this means the growth teams operator running whatsapp flows — app-like forms inside chat does not need to compose the logic themselves; they pick the trigger, review the copy, and let LandinChat handle rate-limits, template compliance, and retry behaviour.
All input types
Text, number, date, dropdown, radio, multi-select, image carousel, embedded media. In practice this means the growth teams operator running whatsapp flows — app-like forms inside chat does not need to compose the logic themselves; they pick the trigger, review the copy, and let LandinChat handle rate-limits, template compliance, and retry behaviour.
E-commerce ready
Size pickers, address forms, COD confirmation and product catalogues inline. In practice this means the growth teams operator running whatsapp flows — app-like forms inside chat does not need to compose the logic themselves; they pick the trigger, review the copy, and let LandinChat handle rate-limits, template compliance, and retry behaviour.
Booking flows
Service + slot pickers with availability pulled live from your calendar or CRM. In practice this means the growth teams operator running whatsapp flows — app-like forms inside chat does not need to compose the logic themselves; they pick the trigger, review the copy, and let LandinChat handle rate-limits, template compliance, and retry behaviour.
Lead capture & KYC
Multi-step lead qualification, document upload, OTP verification inside chat. In practice this means the growth teams operator running whatsapp flows — app-like forms inside chat does not need to compose the logic themselves; they pick the trigger, review the copy, and let LandinChat handle rate-limits, template compliance, and retry behaviour.
Pay inside the flow
Combine Flows with WhatsApp Pay / payment links to close the loop without leaving chat. In practice this means the growth teams operator running whatsapp flows — app-like forms inside chat does not need to compose the logic themselves; they pick the trigger, review the copy, and let LandinChat handle rate-limits, template compliance, and retry behaviour.
How this actually rolls out
Step 1. Pick a template
Start from a vetted template — lead capture, booking, KYC, returns or NPS — or build from scratch. On day one, an onboarding specialist walks a growth teams operator through this step live; on subsequent campaigns, the team runs it themselves from the LandinChat console. Expect this step to take between 15 minutes and an afternoon depending on how clean your existing data is.
Step 2. Design screens visually
Drag inputs, set validation rules and conditional logic in the Flow Builder. On day one, an onboarding specialist walks a growth teams operator through this step live; on subsequent campaigns, the team runs it themselves from the LandinChat console. Expect this step to take between 15 minutes and an afternoon depending on how clean your existing data is.
Step 3. Wire to your stack
Connect the Flow submit to your CRM, helpdesk, calendar, payment or generic webhook. On day one, an onboarding specialist walks a growth teams operator through this step live; on subsequent campaigns, the team runs it themselves from the LandinChat console. Expect this step to take between 15 minutes and an afternoon depending on how clean your existing data is.
Step 4. Trigger from anywhere
Launch Flows from broadcasts, click-to-WhatsApp ads, keywords, chatbot intents or auto-replies. On day one, an onboarding specialist walks a growth teams operator through this step live; on subsequent campaigns, the team runs it themselves from the LandinChat console. Expect this step to take between 15 minutes and an afternoon depending on how clean your existing data is.
Step 5. Measure & iterate
Track completion, step drop-off and downstream conversion in LandinChat analytics. On day one, an onboarding specialist walks a growth teams operator through this step live; on subsequent campaigns, the team runs it themselves from the LandinChat console. Expect this step to take between 15 minutes and an afternoon depending on how clean your existing data is.
How different teams put this to work
Lead capture for ads
Replace ugly web lead forms with a 30-second WhatsApp Flow on every click-to-WhatsApp ad. The common failure mode we see is over-templating — sending the same broadcast to every segment. The teams that outperform run at least three variants keyed to recency, spend tier, and language, and they measure reply-rate not open-rate.
Appointment booking
Service + slot picker for clinics, salons, real-estate visits and consultations. The common failure mode we see is over-templating — sending the same broadcast to every segment. The teams that outperform run at least three variants keyed to recency, spend tier, and language, and they measure reply-rate not open-rate.
KYC & onboarding
Collect documents, photos and structured data for fintech, lending and insurance journeys. The common failure mode we see is over-templating — sending the same broadcast to every segment. The teams that outperform run at least three variants keyed to recency, spend tier, and language, and they measure reply-rate not open-rate.
Returns & RTO reduction
Confirm COD orders and capture reason-for-return in a structured 2-screen flow. The common failure mode we see is over-templating — sending the same broadcast to every segment. The teams that outperform run at least three variants keyed to recency, spend tier, and language, and they measure reply-rate not open-rate.
NPS & CSAT surveys
1–10 ratings, multi-select drivers and free-text feedback in under a minute. The common failure mode we see is over-templating — sending the same broadcast to every segment. The teams that outperform run at least three variants keyed to recency, spend tier, and language, and they measure reply-rate not open-rate.
Catalogue browsing
Show categories, products and add-to-cart inline with native image carousels. The common failure mode we see is over-templating — sending the same broadcast to every segment. The teams that outperform run at least three variants keyed to recency, spend tier, and language, and they measure reply-rate not open-rate.
Buyer’s checklist
- • Official Meta Tech Partner — templates approve faster and account is not at ban risk.
- • Native growth teams data model — no glue-code to import contacts, orders, or bookings.
- • Green-tick support with a clear submission checklist and Meta-side follow-up.
- • Conversation-based pricing that matches WhatsApp’s own billing model, not per-message surcharges.
- • Human handoff with unread routing, so qualified replies never sit in a bot loop.
- • Audit log & role-based access — required for regulated enterprise buyers.
Common pitfalls
- • Broadcasting cold lists — quickest way to a quality-rating downgrade and eventually a template ban.
- • Skipping opt-in capture — makes every future utility template harder to approve.
- • Treating WhatsApp as a one-way channel — the platform penalises accounts with low reply-rate.
- • Running only one template variant — you leave 20–40% of lift on the table.
- • Not routing hot conversations to a human within 5 minutes — kills conversion by up to half.
What to measure after launching whatsapp flows — app-like forms inside chat
Week 1 signal
Track template approval time, first-reply latency, delivered-rate, and the first 100 customer replies. For growth teams, the fastest warning sign is not low opens; it is customers replying with confusion because the trigger, offer, or handoff promise was not specific enough.
Month 1 signal
Compare reply quality across Visual Flow Builder, All input types, E-commerce ready, Booking flows. The best-performing growth teams teams keep the highest-intent replies visible to managers, then rewrite templates around real customer language instead of internal terminology.
Scale signal
Once Pick a template → Design screens visually → Wire to your stack → Trigger from anywhere is stable, scale by segment rather than volume. Add new audiences only when opt-in source, template intent, agent ownership, and conversion tracking are all mapped.
Search-quality notes for this workflow
This page is intentionally built around whatsapp flows — app-like forms inside chat rather than a generic WhatsApp marketing overview. The content references the actual workflow, the growth teams audience, implementation steps such as Pick a template, Design screens visually, Wire to your stack, Trigger from anywhere, and use cases like Lead capture for ads, Appointment booking, KYC & onboarding, Returns & RTO reduction. That specificity helps buyers, internal teams, and search engines understand why this page deserves to exist separately from broader WhatsApp CRM, broadcast, chatbot, and automation pages.
What WhatsApp Flows actually replaces
WhatsApp Flows is a native multi-screen form runtime inside the WhatsApp client. It replaces three things: (1) the "click this link, fill this Typeform, come back" handoff that loses 60% of users, (2) branching chatbot menus that scroll for eight bubbles, and (3) OTP-secured mini-webviews for KYC and applications. Because the UI renders inside WhatsApp, conversion on a Flow is consistently 2–4× the equivalent web form on mobile.
Anatomy of a Flow (screens, data, endpoints)
| Piece | Purpose | Gotcha |
|---|---|---|
| Flow JSON | Declarative screen + component definition | Versioned per publish; live edits require re-approval |
| Screens | Ordered UI steps (max 10) | Each screen has a hard 4KB payload limit |
| Components | TextInput, Dropdown, RadioButton, DatePicker, Footer | No free HTML — component palette is fixed |
| Data endpoint | Your HTTPS URL for dynamic screens | Must respond within 10s or Meta aborts the Flow |
| Encryption | RSA public-key encryption on payloads | Rotate keys quarterly; Meta pins them |
| Completion | flow_response webhook with final payload | Reconcile to a business record; do not trust client state |
Highest-ROI use-cases in 2026
- Lead qualification — 4-screen quiz replaces a landing page. Conversion 38% vs 12% on web.
- Appointment booking — DatePicker + slot dropdown; no calendar link.
- KYC / document upload — encrypted, Meta-hosted, GDPR-friendly.
- NPS + long-form feedback — completion rate 3× vs external survey.
- Insurance / loan application — multi-step form with computed eligibility on the endpoint.
Constraints Meta doesn't advertise
Launch checklist
- Design in the Flow Builder (WhatsApp Manager) — export JSON to source control.
- Stand up the data endpoint; sign responses with your RSA private key.
- Submit for Meta review — turnaround 1–3 business days.
- Publish to a single template first; A/B against the equivalent link-out form.
- Wire
flow_responsehandler; retry on failure with idempotency key.
Related: Cloud API · Chatbot · Automation.
Ready to ship on WhatsApp?
Talk to our team about plans, onboarding and how LandinChat fits your stack.