WhatsApp Flows: The Complete 2026 Guide to In-Chat Forms

WhatsApp Flows are Meta's native feature for building multi-screen forms, surveys, booking interfaces, and lead-capture experiences that customers complete entirely inside a WhatsApp chat — no website, no landing page, no app switch required.

A Flow can have one screen or many. Each screen contains components like text inputs, dropdowns, date pickers, radio buttons, checkboxes, and opt-in toggles. The user taps a CTA button in a normal WhatsApp message, the Flow opens as a full-screen interface inside WhatsApp, the user fills it out, taps Submit, and the structured response arrives at your server.

Flows are now supported on PayPerWA, Wati, AiSensy, and Interakt. PayPerWA's Flow builder includes a visual editor, 8 pre-built templates (appointment booking, lead capture, feedback, order, event registration, sign-up, demo request, contact us), conditional routing between screens, and automation triggers on completion.

Compared to a traditional WhatsApp message with a link to a Google Form or your website, Flows convert 4-6x better in Indian businesses we've measured. The reason is simple: zero context switching, no extra app opens, no mobile-data-required-but-website-loads-slowly friction.

Use a Flow whenever you need to collect structured information from a customer. Common high-impact use cases for Indian businesses:

1. Appointment booking — clinics, salons, coaching classes, dentists, financial advisors. Customer picks date and time slot inside WhatsApp; your team gets a structured response with the booking details.
2. Lead capture — real estate inquiries, education enrollment, B2B sales leads. Replace your contact form with a Flow attached to your WhatsApp ad.
3. Order placement — restaurants taking takeaway orders, neighborhood grocery stores, custom-product makers. Customer selects items, quantity, delivery address, all in-chat.
4. Customer feedback / NPS — post-purchase, post-delivery, post-service feedback. Higher response rates than email surveys.
5. Event registration — webinars, workshops, religious events, exhibitions.
6. KYC and document upload — works for capturing structured KYC data; file upload itself happens via follow-up chat message.
7. Sign-up and newsletter opt-in — turn one-time message recipients into long-term subscribers with a tap.

Avoid Flows when the interaction is simple (yes/no, single choice) — quick reply buttons in a template message work better there. Flows shine when you need 3+ structured inputs.

Every Flow has four pieces:

1. Screens

A Flow has one or more screens, each with a title and a list of components. PayPerWA supports unlimited screens per Flow.

2. Components

Each screen contains components. Display components (Headings, Body text, Captions, Images, Embedded links) provide context. Input components (TextInput, TextArea, DatePicker, Dropdown, RadioButtonsGroup, CheckboxGroup, OptIn) collect data. The Footer is the CTA button — "Continue" between screens, "Submit" on the last screen.

3. Routing

By default, screens flow linearly: screen 1 → screen 2 → screen 3 → Submit. PayPerWA supports conditional routing — for example, if a user rates their experience 1-2 on a feedback Flow, branch to a "What went wrong?" screen; if they rate 4-5, branch directly to "Thank you". Routing rules support equals, not equals, contains, greater than, and less than operators.

4. Completion Actions

When a user submits a Flow, you can trigger automated actions: assign contact tags, send a confirmation template message, fire a webhook to your CRM, or all three. PayPerWA's automation dialog lets you configure these per Flow without writing code.

Once a Flow is published to Meta, you can deliver it to customers in three ways:

Method 1: Standalone Send

Send the Flow as a one-off interactive message to a contact or group. Best for ad-hoc lead capture, surveys after a meeting, or feedback requests after a transaction. In PayPerWA: open the Flow, click "Send Flow", pick recipients, write a short intro body, set a CTA label (e.g., "Open Booking"), send.

Method 2: Template CTA Button

Attach a Flow to an approved Marketing or Utility template as a CTA button. When the template is sent in a campaign, recipients tap the button to open the Flow. Best for high-volume campaigns where the Flow IS the conversion goal (e.g., a 10,000-recipient marketing blast with "Book a Slot" Flow attached). In PayPerWA: when building a template, add a button of type FLOW, pick the published Flow.

Method 3: Chatbot Node

Trigger a Flow inside a chatbot conversation flow. Example: customer messages "book", chatbot replies "Let's schedule your visit" and sends the Booking Flow. PayPerWA's chatbot builder includes a Send Flow node for exactly this.

Here's the exact path for building a Lead Capture Flow on PayPerWA:

1. Go to Dashboard → Flows → New or pick the "Lead Capture" template from the library.
2. Edit the screen title (e.g., "Get In Touch").
3. From the component palette on the left, drag in: a Heading ("Tell us about you"), a TextInput for full name, an email TextInput, a Dropdown for budget range, a TextArea for requirements, and an OptIn for consent.
4. Click Save, then Publish to WhatsApp. Meta typically approves Flows within minutes; you'll see the status badge flip from "Draft" to "Published".
5. Configure Automation (top bar): assign the "Lead" tag automatically, send a confirmation template ("Thanks, our team will reach out within 24 hours"), and POST the response to your CRM webhook.
6. Test it: click Send Flow, send to your own WhatsApp number, fill it out from your phone, and verify the response arrives in your Flows → Responses dashboard.

Total time: 10 minutes. From there, you can attach the Flow to a template button for ongoing campaigns.

1. Keep it short. 3-5 fields convert dramatically better than 10+. Cut every non-essential question.
2. Use multi-screen for long forms. Better to have three screens with 3 questions each than one screen with 9 questions. Mobile users abandon long scrolling forms.
3. Start with the easiest field. Name first, then phone, then more demanding questions like budget or address.
4. Use dropdowns over text inputs when there's a finite set of options (service type, budget range, time slot). Dropdowns are faster to fill on mobile.
5. Add an opt-in. Required for compliance — and reduces "I never asked to be contacted" complaints later.
6. A/B test your CTA label. "Get a Quote" vs "Book Now" vs "Free Consultation" can swing tap-through rates by 20%+.
7. Reply within 5 minutes of receiving a Flow response. The lead is hot — the customer literally just submitted intent. Automate the immediate confirmation, then have a human follow up.

Sending a Flow costs the same as sending any other WhatsApp message:

• Standalone send or chatbot-triggered Flow: counts as a service conversation if the customer messaged first within 24 hours (free Meta fee, ₹0.20 PayPerWA fee). If outside the window, you'd need a template, which means marketing or utility rate.
• Template-attached Flow: pays the template's category rate. Marketing template with Flow button = ₹1.06/recipient. Utility template = ₹0.33.

The Flow itself adds no extra Meta charge — you pay per message-delivery as usual. PayPerWA charges no surcharge for Flows; the ₹0.20 platform fee is the same as for any other message type.

Q: Can WhatsApp Flows replace a website form?
For most lead capture, booking, and survey use cases — yes. Indian businesses we've worked with see 4-6x higher submission rates on WhatsApp Flows compared to traditional website forms. Flows are not a replacement for complex multi-step checkout with payment integration; for that, link to your checkout page after capturing intent in a Flow.

Q: How long does Meta take to approve a Flow?
Most Flows are approved within minutes if the JSON validates cleanly. PayPerWA pre-validates Flows before submission, catching the common "Integrity requirements not met" rejection in advance. The most common reasons for slow approval: duplicate field names, missing required components, or invalid URLs in embedded links.

Q: Can I edit a published Flow?
Not directly. Once a Flow is published, the JSON is locked. To make changes, deprecate the current Flow and create a new version. PayPerWA tracks versions automatically so you don't lose old responses.

Q: Do WhatsApp Flows work on iPhone and Android?
Yes, on both platforms. WhatsApp version 2.23.x or later required (most users are current). On older WhatsApp versions, the user sees a fallback message asking them to update.

Q: Can I conditionally branch screens in a Flow?
Yes. PayPerWA's Flow builder supports routing rules — if the answer on a previous screen meets a condition (equals, not equals, contains, gt, lt), branch to a specific next screen.

Q: Can a Flow collect file uploads (photos, PDFs)?
Currently no — WhatsApp Flows do not support direct file upload components. You can ask the user to send the file as a follow-up message in the chat.

Q: How do I see Flow responses?
In PayPerWA, go to Flows → click on a published Flow → Responses tab. You'll see every submission with all field values, sender name/phone, and timestamp. CSV export is available. The Flows analytics page also shows a funnel: sent → delivered → read → completed.

Flows are one of the highest-ROI features in WhatsApp marketing for 2026. They turn passive message recipients into structured leads with one tap. Indian D2C brands, coaching institutes, and service businesses are seeing real conversion lifts.

Get started: create a free PayPerWA account, connect your WhatsApp Business number, and pick one of our 8 pre-built Flow templates. From draft to published Flow on Meta typically takes 10-15 minutes. Sending costs the same as any WhatsApp message — ₹0.20 platform fee plus Meta's standard rate.