WhatsApp Flows: A Practical Guide to Static and Dynamic Forms
WhatsApp Flows turn a chat into an app screen. Instead of asking five questions one message at a time, you send a structured form that opens inside WhatsApp, collects everything in one go and returns clean data to your system.
Static Flows
A static Flow is defined entirely in advance: screens, fields and options are fixed. Ideal for lead capture, feedback surveys, event registration and simple preference centres. No server is needed beyond receiving the completed response.
Dynamic Flows
A dynamic Flow calls your endpoint as the customer moves between screens. That lets you show live appointment slots, check stock, price a quote or validate a postcode before the customer continues. The endpoint exchange is encrypted and must respond quickly, so it suits teams with a reliable back-end.
| Static | Dynamic | |
|---|---|---|
| Content | Fixed | Fetched live per screen |
| Back-end needed | No | Yes, an encrypted endpoint |
| Best for | Surveys, sign-ups, feedback | Bookings, quotes, eligibility checks |
Use cases that work
- Appointment booking with real availability.
- Lead qualification after a Click-to-WhatsApp ad.
- Onboarding and KYC-lite data collection.
- Post-service surveys and NPS.
- Consent and preference capture.
Pricing
Flows themselves are not billed. Since Meta's move to per-message pricing on 1 July 2025, you pay for the message carrying the Flow: nothing inside an open customer service window, or the relevant template rate outside it.
GDPR checklist
- Collect the minimum fields needed for the purpose.
- State the purpose and link your privacy notice on the first screen.
- Use a separate, unticked checkbox for marketing consent.
- Store responses in-region with defined retention.
- Avoid special-category data unless you have a clear legal basis.
How Arino One fits
Arino One lets you build static and dynamic Flows, write responses straight to the contact record in the CDP, and trigger automations on completion — all on your dedicated instance.
FAQ
What are WhatsApp Flows?
Native, multi-screen forms that open inside a WhatsApp chat — text fields, dropdowns, date pickers, checkboxes — so customers can book, sign up or answer a survey without leaving WhatsApp.
What is the difference between static and dynamic Flows?
Static Flows have fixed content defined up front. Dynamic Flows call your own endpoint between screens to fetch live data, such as available appointment slots or stock, and validate answers in real time.
How much do WhatsApp Flows cost?
Meta does not charge separately for Flows. You pay for the message that carries the Flow: free inside a customer service window, or the template's category rate if you send it as a template outside one.
Are WhatsApp Flows GDPR compliant?
They can be. Collect only what you need, state the purpose on the form, record consent separately for marketing, and make sure responses land in a system hosted in-region with a proper DPA.
Apply this to your own deployment
This guide describes decisions we make on live instances. Tell us your channels, systems and region and we will map it to an architecture outline, a provisioning plan and an indicative commercial model — usually within one business day.