WhatsApp Flows is a feature of the official WhatsApp Business API that opens interactive screens, such as forms and date pickers, without the customer leaving the chat. With WhatsApp Flows, a business collects data, books appointments and qualifies leads without sending the customer to a website.
The feature tackles the back-and-forth of loose questions in customer service automation. The sections below cover how it works, how it differs from a menu chatbot, form and booking use cases, requirements, creation, sending, costs in 2026, best practices and metrics.
Key Takeaways
- Use WhatsApp Flows to collect structured data; leave open conversation to AI.
- Prefer a Flow without an endpoint when there is no data to look up in real time.
- Test everything in draft: a published Flow cannot be deleted, only deprecated.
- Redo the budget: from October 1, 2026, service messages are charged.
What WhatsApp Flows Is and How It Works
A Flow does not open a new conversation: it fits a task with a beginning, middle and end into the chat that is already happening. Behind the screens there are two technical elements, the Flow JSON and, when needed, the endpoint.
Definition and Launch
According to Meta’s official Flows guide, Flows are structured interactions made up of screens, components and features. Each Flow handles a single task, such as booking an appointment, and a tap on a button opens the screens inside WhatsApp customer service.
Meta announced the feature in September 2023 at its Conversations event in Mumbai, according to the Meta newsroom announcement, with examples such as choosing a train seat, ordering a meal or booking an appointment without leaving the chat.
Flow JSON and Screen Components
The Flow JSON is the file that defines the screens and the navigation between them. Each screen brings together ready-made components, chosen according to the data to be collected. The most common in forms and booking flows are:
- Text fields: name, email, ID number or free-form notes.
- Dropdowns and radio buttons: choice of location, service or plan.
- Checkboxes: several answers to the same question, such as interests.
- Date picker and calendar: appointment day or booking period.
- Consent (opt-in): agreement to be contacted or to data use.
The logic differs from building a WhatsApp chatbot. In a chatbot, the team writes a dialogue, message by message. In a Flow, it designs screens, and the customer sees all the fields for that step at once.
Flows With and Without an Endpoint
Without an endpoint, the Flow’s options are fixed and the response is only sent at the end. With an endpoint, the Flow exchanges data with the business’s server between screens, to show available time slots, stock or a quote calculated on the spot.
The official best practices recommend a Flow without an endpoint whenever live data is not needed. Fewer moving parts mean fewer points of failure, and the automation is easier to maintain.
WhatsApp Flows vs. Menu Chatbots
Both features automate conversations, but they solve different problems. Understanding that split avoids a common mistake in AI customer service projects: forcing a form where a conversation belongs, or the other way around.
Differences in the Customer Experience
A menu-based chatbot asks one thing per message and depends on the customer typing the right option. A Flow brings several fields together on one screen, guides the input and returns the answers all at once.
| Criterion | Menu chatbot | WhatsApp Flows |
|---|---|---|
| How data is collected | One question per message | Several fields on the same screen |
| Field validation | Depends on rules applied to typed text | Dedicated components for each data type |
| Choosing a date | Customer types the date | Date picker or calendar |
| When to use | Triage and open conversation | Sign-ups, bookings and quotes |
| Where the response arrives | Scattered across the chat history | In structured format, via webhook |
In short, a menu chatbot works best for open conversation and quick triage. A Flow wins when the task requires structured data, such as a date, location, document or choice between plans with different rules.
How to Combine Flows With AI Agents
An efficient division of labor combines both. The AI agent understands the request in free text and, when it is time to collect structured data, sends the Flow. The response goes back to the agent, which confirms it and continues the conversation.
Teams that create AI agents for WhatsApp can treat the Flow as one of the agent’s tools. The practical rule is simple: the AI converses, the Flow collects.
An example: the customer writes that they want to book a car service on Friday. The agent identifies the service, sends the booking Flow and, when the response arrives, confirms the date in the chat and records the appointment.
Forms and Bookings With WhatsApp Flows
Official use cases range from booking appointments to generating leads and running surveys. What they share is replacing an exchange of many question-and-answer messages with a short, guided task that has a clear start and finish for the customer.
Appointments and Reservations
Booking appointments on WhatsApp is the most cited use case. The customer chooses a location, service, date and an available time slot, looked up in the business’s system through the endpoint, and receives the confirmation in the chat.
On the WhatsApp Flows page, Meta cites a pharmacy chain that saw a 2.6x increase in appointments. Clinics, salons and auto repair shops, segments served by vertical AI agents, follow the same logic of scheduling with real availability.
Sign-Ups, Leads, Quotes and Surveys
The API organizes Flows into sign up, sign in, appointment booking, lead generation, contact us, customer support, survey and other. The list of Flow categories in the API shows that a WhatsApp form is not limited to scheduling.
The official guides include examples such as a pre-approved loan, an insurance quote, a personalized offer and purchase intent, which collects name, email and products of interest. That last one feeds the sales funnel with leads that are already qualified.
In a satisfaction survey, a single screen can ask for a rating from 1 to 5 and the main reason from a closed list, sent right after the interaction. With standardized options, the team compares locations and periods without rereading conversations.
Example of a Booking Flow
A booking Flow with an endpoint can be built in four screens, each with a single task:
- Service and location: radio buttons or a dropdown, depending on the number of choices.
- Date: a date picker or calendar showing the available days.
- Time: options loaded by the endpoint from the real schedule.
- Summary: a review of the data before submitting, followed by confirmation in the chat.
If the business does not need to show live time slots, the third screen can become a choice of period, such as morning or afternoon, and the Flow no longer needs an endpoint.
How to Create a WhatsApp Flow: Requirements and Publishing
Creating a Flow does not necessarily require coding skills. First, however, the account must meet some requirements, a Flow with an endpoint has its own technical checklist, and once published, the Flow follows strict editing rules.
Account and Endpoint Requirements
According to getting started with Flows, the business must be verified and have high message quality to send Flows. Low quality gets in the way of sending and raises the risk of number restrictions, and forms sent to people who did not ask for them make the problem worse.
With an endpoint, the list grows. The endpoint implementation page sets a 10-second timeout per request, and health monitoring lists what must be ready before publishing:
- A generated key pair, with the public key uploaded and signed.
- An HTTPS server with a valid TLS certificate, ready to receive POST requests, and encrypted data.
- A Meta app linked to the Flow and a valid Flow JSON.
- A working health check.
- A subscription to Flows webhooks.
Without these items, a Flow with an endpoint cannot be published. And a slow or offline server breaks the experience right when the customer is in the middle of filling out the form.
Three Ways to Build a Flow
The WhatsApp Flows page describes three official ways to create a WhatsApp Flow:
- Ready-made templates in WhatsApp Manager: simple forms, such as sign-ups or surveys, with no code.
- Help from partners: a Flow integrated with systems without building a technical team.
- Flow Builder or API: teams that code and need an endpoint or custom rules.
A simple survey can start from a ready-made template. A booking flow with real time slots, however, needs an endpoint and therefore development work.
Lifecycle: Draft, Published and Deprecated
The Flow lifecycle has strict rules. In draft, a Flow is for testing only and can be deleted. Once published, it can no longer be deleted, only deprecated, which ends the use of that version.
Editing a published Flow sends it back to draft. The practical consequence is to test everything before publishing: copy, required fields, navigation between screens and the confirmation message that closes the task.
Sending a Flow and Receiving Responses
The Flow reaches the customer inside a message and returns to the business through a webhook. Both ends must be ready before the first send at scale, so that no response gets lost along the way.
Template With a FLOW Button or Interactive Message
When the business starts the contact, it uses a template with a FLOW button, whose text can have up to 25 characters, for example to re-engage a stalled lead in sales follow-up. That template goes through approval, according to the guide to sending Flows.
If the customer is already chatting, the business sends an interactive call-to-action message within the customer service window. For example, the customer asks about plans in the chat and then receives the quote Flow.
In both formats, the button text is the promise of the task. Short, specific labels such as “Book a time” or “Get a quote” fit the character limit and make clear what the customer will find when they tap.
nfm_reply Webhook and CRM Integration
The response arrives via webhook as an interactive message of type nfm_reply. The response_json field carries the completed data, ready to go to the calendar, the database or the sales system.
With a CRM integration, the lead enters the system with no manual data entry. Flows webhooks also report on status, errors, latency and endpoint availability.
A practical precaution is to send the customer a confirmation message as soon as the response is processed. If the destination system fails, the team needs a record of the response received to handle the case without asking for everything again.
How Much WhatsApp Flows Costs
Meta does not publish a specific rate for Flows. Meta charges per delivered message, based on the message category and the recipient’s country, according to the official WhatsApp pricing page: what is charged is the message that carries the form to the customer. So the cost depends on the message type and the send date.
Rules Through September 30, 2026
A template with a FLOW button is charged by the category it was approved in: marketing, utility or authentication. Rates vary by market and should be checked in the official price list before any budget.
Through September 30, 2026, service messages (non-template) are not charged, and utility templates sent within the customer service window are not charged either. An interactive message with a Flow, since it is not a template, counts as a service message.
In practice, the budget for a Flow campaign starts from two calculations: the templates sent, multiplied by the category price in the customer’s market, and the messages exchanged inside the window, which follow the rule for each period.
Rules From October 1, 2026
According to Meta’s pricing page, from October 1, 2026, Meta charges for service messages at the same price as utility and authentication in each market. In Brazil, for example, that is R$ 0.035 per delivered message. Utility templates sent within the window are also charged.
Each phone number gets 1,000 free service messages delivered per month, with no rollover. Beyond that allowance, Flows sent as interactive messages within the conversation are charged, and volume weighs on the budget.
A Flow that completes a booking in a single response replaces several service messages, which helps keep customers engaged without inflating costs.
WhatsApp Flows Best Practices, Metrics and Health
A Flow is short by nature. The official rules exist so that the customer reaches the end of the task, and measurement shows whether that happens and whether the endpoint can handle the send volume.
Official Rules and Common Mistakes
Meta’s best practices bring together objective guidance for designing screens, valid for simple Flows and for those that use an endpoint:
- Time: the whole task should fit within 5 minutes.
- Focus: one task per screen, with up to 10 options.
- Dropdowns: only from 8 options up; below that, radio buttons.
- Promise: the first screen matches the button text.
- Closing: a summary screen and a confirmation message in the chat.
Common mistakes are the opposite of these rules: asking for data that will not be used, straying from the button’s promise and requiring login early, when it should come only if necessary and at the end.
Meta also recommends a minimal final payload and the sensitive flag on sensitive fields. That aligns with Brazil’s data protection law (LGPD), and similar rules apply under the GDPR in the EU; the same care applies to what AI chatbots store.
Completion Rate
A direct way to measure is to compare Flows sent with nfm_reply responses received in the same period. The ratio between the two is the completion rate: it shows how many customers reached the end of the task, and a drop points to where to review.
Since the Flows Metrics API, focused on endpoint performance, was deprecated on April 30, 2026, measurement is up to the business. It is worth cross-checking the rate against real conversions, such as appointments attended, and against other customer service metrics.
Endpoint Health: Throttled and Blocked
According to Meta’s health monitoring, an endpoint with failures moves the Flow to the Throttled state, limited to 10 sends per hour. If the problem continues, the Flow becomes Blocked and can no longer be sent or opened.
The recommended target is to respond in under 1 second. It is worth having a plan B: when the Flow fails, the conversation continues with a team member, a common setup in operations with multiple agents.
WhatsApp Flows FAQ
The answers below cover questions that come up when putting the first Flow into production, from device compatibility to consent and coexistence with the website.
Not on every device. According to the official Flows guide, the feature works on Android 6.0 or newer and iOS 12 or newer, but it does not open on linked devices such as WhatsApp Web. For customers on a computer, it is worth keeping a text alternative with a WhatsApp chatbot.
No. The official documentation describes creating and sending Flows only through the WhatsApp Business API platform, not through the app. Businesses on the WhatsApp Business app need to migrate or connect the number to the API before their first Flow.
The practical limit is the validity of the flow_token, the identifier of the Flow session. Meta’s best practices recommend keeping that validity between 2 and 3 days.
According to the Flow lifecycle, messages already with customers keep the old version. That is why reviews should happen before large sends, not in the middle of a campaign.
The WhatsApp Business Policy requires opt-in, with the number provided and the contact’s permission, and requires the business to honor opt-out requests. With opt-in, the first send goes out as an approved template with a FLOW button, as shown in the sending guide.
Not necessarily. A Flow shortens the path for people who are already on WhatsApp, coming from an ad, a conversation or a reminder, while the website remains useful for people who arrive from search. Journeys that happen entirely in the app, such as food delivery on WhatsApp, show where it delivers the most.
Next Steps With WhatsApp Flows
WhatsApp Flows turns sign-ups, quotes and bookings into short screens inside the chat, while open conversation stays with AI customer service. With service messages charged from October 2026, testing in draft, measuring completion and keeping the endpoint stable also affect the budget.
To run the official WhatsApp API with coexistence and AI agents that take actions in the CRM, talk to ConverZap.
