Creating WhatsApp Flows native forms to collect leads in-chat

Updated 2026-09-19 · 4 min read · By the Convo360 team

WhatsApp Flow forms vs Show Form (web)

Convo360's flow builder has two form mechanisms and it's worth knowing which one you actually need. Show Form (web) opens a lightweight in-chat web form for name, phone, email or custom fields, quick to set up, with no Meta review needed. WhatsApp Flow (native form) is Meta's own multi-screen form technology, rendered nativnatively inside WhatsApp itself rather than a web view, better for longer, structured intakes with several screens, but it needs to be built and published in Meta's system first.

As a rule of thumb: reach for Show Form when you need three or four fields answered quickly, and reach for a WhatsApp Flow form when you need several screens, conditional questions, or a genuinely form-like structure that a simple in-chat text exchange would make tedious.

Prerequisites

You need your WhatsApp Cloud API connected (Coexistence numbers cannot use native Flow forms), access to your Meta Business Manager, and a clear idea of the screens and fields you want before you start, since changing a published flow's structure later usually means creating a new version.

Sketch the screens on paper first if it helps: how many fields per screen, and what order makes sense, since Meta's flow builder is a separate tool from Convo360's and switching between the two mid-design slows you down.

The exact click path

1. Design and publish the form's screens in Meta's WhatsApp Manager flow tool: fields, dropdowns, screen order.
2. Back in the Convo360 flow builder, add a WhatsApp Flow block from the Interactive category.
3. Reference the flow you published in Meta.
4. Map each screen's answers to a Save to variable field, exactly as you would with an Ask a Question step.
5. Follow it with a Save CRM lead step to turn the completed form into a pipeline lead.

Treat the Meta side and the Convo360 side as two halves of one job: nothing in the flow builder can change a screen's fields after publishing on Meta's side, so get the structure right there first, then wire up the mapping in Convo360 once it is final.

Worked example: a two-screen lead-gen form

A coaching institute wants prospective students to share their details and requirement without a long back-and-forth chat. Screen one asks name, phone and city; screen two asks the course of interest and preferred batch timing. Both screens' answers land as flow variables, which a Save CRM lead step turns into a lead with the course and batch already filled in, ready for a counsellor to call, no manual data entry.

Compare that to the same intake over free-form chat: five or six back-and-forth messages, several of which the AI would need to interpret rather than simply record. A native form is faster for both sides when the questions are this structured.

Good use cases for a native Flow form

Reach for a WhatsApp Flow form whenever a chat exchange would otherwise take five or more back-and-forth messages to collect structured information: a detailed service request, a multi-field KYC-style intake, an event registration with several attendee details, or a job application with education and experience fields. Each is naturally a form, not a conversation, and customers tend to complete a well-designed multi-screen form faster than the same questions asked one at a time in chat.

It is a poor fit for anything that benefits from back-and-forth, a query where the next question depends heavily on the previous answer in a way that is easier for an AI Reply step to handle than a fixed set of screens.

Troubleshooting

What to test before going live, and cost

• Complete the form yourself from a real phone before sharing it with customers.
• Confirm every screen's answers show up correctly as variables in the flow logs.
• Confirm a completed form actually creates or updates a CRM lead.
• Test on an older phone if you can, to catch the rare device that can't render the native form.
• Walk through what happens if the customer abandons the form halfway, decide whether a partial submission should still create a CRM lead worth following up on.

There's no extra Convo360 charge for using WhatsApp Flow forms beyond your plan; Meta's own per-message fees apply as usual, billed directly with no Convo360 markup.

Budget a little extra review time for the first Flow form you build, since Meta's own approval and publishing steps sit outside Convo360's control.

Step by step

1. Design the flow's screens in MetaBuild and publish the form's screens (fields, dropdowns, order) in WhatsApp Manager.
2. Add a WhatsApp Flow blockIn the Convo360 flow builder, drop a WhatsApp Flow block and reference the published flow.
3. Map answers to variablesSet 'Save to variable' for each screen's fields.
4. Save as a CRM leadAdd a Save CRM lead step after the form to turn the submission into a pipeline lead.
5. Test end to end from a real phoneComplete the form yourself and confirm the variables and CRM lead are correct.

Example conversation

Frequently asked questions

Related reading

Available across India — see WhatsApp & AI calling automation by state and city.