Static vs. Dynamic WhatsApp Flows
A static WhatsApp Flow shows screens and content that are fixed when it is published and needs no server of its own. A dynamic WhatsApp Flow exchanges data with a server while the customer fills it in, for example to show open appointment slots or check an entry on the spot.
What is the difference between static and dynamic WhatsApp Flows?
A WhatsApp Flow is a form inside the chat. Meta distinguishes two kinds, depending on where the flow gets its content:
- Static flow: every screen, field and option is fixed when the flow is published. The flow needs no server of its own. Meta works out the paths between screens from the buttons, and the answers only reach the business when the customer submits.
- Dynamic flow: the flow is connected to a data endpoint. At defined steps it sends the entries so far to that server and gets new content back, for example the open slots for the chosen day, matching products or a note that a customer number does not exist.
Technically the difference shows in the Flow JSON. A dynamic flow needs an explicit routing model that lists the allowed paths between screens, a data API version and data_exchange actions that call the server. The endpoint must be reachable over HTTPS, and the data is encrypted in transit.
What a static flow can still do
Static does not mean rigid. A static flow can show or hide parts of a screen depending on an answer, for example a free-text field that only appears when "Other" is selected. It validates required fields, can span several screens and can send customers down different paths depending on their answers. What it cannot do is look something up that keeps changing while the customer fills it in.
As a rule of thumb: if the content rarely changes, a static flow is enough. If it depends on your stock, your calendar or your customer data, you need a dynamic one.
Why the difference matters
- Up-to-date options: only a dynamic flow shows customers what is true right now, such as only the slots that are still free. People who see a fitting option straight away are more likely to finish.
- Fewer errors: a dynamic flow can check an entry immediately and let the customer correct it inside the form.
- Effort: a static flow is quick to build and needs no development. A dynamic one needs an endpoint that answers quickly and reliably.
- Operations: Meta monitors endpoints. If one responds too slowly or fails too often, Meta can throttle or block the flow.
Practical example
A bike repair shop takes repair requests on WhatsApp. Its first flow is static: type of bike, what needs fixing, a photo of the damage and a preferred time frame. The team then replies with a suggested appointment.
Later the shop switches to a dynamic flow. After the customer picks a repair, the flow only shows the days with free capacity for it, and the customer chooses a slot right in the form. The back-and-forth about dates disappears.
Static and dynamic flows with SendSeven
In SendSeven's builder for WhatsApp Flows (beta) you can build static flows from the Basic plan. Dynamic flows are available from the Scale plan. Their content can come from the contact profile, custom-field options, lists, tags, the catalogue or your own webhook. SendSeven provides the data endpoint that Meta requires for dynamic flows, hosted in the EU.
Two limits are worth knowing: Coexistence numbers run static flows only, and the AI builder (Professional and up; it uses AI Credits, only for successful runs) also builds static flows. Only for dynamic flows do analytics show at which screen customers drop off.
WhatsApp Flows is in beta. What a sent and a completed flow cost is explained in the WhatsApp Flows entry.
GDPR-compliant, EU-hosted. 14-day free trial.