WhatsApp Flows: Meta's In-Chat Forms Feature Explained (2026)

WhatsApp Flows is Meta's feature for sending structured, multi-screen forms inside a WhatsApp chat. Launched in late 2024 and expanded throughout 2025, Flows let businesses collect sign-ups, bookings, lead data, and support intake without sending customers to an external landing page. The format runs only on the WhatsApp Cloud API, and replaces brittle typed-answer flows with a native form UI. This guide covers what Flows can do, how to build one, approval rules, pricing under the 2026 model, and how Shopify merchants are using them.

WhatsApp Flows vs Templates vs Broadcast

The three formats often get conflated. They are not interchangeable. Each was built for a different stage of the conversation.

If you only need to push an update, send a template. If you need to broadcast to a list, see our WhatsApp broadcast guide. If you need to collect structured data inside the chat, that is what Flows were built for.

What a WhatsApp Flow Can Do

The core unit is a screen. A screen contains form components (text input, radio, dropdown, date picker, checkbox) plus a continue button. A Flow can have a single screen or multiple, with conditional logic deciding which screen comes next.

Common patterns in production:

Sign-up Flow. Capture name, email, segment, opt-in. One screen, four fields, one CTA. Used to convert click-to-chat ad traffic into newsletter subscribers without a landing page.

Booking Flow. Pick a service, pick a date, pick a slot, confirm. Used by salons, clinics, and service-led commerce.

Lead-capture Flow. Multi-step qualifier with branching. Common for B2B and high-ticket B2C.

Support intake Flow. Order number, issue category, severity, description, photo upload. Routes the message to the right queue with the right context. Used by Shopify brands offering WhatsApp customer support.

Post-purchase survey Flow. NPS plus 2 follow-ups. Sent as a utility message 7 days after delivery. Response rates 25 to 40%, vs 3 to 8% for an email survey link.

Technical Requirements

Three constraints to know before you commit:

• Cloud API only. Flows do not work on the free Business app, on MM Lite, or on the deprecated on-premises API.
• Meta Business Manager required. Your WhatsApp Business Account must be inside a verified Meta Business Manager.
• HTTPS endpoint for data exchange. Meta posts submitted Flow data to a public HTTPS endpoint you control (or your BSP provides). It must respond with a 200 in under 10 seconds.

For Shopify merchants, the easiest path is a BSP that handles the endpoint and certificate. The Kanal Shopify integration ships with a managed Flow endpoint mapped to Shopify customer and order objects.

How to Build a WhatsApp Flow

Meta exposes two ways to build a Flow.

The Flow Builder UI

The Flow Builder lives inside your Meta Business Manager under WhatsApp Manager. Drag-and-drop screens onto the canvas, add components, set validations and conditional rules. The builder writes the underlying JSON for you. Best for marketing and operations teams without a developer in the room.

The JSON Spec

For developers, Meta publishes the Flow JSON spec. A Flow is a single JSON document with a version, a list of screens, components on each screen, and a routing_model between them. The JSON path is faster to version-control and the right choice when Flows are part of a larger codebase.

Most Production Builds Use a BSP

In practice, neither pure-Meta path is what most Shopify brands ship with. They use a BSP that wraps Meta's API with a Shopify-aware UI. The brand defines the Flow once, the BSP handles the endpoint, the data mapping into Shopify customer or order objects, and the trigger from Shopify events (cart abandoned, post-purchase, repeat customer).

Approval Process and Meta's Review Criteria

Every Flow goes through Meta review before it can be sent in production. The review is automated for structure and manual for content.

What Meta checks:

• Privacy policy link in any screen that collects personal data
• No sensitive data without justification (no asking for ID numbers, payment cards, health info unless the use case is registered with Meta)
• No external messaging app promotion (the Flow cannot funnel users to Telegram, SMS, or competing channels)
• Screen transitions resolve (no orphan screens, no infinite loops in conditional routing)
• Template that opens the Flow matches its category (Marketing template opens a marketing Flow, Utility template opens a utility Flow)

First-pass approval rate sits around 70% across Kanal customers. After resubmission with the cited fix, it goes above 95%. Review time is typically 24 to 48 hours, slower in Q4.

Use Cases for Shopify E-commerce

Five Flow patterns paying for themselves on Shopify stores in 2026:

Welcome sign-up Flow. Triggered from a click-to-WhatsApp ad or QR code. Captures name, segment, and explicit opt-in. Converts cold ad traffic into a subscriber base. Average completion rate 55 to 70%, vs 8 to 15% for an equivalent landing page.

Return request Flow. Order number, item, reason (dropdown), photo upload. Replaces an email or a help-desk form. Cuts time-to-first-response from 6 to 8 hours to under 30 minutes.

Sizing-helper Flow. A 3-screen quiz that recommends a size based on height, weight, fit preference. Sent as a post-purchase utility template. Reduces return rate by 12 to 20% on apparel.

Post-purchase survey Flow. NPS plus open feedback. Response rate 25 to 40%. Used to recover at-risk customers and to surface SKU-level quality issues early.

B2B lead Flow. For Shopify Plus and B2B brands. Qualifies inbound demand from ads or referral. Routes high-fit leads to a human sales rep, low-fit to a self-serve checkout.

Performance Benchmarks

Across Shopify merchants using Kanal in 2025 and 2026:

• Open rate on the template that opens the Flow: 90 to 96%, in line with all WhatsApp templates
• Tap rate on the CTA button that opens the Flow: 35 to 55%, depending on incentive and audience warmth
• Completion rate of the Flow once opened: 55 to 80% for single-screen, 35 to 55% for multi-screen
• Time spent inside the Flow: 18 to 60 seconds, vs 2 to 5 minutes for equivalent landing-page forms
• Conversion rate (data submitted to action taken on Shopify): 15 to 35% for sign-up Flows, 40 to 65% for return requests

Compared to equivalent email forms: completion rate is 4 to 8x higher, time-to-submit is roughly 10x faster, and form abandonment drops from 60 to 70% on email to 15 to 30% on WhatsApp.

Limitations and Gotchas

Things to plan around in 2026:

• No native payment in most countries. The customer still has to leave the Flow to pay on your Shopify checkout. India and Brazil have partial WhatsApp Pay integration, but not yet a true in-Flow checkout in Europe or North America.
• No file upload above 5 MB per attachment. Photo uploads for support intake work for most use cases. Large video files do not.
• No real-time analytics in the Flow Builder. You see total opens, completions, and field-level drop-off, but not per-message attribution out of the box. You need a BSP or your own pipeline to tie a Flow completion to revenue.
• No A/B testing built into Meta's Flow Builder. You can ship two Flows and split traffic at the template level, but there is no native experiment manager. Most BSPs add this on top.
• Flow versioning is partial. When you edit and republish, the in-flight Flow sessions complete on the old version. New sessions start on the new one. Be careful when changing field names mid-campaign.

Pricing Under Meta's 2026 Model

Meta charges per conversation, not per message. A WhatsApp Flow opened from a template costs one conversation at the template's category rate.

There is no separate Flow surcharge from Meta. Your BSP typically adds a small platform fee on top, often a fixed monthly fee plus the per-conversation cost passthrough. For most Shopify merchants, a Flow conversation lands between $0.005 and $0.08 fully loaded. See our WhatsApp Business pricing guide for the per-country breakdown.

How Kanal Builds Flows for Shopify Merchants

The Kanal Shopify app ships a visual Flow builder with two things the bare-Meta tooling does not have:

Shopify-event triggers. A Flow can be triggered by any Shopify event: order created, order delivered, customer first purchase, cart abandoned, refund issued. The trigger pulls the relevant customer and order data into the Flow as variables, so the merchant does not write any code.

Pre-validated templates. The opening template that launches the Flow is checked against Meta's content rules before submission. First-pass approval rate inside Kanal sits around 90%, vs the 70% Meta-direct baseline.

The full set of Shopify automations including Flows is in our WhatsApp campaigns page. If you're comparing tools, our Kanal vs Wati comparison and Kanal vs Charles comparison cover Flow capabilities side by side. Want to see it live? Book a Kanal demo or check the pricing page.

When to Use a Flow Instead of Other Surfaces

A decision tree to keep on a sticky note:

• Need to push an update, no response expected: send a template message.
• Need to broadcast to a list: see the broadcast guide.
• Need to chat in free text, no structured fields: use an AI chatbot or a human agent.
• Need to collect 2 or more structured fields in one session: send a Flow.
• Need to take payment: redirect from the Flow to Shopify checkout via a CTA button (or use WhatsApp Pay if you operate in India or Brazil).
• Need recurring content delivery to fans (one-to-many, no replies expected): see our WhatsApp Channels guide.

Flows fill the gap between "send a message" and "open the website." They keep the customer inside WhatsApp while still collecting the structured data your Shopify backend needs.

Getting Started

Three steps: verify your WhatsApp Business API is on Cloud API and Meta Business Manager is verified. Pick a single, low-stakes Flow to launch first (sign-up or return request). Ship behind a small test segment, measure completion rate, then scale.

If your store is on Shopify, install Kanal and the Flow builder, Shopify event triggers, and managed endpoints are ready to go.