AI Applications
WhatsApp Flows in AiSensy: What They Actually Do and How to Build One
WhatsApp Flows are Meta's native in-chat forms, and AiSensy gives you a no-code builder to create, publish and attach them to templates or chatbot buttons. This guide explains what Flows are, how they differ from AiSensy's chatbot flow builder (which confuses almost everyone), the actual build steps, when a Flow beats a landing page, and what to do with the data once it starts arriving.
CSEWhy ·
WhatsApp Flows are Meta's native in-chat forms, and AiSensy gives you a no-code builder to create, publish and attach them to templates or chatbot buttons. This guide explains what Flows are, how they differ from AiSensy's chatbot flow builder (which confuses almost everyone), the actual build steps, when a Flow beats a landing page, and what to do with the data once it starts arriving.
What a WhatsApp Flow is, and the thing people confuse it with
A WhatsApp Flow is Meta's native form inside the chat. The user taps a button on your message, a screen slides up inside WhatsApp with text fields, dropdowns, date pickers, radio buttons, and they fill it in without ever leaving the app. No browser, no redirect, no login. AiSensy supports this and gives you a drag-and-drop builder plus the option to paste raw Flow JSON if you want control.
Here is where most people get stuck. AiSensy has two things with the word flow in them. There is the chatbot flow builder (sometimes called Smart Flows), which is AiSensy's own conversation logic: user sends a keyword, bot replies, branches, tags, assigns to an agent. And there is WhatsApp Flows, which is Meta's form product and lives on Meta's servers after approval. They are not the same feature, they are priced differently, and they solve different problems. A chatbot flow is a conversation. A WhatsApp Flow is a form.
| Meta WhatsApp Flows | AiSensy chatbot flow builder | |
|---|---|---|
| What it is | A structured form or multi-screen UI inside WhatsApp | Automated reply logic in the chat thread |
| Where it runs | Meta's infrastructure, after you publish | AiSensy's platform |
| Needs Meta approval | Yes, the Flow is reviewed and versioned | No |
| Best for | Appointment booking, applications, surveys, order details | FAQ deflection, keyword routing, lead qualification chat |
| User experience | Tap a button, a screen opens over the chat | Back-and-forth messages and quick reply buttons |
Building and publishing a Flow in AiSensy
The build itself takes under an hour once you know the sequence. The waiting is the slow part, because a published Flow goes to Meta for review the same way a template does.
- Open the Flows section in your AiSensy dashboard and create a new Flow. Start from a category like lead generation, appointment booking, sign-up or survey, or start blank.
- Add screens. Each screen holds your components: short text input, paragraph, dropdown, checkbox, date picker, opt-in checkbox, image. Keep it to two or three screens. Drop-off on screen four is brutal.
- Set the ending. A Flow either ends locally and returns the collected answers to you (navigate mode, no server needed) or calls your endpoint mid-way to fetch live data like available slots (data exchange mode, developer needed).
- Preview it on your own number before publishing. The preview shows real rendering, and cramped labels look very different on a phone than in the builder.
- Publish. Meta reviews it. Once approved, the Flow is locked to that version, so edits mean publishing a new version.
- Attach it. Either bind the Flow to a template button and send it as a campaign, or trigger it from a chatbot flow button for inbound users.
When a Flow genuinely beats a link, and when it doesn't
The honest case for Flows is friction. A Google Form link inside WhatsApp asks the user to leave the app, load a page, possibly sign in, then come back. Every one of those steps leaks people. A Flow removes all of them, and because the form opens inside WhatsApp you already know who filled it, which means no asking for a phone number and no matching submissions to contacts later.
That matters most for short, structured, high-intent asks. Booking a demo slot. Choosing a service and a preferred time. A clinic collecting patient name, age and symptom before a call. A coaching institute taking course preference and city from an ad click. A D2C brand collecting a return reason and order ID instead of a five-message back-and-forth with an agent.
Flows are the wrong tool for long applications with document uploads, for anything needing payment inside the same step, or for content you want indexed and shareable. A Flow cannot be linked to from Instagram bio. If your form runs fourteen fields deep, send them to a page.
The parts that break
Four things cause most of the support tickets. First, approval: a Flow attached to a marketing template still needs the template approved separately, so you are waiting on two reviews, not one. Second, versioning. People edit a live Flow, forget to publish the new version, and wonder why the old screens keep appearing. Third, endpoint mode. If you picked data exchange because you wanted live inventory or slot availability, you now own a server that must respond within Meta's timeout and handle Meta's encryption handshake. Most small teams do not need this and should stay in navigate mode.
Fourth, and this is the expensive one, the message carrying the Flow is still a template message with a normal per-message charge under Meta's pricing. Flows do not make sends free. Blasting a survey Flow to 40,000 contacts costs exactly what blasting any other marketing template costs, and the block rate is the same if the list is cold.
The data is the point, not the form
Here is what usually happens three weeks after launch. The Flow works, responses land in the AiSensy dashboard or in a connected sheet via webhook, and nobody touches them for two days. The advantage of collecting a lead inside WhatsApp with zero friction disappears entirely if a human opens the sheet on Thursday.
So decide the downstream path before you publish. Where does each submission go, what tags it, who gets pinged, what message goes back automatically, and what happens if nobody replies in 24 hours. Most teams can wire the basic version themselves with a webhook into a sheet plus a CRM. The harder version, routing by intent, scoring, drafting the first reply, syncing across tools and reporting on what actually converted, is where it stops being a checkbox exercise. If you want that built and running rather than diagrammed, our team does exactly this kind of workflow build through AI Automations. Send us your current WhatsApp funnel and where it leaks, and we will tell you whether a Flow is even the right fix.
One closing note. A Flow is a conversion surface, not a strategy. The businesses seeing real lift from it are the ones who already knew their drop-off point and used a Flow to remove it.
FAQs
1. Does AiSensy charge extra for WhatsApp Flows?
Meta does not bill the Flow itself as a separate product. You pay the normal per-message charge for the template that carries the Flow, plus whatever your AiSensy plan costs. Flow availability can differ by plan tier, so check your current plan in the dashboard before building.
2. Can I use a WhatsApp Flow without a developer?
Yes, if you use navigate mode, where all screens are defined upfront and answers come back to you at the end. You only need a developer for data exchange mode, where the Flow calls your server mid-conversation to load live data such as available appointment slots.
3. How long does Meta take to approve a WhatsApp Flow?
Review is usually quick, often within a few hours, though it can stretch longer. Remember the template carrying the Flow is reviewed separately, so plan for two approvals rather than one before a campaign goes out.
4. Can WhatsApp Flows be used in marketing campaigns or only in chatbot replies?
Both. A Flow can be attached to a button on a marketing or utility template and sent out as a broadcast, or triggered from within a chatbot conversation when a user taps an option.
5. Where do WhatsApp Flow responses go in AiSensy?
Submissions appear against the contact in the AiSensy dashboard and can be pushed out through webhooks or integrations into a Google Sheet, CRM or your own system. Set that routing up before launch, otherwise responses sit unactioned.
6. What is the difference between a WhatsApp Flow and Click to WhatsApp Ads?
Click to WhatsApp Ads bring a user from Facebook or Instagram into a WhatsApp chat. A Flow is what you can show them once they are in that chat, so the two are often used together rather than as alternatives.