Build a form once with 3650HQ's visual Flow builder, then send it inside a WhatsApp conversation. A clean form opens on the customer's phone to collect size, colour and delivery address, without sending them to an external website.
3650HQ's Flows are static forms: you design the fields once and send them, and there's no dynamic, server-driven logic that changes what a customer sees based on a previous answer. They're built with Meta's official WhatsApp Flows API, not a third-party workaround.
Collecting the details needed to fulfil an order over WhatsApp usually means typing out a list of questions and hoping the answers come back in a usable shape. They rarely do. The customer answers two of the four questions, sends the address as a voice note, adds the landmark in a follow-up message ten minutes later, and gives a size in a format that could mean two different things.
Someone then has to reassemble all of that into an order. That reassembly is where wrong sizes and wrong addresses get introduced, and a wrong address is not a small error: it is a courier fee spent on a delivery that does not arrive.
The alternative most tools reach for is a link to a web form. It works, technically. It also asks a customer who is comfortable in WhatsApp to open a browser, load a page from a domain they do not recognise, and type an address into it. A measurable share of them simply do not, and the ones who abandon look identical to the ones who were never going to buy.
WhatsApp Flows are Meta's own in-chat form mechanism. The form opens natively on the customer's phone inside WhatsApp, and 3650HQ publishes real Flow JSON to Meta through the official API rather than approximating one with a sequence of question messages.
Add screens, drag to reorder them, and set field properties in an inspector. A live phone preview shows what the customer will actually see as you build, so the form is checked before it is sent rather than after.
Common shapes are already built, so a typical order form is an edit rather than a blank canvas.
A published Flow can be dropped into any thread mid-conversation, at the point where the details are actually needed.
Submissions come back in a per-Flow Responses view as structured fields rather than as free text scattered through a thread, and the whole set exports to CSV.
A published Flow can be the payload of a bulk campaign, so a send can collect answers from a list rather than only delivering a message to it.
3650HQ's Flows are static. You design the screens and fields once, and every customer who receives that Flow sees the same ones. There is no server-driven branching that changes the next question based on a previous answer, and no live data being fetched into the form while the customer is filling it in.
For a delivery address, a size and a colour, that is the whole requirement and the limitation never comes up. Where it does come up is anything conditional: a form that should ask different questions for a bulk order than a single item, or one that needs to show live stock for the colour just chosen. Those are genuinely not possible here, and it is better to know that from this page than to find out after building the form.
Responses land in a per-Flow view, with every submission as structured fields. That is what makes the data usable downstream: an address collected through a Flow is a field, not a sentence somebody has to read and interpret before a courier booking can be made.
It is also what makes the order reconstructable later. When a delivery goes wrong three days afterwards, the address the customer actually submitted is a record you can look at, rather than a claim to be re-litigated by scrolling through a conversation.
Yes. Build a Flow with an address field and send it in the chat. The customer fills it in without leaving WhatsApp, and the answer lands in your thread.
No. 3650HQ has a visual Flow builder and starter templates, so no coding is required.
Not currently. 3650HQ's Flows are static, single-pass forms rather than branching, conditional forms.
They appear inside the conversation thread and can be exported to CSV.
No. WhatsApp Flows open natively inside WhatsApp on the customer's phone. They never leave the app, which is the entire point: a link to an unfamiliar domain is where a meaningful share of customers drop out.
Yes. The builder shows a live phone preview as you add and reorder screens, so the form is checked before a customer ever receives it.
Yes. Submissions collect in a per-Flow Responses view as structured fields and the whole set exports to CSV.
Yes. A published Flow can be the payload of a bulk campaign, so a send can collect structured answers from a list rather than only pushing a message out to it.
No. The builder is visual, with six starter templates for common shapes. 3650HQ publishes the underlying Flow JSON to Meta for you.