Blog / API & technical

WhatsApp Flows: the native forms you fill out in chat

Every time you send an external link in chat—"fill out the form here"—a share of customers gets lost along the way: the page loads slowly, the form asks for too much, the phone rings and that's the end of it. WhatsApp Flows exists to close that gap: the form opens inside WhatsApp, with native screens, and the customer completes it without ever leaving the conversation.

What WhatsApp Flows is

It's a feature of the WhatsApp Business Platform—Meta's official API—that lets you build structured, screen-based experiences inside the chat: forms with text fields, dropdown menus, multiple choices, date pickers, consent checkboxes. The customer receives a message with a button, taps it, and a native panel opens that guides them step by step; at the end, the completed data reaches your systems.

Flows come in two variants. Static ones simply collect data with predefined screens and fixed navigation: perfect for contact forms and surveys. Dynamic ones talk to an endpoint of yours in real time: they can show the slots actually available for a booking, validate a customer code, change the following screens based on previous answers.

The difference compared to an external link is all about friction: no loading, no app switching, the interface is the familiar WhatsApp one. And compared to a free conversation, the Flow collects structured data: not "around 5, maybe Thursday," but a date and time chosen from a calendar.

The use cases that pay off the most

Lead generation

The classic "name, need, budget" form inside the chat, perhaps tied to a Click to WhatsApp campaign: the ad opens the conversation, the Flow qualifies. Closed-choice fields make leads immediately sortable by priority.

Bookings and appointments

Service, date, time, optional preferred operator: with a dynamic Flow the customer sees only the slots that are actually free, and the booking comes in already clean, without the three back-and-forth messages of "can Thursday at 3 p.m. work?"

Surveys and feedback

A rating from 1 to 5, a multiple choice, an optional free-text field: a survey that opens inside the chat gets completed far more willingly than a link to an external questionnaire. Useful after a purchase, a delivery, or an appointment.

Other uses that work

• Event registration: seats, preferences, and consent on a single screen.
• Structured quote requests: dimensions, quantities, timelines—everything you ask for today in five messages.
• Profiled opt-in: the customer chooses which communications to receive (offers, news, reminders).
• Guided product selection: closed-choice questions that lead to the right model, the way a salesperson would.

How to build a Flow with the official API, in 5 steps

1. Start from the goal (and cut the fields)

Decide what the Flow should produce—a qualified lead, a booking, a vote—and ask only for the essentials: every extra field costs completions. The rule of thumb: if a piece of data you can get later, in conversation, don't put it in the form.

2. Build the screens in the Flow Builder

In WhatsApp Manager—inside Meta Business Manager—there's the Flow Builder: a visual editor where you compose the screens with ready-made components (text, fields, pickers, buttons) and instant preview. Under the hood, each Flow is a JSON document, the Flow JSON: developers can write it directly, version it, and manage it via the API.

3. Connect the endpoint (only for dynamic Flows)

If the Flow needs to show real-time data—availability, prices, personalized content—you need an endpoint that responds to the screens' requests. Meta requires the exchange to be encrypted: it's the most technical step and typically involves a developer. For static forms, you skip it entirely.

4. Test in preview and publish

Every Flow starts as a draft: you try it in preview, send it to test numbers, check that the data lands where it should. Once published it can no longer be modified—to change it you create a new version—so it's worth testing well beforehand.

5. Send it: template or reply in conversation

A Flow travels inside a message with a dedicated button. Two vehicles: a Meta-approved template, so you can start the conversation yourself even in a mass campaign, or an interactive message inside the 24-hour window, when it's the customer who has written to you. Upon completion, the filled-in data reaches you via webhook, ready for CRM and automations.

Flows live only on the official API: the first step is having your number on the WhatsApp Business Platform. With SendApp Official you connect it with guided onboarding and manage templates and campaigns—the vehicles that carry Flows to customers—paying only Meta's rates, with no markups on messages.

Best practices: forms people actually finish

• One screen, one task: better three light screens than one with ten fields.
• Clear labels and closed options where you can: choice menus get completed faster than free fields and produce clean data.
• Close with a summary: a final screen showing what was entered reduces errors and second thoughts.
• Immediate follow-up: upon completion, send a confirmation in chat right away—a filled-out Flow that falls into silence wastes everything.
• Explicit consent when collecting personal data: a dedicated checkbox in the Flow, with a reachable privacy notice (GDPR).
• Measure the drop-off point: if many people stop at the same screen, the problem is almost always one field too many.

One last thing: the Flow collects, but it doesn't converse. The strong combination is with an AI agent that watches over the chat: it answers questions, proposes the Flow at the right moment—"if you want, I'll set up an appointment for you: pick a date and time here"—and takes the conversation back over after completion. With SendApp the agent is trained on your content and the contacts end up in the CRM, tagged and ready for follow-up.