Key takeaways
- A WhatsApp Flow is a native form with one or more screens that opens on top of the chat.
- Flows collect structured data, text, dropdowns, dates, checkboxes, and return it as a single reply the business can process.
- Flows are a WhatsApp Business API feature; the free WhatsApp Business app cannot send them.
- Outside the 24-hour customer service window, a Flow must be sent through an approved template with a Flow button.
- Static Flows need no server; dynamic Flows call a business endpoint to fetch live data such as available slots.
WhatsApp Flows let a business open a real form inside a WhatsApp conversation. Instead of asking ten questions one message at a time, you send a single message with a button. The customer taps it, a full-screen form slides up, they fill it in and submit, and the chat carries on.
If you have ever booked a test drive, requested a loan callback or picked an appointment slot without leaving WhatsApp, you have probably used a Flow.
What exactly is a WhatsApp Flow?
A Flow is a structured, multi-screen experience that Meta renders natively in the WhatsApp app. Each screen can contain:
- Headings and body text
- Short and long text inputs (name, email, address, comments)
- Dropdowns, radio buttons and checkboxes
- Date pickers
- Opt-in checkboxes and links to your terms
- A footer button to move to the next screen or submit
The customer never visits a website, so there is no page load, no login and no drop-off from switching apps. When they submit, the answers arrive at the business as one structured reply.
How is a Flow different from a chatbot or a web form?
| Chatbot questions | Web form link | WhatsApp Flow | |
|---|---|---|---|
| Where it opens | In the chat, one message at a time | In the browser | Native screen inside WhatsApp |
| Fields per step | One | Many | Many, across multiple screens |
| Validation | Handled by bot logic | Handled by the site | Built into the form components |
| Drop-off risk | Rises with every question | Leaving the app | Lower, the customer stays in WhatsApp |
| Best for | Short, conversational qualification | Long or complex applications | Bookings, lead forms, surveys, sign-ups |
Chatbots and Flows work well together. A no-code chatbot can greet the customer and understand intent, then hand over to a Flow for the step that needs several fields at once.
What can businesses use WhatsApp Flows for?
Meta groups Flows into common use cases, and they map closely to what Indian businesses already do on WhatsApp:
- Lead generation: collect name, city, budget and product interest from a Click-to-WhatsApp ad in one step.
- Appointment booking: let patients, salon clients or test-drive customers pick a service, date and time slot.
- Sign-ups and registrations: webinar and event registrations, loyalty programme enrolment, demo requests.
- Surveys and feedback: CSAT and NPS questions after delivery, with optional comments. See our guide to WhatsApp customer feedback surveys.
- Customer support: structured complaint or return requests that capture order ID, reason and photos of the issue before an agent picks it up.
- Pre-sales qualification: loan eligibility, course counselling, property requirements.
How do WhatsApp Flows work technically?
There are two kinds of Flows.
Static Flows
Every screen and option is defined in advance in the Flow definition (a JSON document Meta calls Flow JSON). When the customer submits, the answers are delivered to your webhook. No server is needed while the customer is filling the form. Most lead forms, surveys and registrations are static.
Dynamic Flows (with an endpoint)
The Flow calls a secure endpoint you host to fetch or validate data while the customer moves between screens: for example, showing only the appointment slots still available, or checking a pincode against your delivery areas. Requests between WhatsApp and your endpoint are encrypted, so these Flows need a developer to set up. Chatbox AI's API and webhooks are the usual starting point for this kind of integration.
In both cases the submission comes back through the same webhook as normal messages, which means it can trigger the rest of your journey. If you are new to webhooks, read WhatsApp webhooks explained.
How do you send a WhatsApp Flow to a customer?
It depends on who started the conversation, the same rule that governs every WhatsApp Business API message.
- Inside the 24-hour customer service window (the customer messaged you recently), you can send the Flow as an interactive message with a button. No template approval is needed for that message. Learn more about the 24-hour window.
- Outside the window, you must send an approved template message that includes a Flow button. The template is charged by its category, marketing or utility, like any other template.
Flows are published from WhatsApp Manager. Once published, a Flow cannot be edited in place; you create a new version or clone it. Test drafts on your own number before you publish.
What are the best practices for WhatsApp Flows?
- Keep it short. Ask only what you need for the next step. Two or three screens usually beat six.
- Say why you are asking. A one-line explanation at the top of each screen ("We'll use your city to find the nearest showroom") improves completion.
- Pre-fill what you know. If the contact profile already has the customer's name or phone number, do not ask again.
- Confirm immediately. After submission, send a clear confirmation message with the booking details or the next step.
- Route the data. Save answers to contact attributes, tag the lead and assign it to the right agent in the team inbox.
- Respect consent. Collect only data you have a reason to hold, link to your privacy policy and follow WhatsApp opt-in rules before sending marketing templates later.
Are WhatsApp Flows right for your business?
Flows make sense when a conversation needs several pieces of information at once and customers are dropping off along the way. If your chatbot asks more than four questions in a row, or you are sending customers to a web form that few complete, a Flow is worth testing.
They sit alongside other interactive messages: reply buttons and list menus handle quick choices, Flows handle the data-heavy steps.
Chatbox AI is an official WhatsApp Business API platform that helps you connect Flows to chatbots, broadcasts and your team inbox. Start a 7-day free trial to try it on your own number, or compare plans on the pricing page.
Frequently asked questions
Meta does not charge separately for building or opening a Flow. You pay the normal message charge for the message that carries it: a marketing or utility template if you start the conversation, or nothing extra if you send it as a reply inside the customer service window.
Are WhatsApp Flows free to use? Meta does not charge separately for building or opening a Flow. You pay the normal message charge for the message that carries it: a marketing or utility template if you start the conversation, or nothing extra if you send it as a reply inside the customer service window.
Do I need a developer to build a WhatsApp Flow? Not for simple forms. Meta's Flow builder in WhatsApp Manager lets you assemble screens visually, and platforms like Chatbox AI help you trigger Flows from chatbots and broadcasts. Dynamic Flows that look up live data need a developer to build and host an endpoint.
What is the difference between a Flow and a chatbot? A chatbot asks questions one message at a time. A Flow shows a proper form with several fields on one screen, validation and navigation between screens. Many businesses use a chatbot to start the conversation and hand off to a Flow for the data-heavy step.
Can customers fill a Flow on WhatsApp Web? Flows are designed for the WhatsApp mobile apps. Support on other WhatsApp clients has changed over time, so test on the devices your customers actually use and give them a fallback, such as a chatbot question, if a Flow does not open.
Where do the answers from a Flow go? When the customer submits, WhatsApp sends the answers to the business as a structured reply through the API webhook. Your platform can then save them to the contact profile, tag the lead, assign an agent or push the data to a CRM.
