WhatsApp Forms: Build WhatsApp Flows, Order Forms and Booking Forms In Chat
WhatsApp does have native forms. The product is called WhatsApp Flows, and it renders real input screens inside the conversation: text fields, dropdowns, date pickers, multiple screens. The customer never leaves the chat, and the answers arrive as structured data. It runs on the WhatsApp Business Platform, so it needs Cloud API access rather than the free Business app.
Endpoint and encryption details quoted from Meta's WhatsApp Flows documentation. Per message rates are Twilio's published US list prices.
Plan your WhatsApp form
No sign inThis form has to show live data, so Meta calls your HTTPS endpoint between screens to decide what to render next. That means a server, a TLS certificate and an RSA key pair for the encrypted payloads.
Every screen can be defined up front in the Flow JSON, so no server is involved. The answers come back in one submission event. Meta recommends skipping the endpoint whenever the Flow does not need it.
A cold lead capture form is a marketing template, and Meta has blocked delivery of marketing templates to US phone numbers since April 1, 2025. Collect the lead from an inbound conversation or a click to WhatsApp ad instead, which opens a free 72 hour window.
Flows carries no separate fee. You pay for the message that delivers it. Estimate uses $0.0084 per send, being Twilio's $0.005 fee plus a $0.0034 Meta pass through at the current US utility rate. Forms sent inside an open 24 hour window are free today and become chargeable on October 1, 2026.
WhatsApp has native forms, and the product is called WhatsApp Flows
required, the free WhatsApp Business app cannot send a Flow
extra for Flows itself, you pay only for the message carrying it
typical review time, and the Flow and its template are approved separately
Does WhatsApp have forms?
Yes, and most of the advice you will find says otherwise. Search for WhatsApp forms and the top results tell you WhatsApp has no native form tool and that you need a third party builder. That was true a few years ago. It is not true now. Meta shipped WhatsApp Flows, a first party framework for interactive screens that open inside the conversation, and it handles the things people actually want a form for: several screens in sequence, required fields, dropdowns, radio buttons, checkboxes, date pickers and a submit action.
The distinction matters because the third party tools those articles recommend are usually not forms in WhatsApp at all. They generate a link or a QR code that opens a web page in the phone browser. The customer fills that page in, and the tool then forwards the answers into a WhatsApp thread. It works, but you have moved the customer out of the app to do it, and the response arrives detached from the conversation that produced it.
A Flow behaves differently. The form sheet slides up over the chat, the customer stays inside WhatsApp the whole time, and when they submit, the answers come back to your webhook as structured fields already attached to their WhatsApp identity. You are not parsing free text or matching a spreadsheet row to a phone number afterwards.
The catch is access. Flows is part of the WhatsApp Business Platform, so it needs Cloud API access through a WhatsApp Business Solution Provider or a direct integration, and your WhatsApp Business Account has to sit inside a Meta Business Manager that has completed business verification. The free WhatsApp Business app has no API, so it cannot build or send one.
WhatsApp Flows vs link based form builders vs a Google Form
Three things get called a WhatsApp form and only one of them runs inside WhatsApp. Here is what each actually does.
| WhatsApp Flows | Link or QR form builder | Google Form link | |
|---|---|---|---|
| Where it opens | Inside the chat, native sheet | Phone browser, outside WhatsApp | Phone browser, outside WhatsApp |
| Answers tied to the phone number | Yes, automatically | Only if the tool passes it through | No, unless the person types it |
| Multi screen with branching | Yes | Depends on the tool | Section logic only |
| Live data in the form | Yes, with an endpoint Flow | Yes, it is a web app | No |
| Needs Cloud API access | Yes | No | No |
| Needs Meta review | Yes, Flow and template both | No | No |
| Cost per send | Normal template or service message rate | Tool subscription plus the message that carries the link | Free, plus the message carrying the link |
| Best for | Booking, order details, onboarding, anything where drop off costs you money | Teams without API access that need something today | Internal or one off collection where identity does not matter |
If you do not have Cloud API access yet, a link based form is a reasonable stopgap and we are not going to pretend otherwise. The reason to move to Flows is drop off. Every hop out of the app costs you completions, and a booking or order form is exactly where that hurts. See WhatsApp lead generation for how the capture step fits the rest of the funnel.
What you can build with WhatsApp forms
Flows suits any exchange where you need specific fields back rather than a conversation. These are the patterns that hold up in production.
Appointment booking
Service, date, time slot, contact details. This one needs an endpoint so the slots you show are the slots that are actually open. Pair it with WhatsApp appointment reminders to cut no shows.
Order and delivery details
Size, color, delivery window, address confirmation against an order the customer already placed. Utility category, and it pairs with WhatsApp order notifications.
Lead qualification
Budget, timeline, property or product interest, best time to call. Works well as the first reply to an inbound message or a click to WhatsApp ad, which keeps it out of the marketing category.
Onboarding and signup
Company details, role, preferences, consent checkboxes. Collecting consent inside a Flow gives you a clean record of what the person agreed to, which matters for WhatsApp opt in.
Feedback and surveys
A rating, a reason code, an optional comment. Static Flow, no server needed, and the structured rating is far easier to report on than a thread of replies.
Support intake
Issue type, order reference, description, urgency. Routing on structured fields beats guessing from a free text message, and it feeds a WhatsApp shared inbox cleanly.
Do I need a server to run a WhatsApp form?
Only if the form has to react to live data. This is the decision that sets how much work the build is, so make it before you design the screens.
| Static Flow, no endpoint | Endpoint Flow, data exchange | |
|---|---|---|
| How screens are decided | All defined up front in the Flow JSON | Your server returns the next screen at each step |
| Server required | No | Yes, HTTPS with a valid TLS certificate |
| Encryption work | None | RSA key pair, public key uploaded to Meta, AES GCM payloads |
| When answers arrive | Once, on submit | At every screen transition |
| Good for | Surveys, feedback, signup, fixed choice lists | Live slots, order lookups, stock, price quotes |
| Failure mode | Nothing to go down | Your server stalls and the customer sits on a spinner |
Meta's own documentation is blunt about which to pick: "Endpoint-powered Flows should avoid using the endpoint when it is not needed. Avoiding the endpoint reduces latency for consumers and simplifies the development of the Flow."
If you do build an endpoint, Meta's requirement is that "Your server must be enabled to receive and process POST requests, use HTTPS and have a valid TLS/SSL certificate installed." Payloads are encrypted with a key pair you generate, and the docs note that "Meta automatically signs the public key during upload." If a request cannot be decrypted, the endpoint should return HTTP 421. That is the same discipline as the rest of the platform, so if you have already built a WhatsApp webhook you will recognize the shape of the work.
How to create a form in WhatsApp Business
Four steps, and the one people underestimate is the third. Nothing sends until both the Flow and the template that carries it have cleared review.
Get platform access
Connect a number to the WhatsApp Cloud API and complete business verification. The free Business app cannot do this step at all.
Build the screens
Lay the form out in the Flow Builder or post the Flow JSON through the API. Keep one task per screen. Long single screen forms get abandoned on a phone.
Publish and get approved
Publish the Flow, then create a message template with an Open Flow button pointing at it. Both go to Meta review. Budget one to three days and do not promise a launch date inside that.
Send and collect
Send the template to opted in contacts, or drop the Flow into a live conversation. Submissions arrive on your webhook as structured fields ready to write to your CRM.
Template rejection is the usual delay, not the Flow. If you are new to the review process, WhatsApp message template examples shows what passes, and how long template approval takes covers the timing in detail.
Is WhatsApp Flows free? What a form send costs
Meta charges no separate fee for Flows. There is no per form price and no seat license. What you pay for is the message that carries the form, at the ordinary per message rate for its category, so the real question is not what a Flow costs but which category your form falls into.
Meta publishes no US dollar rates in its developer documentation, so the figures below are Twilio's published US list prices, which are a fair proxy if you are buying through a provider. Twilio charges $0.005 per message in each direction and passes Meta's fee through on top, currently $0.0034 for a US utility or authentication template.
| How the form goes out | Category | US cost today | From October 1, 2026 |
|---|---|---|---|
| Reply inside an open 24 hour window | Service message | Free | Chargeable at the utility rate, no free tier |
| Sent about an existing order or account | Utility template | About $0.0084 per send | Unchanged outside the window |
| Utility form delivered inside an open window | Utility template | Free | Loses free status, becomes chargeable |
| Cold lead capture to a US number | Marketing template | Not delivered | Still paused, no published end date |
| First reply after a click to WhatsApp ad | Free entry point, 72 hours | Free | Unchanged |
Two dates are worth putting in your calendar. Meta has committed to publishing final service message rates by September 1, 2026, and from October 1, 2026 any non template reply inside an open 24 hour window becomes chargeable, along with utility templates delivered inside that window. If your form runs as an in window reply today, it is free today and it will not be free in October. The WhatsApp pricing changes page tracks both, and the pricing calculator will model your own volume.
One more thing worth knowing about the marketing row: cold lead capture forms to US numbers have not delivered since April 1, 2025, when Meta paused marketing template delivery to +1 numbers. Meta returns error 131049 and Twilio surfaces it as 63049. The workaround is not a different template, it is a different entry point. Let the customer open the conversation, through an inbound message or a click to WhatsApp ad, then send the form as a reply.
WhatsApp forms questions
What are WhatsApp Flows?
WhatsApp Flows is Meta's framework for interactive, structured screens inside a WhatsApp conversation. You define the screens and fields as JSON, publish the Flow, then attach it to a message with an Open Flow button. When the customer taps it, the form opens in a native sheet over the chat, and the answers come back to you as structured data rather than free text you have to parse.
How to create a form in WhatsApp Business?
You need the WhatsApp Business Platform, not the free WhatsApp Business app. Build the screens in the Flow Builder or upload the Flow JSON through the API, publish the Flow, then create a message template carrying an Open Flow button that points at it. Both the Flow and the template go through Meta review, which typically takes one to three days, and only a published Flow can be sent.
Is WhatsApp Flows free?
Meta charges no separate fee for Flows itself. You pay for the message that carries the form, at the normal per message rate for its category. A form sent inside an open 24 hour customer service window costs nothing today, and a form you send to start a conversation is billed as a marketing, utility or authentication template. From October 1, 2026 replies inside that window stop being free.
Do I need a server to run a WhatsApp form?
Only if the form has to react to live data. A static Flow defines every screen up front and returns the answers when the customer submits, with no server involved. An endpoint Flow calls your HTTPS server between screens, which is what you need to show real appointment slots or look up a live order. Meta's own advice is to skip the endpoint whenever the Flow does not need it.
Can I use Google Forms on WhatsApp instead?
You can paste a Google Forms link into a WhatsApp message, but that is not a form in WhatsApp. It pushes the customer out to a browser, which is where most of the drop off happens, and the response lands in a spreadsheet with no reliable link back to the phone number that filled it in. A Flow keeps the customer in the thread and returns answers already tied to their WhatsApp identity.
How long does WhatsApp Flow approval take?
Plan for one to three days. Two things get reviewed: the Flow itself, and the message template that carries the Open Flow button. They are separate approvals and either one can come back with changes. Build the review time into any launch date, because an unpublished Flow cannot be sent and a rejected template blocks the send even when the Flow is ready.
Can I send a WhatsApp form to a list of customers?
Yes, through an approved template with an Open Flow button, and only to people who opted in. The category rules still apply. A lead capture form sent cold is a marketing template, and Meta has blocked delivery of marketing templates to US phone numbers since April 1, 2025, so US outbound campaigns need a utility purpose tied to an existing order or account. Sending rate is governed by your messaging limit tier, not by the Flow.
Can a WhatsApp form pre fill what I already know?
Yes. You can pass initial values into the Flow when you send it, so a customer confirming a delivery address sees their address already filled in rather than typing it again. This is the single cheapest completion win available, because the shortest form is the one that is already mostly answered.
Send forms to your list, not one chat at a time
WaBulkSend will run approved templates, Flows and scheduling across your opted in contacts from one place, with per message costs shown before you send. Join the waitlist for early access.
Join the waitlistRelated guides
WhatsApp lead generation
Where a capture form fits in the funnel and what to do with the lead afterwards.
WhatsApp Cloud API
The platform access Flows depends on, and how to get a number onto it.
Message template examples
Templates that clear review, including the one that carries your Open Flow button.
WhatsApp appointment reminders
The natural follow up once a booking form has captured the slot.
WhatsApp pricing changes
What changes on October 1, 2026 and what it does to in window sends.
WhatsApp opt in
Consent wording that holds up, including consent collected inside a Flow.