WhatsApp Flows Guide: In-Chat Forms for Indian Businesses

WhatsApp Flows are native forms that open inside a WhatsApp chat. The customer taps a button, fills in one or a few short screens (text boxes, dropdowns, date pickers, checkboxes) and submits without leaving WhatsApp. They are part of the WhatsApp Business Platform, not the free WhatsApp Business app, and they suit short, structured questions; for long applications, payments or heavy document uploads, a good website form link is often still the better choice.

This guide covers what Flows are, where they help Indian businesses, how they compare with a form link, how to design one people finish, and the limits that rarely come up in a sales demo.

What WhatsApp Flows actually are

Meta introduced Flows in 2023 so businesses could collect structured information inside the chat. Each Flow is described in a JSON file (Meta calls it Flow JSON) that sets out the screens, the fields on each screen and what happens when the customer taps the final button. You can design one in WhatsApp Manager, which includes starter templates, or build it through the Flows API.

For the customer, it goes like this:

1. A message arrives with a button such as “Get a quote” or “Book a visit”.
2. Tapping it opens a full-screen form over the chat.
3. They move through the screens and tap the final button.
4. The form closes, a short summary appears in the chat, and your system receives the answers through a webhook.

There are two kinds. A static Flow has fixed questions and options and sends the answers back on submission. A dynamic Flow talks to your own server (Meta calls it an endpoint) while the customer is filling it in, so it can show live slots, check a PIN code against your delivery area or change the next screen based on an answer. Dynamic Flows are developer work: the endpoint must handle encrypted requests and reply within seconds.

A naming trap

Many WhatsApp tools, ZupiChat included, call their chatbot builder a “flow builder”. That builds a conversation out of messages, buttons and lists, one question at a time. Meta’s WhatsApp Flows are a different thing: a native form screen. Both are useful. When a vendor says “we support flows”, ask which one they mean, and ask to see submitted answers land on a real contact record.

How a Flow reaches the customer, and what it costs

• Inside the 24-hour customer service window. If the customer has messaged you in the last 24 hours, you can send the Flow as an interactive message. As of 2026, Meta does not charge for these service replies.
• Outside the window. You need an approved message template with a Flow button. Meta charges per delivered template, at a rate that depends on whether it is classed as marketing, utility or authentication.

Meta does not charge separately for the Flow itself; you pay for the message that carries it, plus your software provider’s fee. Rates and free windows change, so check our WhatsApp Cloud API pricing guide for India before you plan volume.

Use cases that fit Indian businesses

Lead qualification

A coaching institute asks for class, board and preferred batch timing. A real estate developer asks for budget band, configuration and move-in timeline. A B2B supplier asks for product, monthly quantity and whether the buyer is GST-registered. Leads from click-to-WhatsApp ads fit well: the person has just messaged you, so the service window is open and the Flow can go out at once. Your sales team then calls ready buyers first instead of asking the same five questions on every call.

Appointment requests

Clinics, salons, diagnostic labs and car service centres can collect the service, a preferred date and a time band on one screen. A static Flow with a date picker and a morning, afternoon or evening choice is enough for most small businesses, with staff confirming the exact time. Live slots need a dynamic Flow connected to your calendar or booking software.

Feedback after a sale or service

One screen: a rating, a checklist of what went wrong (late, damaged, wrong item, staff behaviour) and an optional comment. It takes seconds, and because the answer arrives against the customer’s number, your team knows exactly whom to call back.

KYC-lite details

Insurance advisors, rental businesses, admissions teams and recruiters often need basic details before the formal paperwork: name as on documents, date of birth, city, PIN code, occupation and preferred language. A Flow collects this neatly. What it should not collect is the sensitive part. Meta’s WhatsApp Business Messaging Policy restricts asking for items such as full card numbers, bank account numbers and national ID numbers, and Aadhaar has its own legal limits on who may collect and store it. Keep those steps on a proper KYC process, and read our DPDP Act and WhatsApp compliance guide for the consent side. The DPDP rules are being phased in as of 2026, so confirm your obligations with a lawyer.

Other good fits: warranty registration, event sign-ups, dealer onboarding, job screening questions and complaint tickets with a category and order number.

WhatsApp Flow vs sending a website form link

The fair comparison has three options, because a chatbot asking questions one message at a time is often the cheapest route.

A Flow’s real advantage is less friction. On a patchy mobile connection a website form has to load, the customer retypes a number you already have, and some never come back to the chat. A Flow opens inside WhatsApp and hands you the answers against a known number.

The website form still wins when the form is long (a loan or admission application with several documents), when payment is part of the same step, when you want your own branding and analytics, or when the same form must work from email, SMS and QR codes. If your mobile form already converts well, do not rebuild it as a Flow just because Flows are new.

When you do not need a Flow at all

If you get a handful of enquiries a day and someone replies to each, a staff member asking three questions in chat is fine. On the free app, Flows are not available, and moving to the API only for forms rarely pays off; our WhatsApp Business app vs API comparison explains the trade-off. If you need just two answers, a lead-generation chatbot with buttons is quicker to build. And no form fixes a weak offer.

Design tips: short screens, few fields

Most Flows that fail are a paper form pasted into WhatsApp. Check these before you publish:

1. Three screens or fewer for most jobs, with three to five fields per screen.
2. Do not ask for what you already have. WhatsApp gives you the number; pass in the name and other known details when you send the Flow so they arrive prefilled.
3. Choices beat typing. Use radio buttons, dropdowns and date pickers wherever answers are fixed. Typing on a small keyboard is where people drop off.
4. Easiest question first: the service they want, not their income.
5. Name the button after the outcome, such as “Get my quote”, not “Submit”.
6. Show progress in screen titles: “Step 2 of 3”.
7. Use the right input type (number, email, phone) so the correct keyboard appears.
8. One Flow per language rather than English and Hindi mixed on one screen.
9. Confirm after submission with a message saying what happens next and how to reach a person.
10. Test on a low-cost Android phone before sending it to your whole list.

Limits and risks to know before you build

• API only. As of 2026, Flows need the WhatsApp Business Platform; the free Business app cannot send them.
• Devices and app versions. Customers on old WhatsApp versions may not be able to open a Flow, and behaviour on WhatsApp Web and desktop can differ from phones. Keep a fallback link or a human reply ready.
• Fixed building blocks. You get Meta’s components, not your own design. Meta caps components per screen, label lengths and list options, and newer pieces such as photo and document upload depend on the Flow JSON version, so read the current reference rather than an old blog post.
• Published means frozen. A published Flow cannot be edited; you clone it, change the copy and publish again.
• Endpoints need care. Meta monitors endpoint errors and response times and can throttle or block a Flow whose endpoint keeps failing.
• Features vary. Some capabilities roll out by region, API version or account, so confirm what your number supports before promising anything to a client.
• Storage is your job. Answers arrive in a webhook. If nothing saves them against the contact, they are lost. Treat them as personal data: collect only what you need.

If you are choosing a tool, test the whole path rather than the demo: send a Flow, submit it from a real phone and check that the answers reach the contact record, apply the right tag and land with the right person in your team inbox. Compare that against the ZupiChat features page, which covers the shared team inbox, visual chatbot builder, contact tags and segments, and a developer API with webhooks.

The short version

• WhatsApp Flows are native in-chat forms on the WhatsApp Business Platform; the free Business app cannot send them.
• They suit short, structured questions: lead qualification, appointment requests, feedback and basic pre-KYC details.
• A website form link is still better for long forms, payments, document-heavy applications and anything that must work outside WhatsApp.
• Keep Flows to a few screens with few fields, never ask for sensitive IDs, and plan the questions carefully, because a published Flow cannot be edited.

Frequently Asked Questions

Are WhatsApp Flows free to use?

Meta does not charge a separate fee for the Flow itself; you pay for the message that carries it. As of 2026, a Flow sent as a reply inside the 24-hour customer service window is not charged, while a Flow sent outside that window needs an approved template and is charged per delivered message according to its category. Your WhatsApp software provider may charge its own subscription on top, so check both before planning volume.

Can I use WhatsApp Flows with the free WhatsApp Business app?

No. As of 2026, Flows are a feature of the WhatsApp Business Platform, which you use through the Cloud API directly or through a software provider. The free WhatsApp Business app offers a catalogue, quick replies and greeting and away messages, but not native Flows. If you are on the app and only need a form now and then, a short, mobile-friendly website form link is a sensible and cheaper choice.

Do I need a developer to build a WhatsApp Flow?

Not always. A static Flow with fixed questions can be designed in the builder inside WhatsApp Manager, which includes starter templates, and many teams manage that without code. You still need somewhere to receive and store the answers, usually a CRM that reads the webhook. A dynamic Flow that shows live slots, checks PIN codes or looks up orders does need a developer, because your server must handle encrypted requests and reply within seconds.

Can a WhatsApp Flow collect Aadhaar, PAN or bank details?

Be very careful. Meta’s WhatsApp Business Messaging Policy restricts requesting sensitive identifiers such as full card numbers, financial account numbers and national ID numbers, and Aadhaar has its own legal restrictions on collection and storage. Use Flows for basic pre-KYC details like name, city and PIN code, and move identity checks to a proper KYC process. Policies and rules change, so as of 2026 confirm with a lawyer before collecting anything sensitive.

Can I send a WhatsApp Flow in a broadcast campaign?

Yes, through an approved template with a Flow button, sent only to contacts who have opted in to hear from you. Each delivered template is charged by category, and marketing templates cost more than utility ones. Keep broadcast Flows especially short, because people who did not ask for a form are less patient than someone who has just messaged you. Send to a small segment first and check completion before sending to your full list.