Skip to content
Meta Business PartnerQuick answer inside

How do WhatsApp Flows work?

WhatsApp Flows turn a static chat into a structured, multi-screen mini-app that runs entirely inside the conversation. Instead of pasting a link and hoping a customer taps out to a browser, you send a single button that opens a native sequence of screens — date pickers, dropdowns, text fields, radio buttons, chips — collects the answers, and hands them straight back to your backend. Because the customer never leaves WhatsApp, logs in again, or waits for a page to load, completion rates on Flows routinely beat the web forms they replace. For Indian businesses running appointments, onboarding, lead qualification or KYC, that difference in drop-off is the whole point.

Quick answer

WhatsApp Flows are interactive, multi-screen forms (pickers, dropdowns, inputs) that run inside the chat window. You send a button, the customer completes structured screens without leaving WhatsApp, and the responses post to your backend via an encrypted endpoint — ideal for bookings, lead capture, and KYC, with higher completion than external web forms.

What a Flow actually is

A Flow is a small, guided app that lives inside a WhatsApp message. When you send it, the customer sees a button such as "Book appointment" or "Complete sign-up." Tapping it opens a full-screen sequence of screens rendered natively by WhatsApp — no browser, no separate app, no login. Each screen is built from standard components you control: single- and multi-select dropdowns, radio buttons, checkboxes, chips, calendar and date pickers, short and long text inputs, and a footer button to move forward. The customer works through the screens one at a time, WhatsApp validates required fields as they go, and on the final screen they submit. It feels less like filling a form and more like tapping through a familiar in-chat wizard, which is exactly why people finish them.

  • Opens in-chat as a full-screen, native experience — no external browser or app
  • Built from pickers, dropdowns, checkboxes, date pickers, and text inputs
  • Fields are validated inline before the customer can continue
  • Ends with a single structured submission back to your business

How the data reaches your backend

When a customer completes a Flow, their answers don't arrive as loose chat text — they come back as one structured payload your systems can read directly. For dynamic Flows, WhatsApp also talks to a data-exchange endpoint you expose while the customer is mid-task: as they move between screens, WhatsApp calls your endpoint, and your server responds with the next screen's content or live data such as the appointment slots still open today. Every exchange is protected with end-to-end encryption using a public/private key pair you register, so sensitive fields are encrypted in transit and only your business can decrypt them. InfiQ builds and hosts that endpoint, registers the keys, and maps the returned fields into your CRM, calendar, or order system, so a finished Flow becomes a real booking or qualified lead automatically.

Static vs dynamic Flows — which to use

Flows come in two shapes, and picking the right one keeps your build simple. A static Flow has every screen and option fixed when you publish it; nothing changes per customer, so it needs no live backend call and is fast to launch. Use it for standard sign-ups, feedback surveys, and enquiry forms where the questions are always the same. A dynamic Flow calls your endpoint while the customer is stepping through it, letting screens show current data or adapt based on earlier answers — essential when you need real-time availability, personalised options, or branching logic. Most businesses start with a static Flow to prove the use case, then move to dynamic once live data or personalisation matters.

  • Static: all screens fixed at publish time; no live endpoint; quickest to launch
  • Dynamic: calls your endpoint mid-flow for live data and branching
  • Static suits sign-ups, surveys, fixed enquiry forms
  • Dynamic suits real-time slot booking, personalised offers, conditional screens

Where Flows earn their keep

Flows shine wherever a plain chat thread would turn into a messy back-and-forth. Appointment and reservation booking is the clearest win: the customer picks a service, a date, and a time in three tidy screens instead of typing free-form messages your team has to interpret. Lead capture and qualification benefit too — a Flow asks the exact fields your sales team needs, so every lead arrives complete and structured rather than half-answered. Onboarding and KYC-style collection, where you need identity details, addresses, and consents captured accurately and securely, fit Flows well thanks to the encryption model. Feedback and CSAT surveys, event registrations, and order or reorder forms round out the common patterns. In each case the gain is the same: fewer steps, less friction, cleaner data, and noticeably lower drop-off than sending people to an external page.

Launching a Flow the right way with InfiQ

Getting a Flow live involves more than drawing screens. You need a WhatsApp Business Account in good standing, the Flow built and validated, encryption keys generated and registered, a reachable endpoint for any dynamic behaviour, and — for proactive sends — an approved template of the right category to carry the Flow button. As an official Meta Business Partner, InfiQ handles that setup end to end: we build and host the endpoint, register keys, get your carrier template approved, and wire completions into your existing tools. You keep full ownership of your WhatsApp Business Account and BSUID, so the number, the Flows, and the data they collect stay yours. Billing stays honest too — the Flow itself carries no extra fee; you only pay for the template message that delivers it, priced per delivered message by category, shown as transparent ₹ pricing (ex-GST).

Do this with InfiQ

Talk to InfiQ

Get a straight answer for your setup

Tell us what you’re trying to do — a WhatsApp specialist replies within one working day.

Step 1 of 2
WhatsApp

Protected by invisible spam checks · replies within 1 working day

Frequently asked questions

Do WhatsApp Flows work without any coding?+
Static Flows — where every screen and option is fixed at publish time — can be built and launched with almost no code, which covers many booking, survey, and sign-up use cases. Dynamic Flows, which show live data such as real-time appointment slots or personalise later screens, need a data-exchange endpoint your server can respond to. InfiQ builds and hosts that endpoint for you, so even dynamic Flows don't require you to run infrastructure yourself.
Are WhatsApp Flows secure enough for KYC and personal details?+
Yes. Flow data is protected with end-to-end encryption using a public/private key pair you register with WhatsApp, so fields like ID numbers, addresses, and contact details are encrypted in transit and only your business can decrypt them. This is why Flows are widely used for onboarding and KYC-style collection where a plain chat message would be inappropriate.
How are WhatsApp Flows billed?+
There is no separate charge for the Flow itself. Since 1 July 2025, WhatsApp bills per delivered message by template category — marketing, utility, or authentication. You pay for the template message that carries the Flow button, priced on its category. A Flow the customer opens as a reply within the free 24-hour service window after they message you doesn't add a send cost. InfiQ shows these as transparent ₹ pricing, ex-GST.
Why do Flows convert better than a link to a web form?+
An external link asks the customer to leave the chat, load a page, and sometimes log in or re-enter details — every extra step loses people. Flows keep the entire task inside WhatsApp with app-like screens and validated inputs, so there's no tab switch and no re-authentication. Fewer steps and less friction mean fewer drop-offs on multi-screen tasks like bookings and onboarding.
Can a Flow send responses straight into my CRM or calendar?+
Yes. When a customer completes a Flow, the answers arrive as a single structured payload rather than loose chat text. InfiQ maps those fields to your CRM, booking calendar, or order system so a completed Flow becomes a real appointment, a qualified lead, or an updated record automatically, without manual re-keying.
What's the difference between a static and a dynamic Flow?+
A static Flow has all screens and options fixed when you publish it — simplest to build and best when the content doesn't change per customer. A dynamic Flow calls your endpoint while the customer is stepping through it, so screens can show live data (like today's open slots) or adapt based on earlier answers. Choose static for fixed sign-ups and surveys, dynamic when content must be current or personalised.
What do I need in place before I can launch a Flow?+
You need a WhatsApp Business Account in good standing, the Flow itself built and validated, encryption keys registered, a reachable data-exchange endpoint for dynamic Flows, and an approved template to carry the Flow button for proactive sends. InfiQ, as a Meta Business Partner, sets up the endpoint, keys, and template approval so you launch a production-ready Flow rather than a prototype.
Do I keep ownership of my WhatsApp account and data?+
Yes. With InfiQ you retain full ownership of your WhatsApp Business Account and BSUID, so the number, the Flows you build, and the customer data collected through them belong to you and aren't locked inside an agency's account.

Launch a WhatsApp Flow that customers actually finish

Talk to InfiQ, an official Meta Business Partner, and we'll build, host, and connect your first booking or lead-capture Flow end to end — with transparent ₹ pricing and full BSUID ownership.