WhatsApp Flows (Beta): build forms inside the chat

Build a WhatsApp Flow in SendSeven (Beta): start from a template or the AI, add screens and fields, save answers to contacts, test, publish and send.

A WhatsApp Flow is a form that opens right inside a WhatsApp chat. Your customer fills in one or more screens and sends all answers back in one go. More in the glossary.

Completed flows are free during the beta. Every flow you send counts as one message from your plan's message allowance, just like any other WhatsApp message, and Meta's fees apply as usual. Once WhatsApp Flows is generally available, an additional charge per completed flow will apply. We'll let you know well in advance.

A WhatsApp Business API number connected to SendSeven. No number yet? Start with the WhatsApp setup guide.

A plan that includes WhatsApp. Static flows work on every such plan; Create with AI needs Professional or higher, dynamic flows need Scale or higher.

About 15 minutes for a first flow. Starting from a template is the quickest way.

SendSeven WhatsApp Flows tab marked Beta with the buttons Create WhatsApp Flow, Create with AI and Templates and a draft static flow in the list

SendSeven Templates dialog for WhatsApp Flows with starter forms: appointment request, lead qualification, satisfaction survey, newsletter preferences, newsletter sign-up and callback request

Create with AI is available from the Professional plan and builds static flows. It uses AI Credits, only for successful runs; the button shows the cost before you start.

Create with AI dialog in SendSeven with a written description of an event registration form, example prompts, a flow name and the language setting

New WhatsApp Flow dialog in SendSeven with the name Event registration and the category Sign up

Text: heading, subheading, body text, caption and rich text

Inputs: short and long answers, date picker, calendar and opt-in checkbox

Choices: dropdown, single choice, multiple choice and chips

Media: image, image carousel, photo upload and document upload

Buttons and navigation: footer button, link and navigation list

Logic: if/else and switch, to show parts of a screen only for certain answers

Counters show WhatsApp's limits while you work, for example 5/50 components on a screen. In the screen settings you set the title in the top bar and mark the screens that end the flow.

SendSeven WhatsApp Flow editor with the screen list, the components of screen 2, the screen settings Last screen and Counts as success, and a phone preview

Input settings in the WhatsApp Flow editor: Prefill from contact set to First name and Save the answer to the contact field First name

Footer button settings in the WhatsApp Flow editor: label Continue, When tapped set to Go to screen, next screen SESSION

Check your flow panel in SendSeven with 3 errors and 0 warnings and the note Errors block publishing

WhatsApp Flow settings in SendSeven: type Static, language EN, button text Save your seat and Tag contact on completion with the tag Marketing selected

Approximate phone preview of a WhatsApp Flow screen Choose a session with a Register button

One exception: a flow linked to an approved message template keeps opening the old version until you edit the template and submit it to Meta again. The publish dialog lists the templates this affects.

Which route fits depends on whether the 24-hour customer service window is open, which happens when the customer has written to you.

Most forms work as static flows. Dynamic flows load live data on every screen.

Comparison of static and dynamic WhatsApp Flows in SendSeven

First screen, filled when the flow is sent

Contact fields and values sent with the flow

Contact profile, custom-field options, lists, tags, catalogue products or your own webhook

Meta sets these limits for every flow. The editor shows them as counters, so you see where you stand while you build.

Exactly one per screen, label up to 35 characters

Text up to 120 characters, up to 5 per screen

Up to 2 per screen, link text up to 25 characters

Up to 3 per screen, JPEG or PNG, ideally 300 KB or less each

One upload field per screen, files up to 25 MiB, at most 10 files and 100 MiB per answer

Meta doesn't publish a maximum number of screens per flow.

When a customer completes a flow, a Flow completed card with all questions and answers appears in the conversation, and each answer is saved where you set it in step 6. Uploaded photos and documents arrive as attachments and are stored in the contact profile.

Analytics for each flow show Sent, Opened, Completed and Expired for the last 7, 30 or 90 days or a period you choose, plus a table of responses you can filter and export as CSV. Dynamic flows also show where customers drop off, screen by screen; static flows report opened and completed. Times in analytics are shown in UTC.

Need the answers in another system? Webhooks and the API pass them on, including links to uploaded files.

Replace the default texts such as "Hello!", "Done" and "Continue" with your own before you publish.

Give every field a name that is unique across the whole flow, even on end screens that exclude each other.

Keep each if/else condition to a single comparison. To react to several options, add one condition per option.

WhatsApp adds helper texts such as "(optional)" or "Choose up to 3 options." by itself, so don't repeat them in your labels.

Use Save & preview before you publish. Only WhatsApp's own check confirms that the flow is accepted.

Want to see what flows can do before you build one? The WhatsApp Flows feature page shows examples. To send a flow as part of an automation, see the Flow Builder.

1. Open Flows and switch to the WhatsApp Flows tab.
2. Start from a template or create a blank flow.
3. Or describe the form and let the AI draft it.
4. Name the flow and choose a Meta category.
5. Add screens and components.
6. Set prefill and where each answer is saved.
7. Connect the screens with footer buttons and mark the last screen.
8. Fix every error in Check your flow.
9. Set language, button text and a completion tag.
10. Use Save & preview to test the draft.
11. Publish the flow for your numbers.