Guide

    WhatsApp Flows Explained: Forms, Bookings and Lead Capture Inside WhatsApp (2026 Guide)

    What WhatsApp Flows are, how they work (screens, endpoints, templates), 6 India use cases from bookings to lead forms, pricing, best practices and limits.

    By Abbas Ali, Founder, WatsBerryUpdated 6 min read

    WhatsApp Flows Explained: Forms, Bookings and Lead Capture Inside WhatsApp (2026 Guide)

    Quick answers

    What are WhatsApp Flows?
    WhatsApp Flows are structured, multi-screen experiences such as forms, booking screens and product selectors that open inside a WhatsApp chat. Meta describes them as a way to build structured interactions for business messaging, used for leads, recommendations, sign-ups and bookings.
    How much do WhatsApp Flows cost?
    Meta's pricing page doesn't list a separate Flows fee. You pay for the message carrying the Flow: a marketing or utility template if you start the conversation, or a service message if you send it inside an open customer service window. Your provider may charge for Flow features in its plan.
    Can I use WhatsApp Flows for appointment booking?
    Yes. A booking Flow can show services, staff, dates and available slots. Showing live availability needs a data endpoint connected to your calendar or booking system, and Meta says endpoint requests time out after 10 seconds, so the backend must be fast.

    Short answer

    WhatsApp Flows are app-like screens (forms, lists, date pickers, dropdowns) that open inside a WhatsApp chat, so customers can book appointments, fill lead forms or pick products without leaving WhatsApp. You send a Flow inside the 24-hour window as an interactive message, or proactively via a template with a Flow button. Simple Flows can be endpointless. Live data (like open slots) needs a data endpoint that responds within 10 seconds. Meta's pricing page doesn't list a separate Flows fee; you pay for the message that carries it.

    Why Flows matter

    A chatbot that asks ten questions one by one feels slow, and typed answers are messy ("tmrw evng?"). A Flow gives the customer a proper form, with dropdowns, date pickers and checkboxes, in the same chat. Meta's Flows overview lists uses such as lead generation, product recommendations, insurance quotes and personalised offers.

    For Indian slot sellers and D2C brands, that means:

    • Cleaner data: structured fields instead of free text.
    • Fewer drop-offs: no website redirect on slow mobile data.
    • Faster bookings: pick a slot in a few taps.

    How a Flow works (in plain English)

    1. You design screens in Flow JSON or a visual builder: welcome → choose service → choose date → confirm.
    2. You publish the Flow. Flows start as Draft (testing only) and become Published for real users (see the Flow lifecycle).
    3. You send it:
      • Inside a service window (the customer messaged you): send it as an interactive message with a button like "Book now".
      • Business-initiated: create a template with a FLOW button and send it like any template (sending a Flow).
    4. The customer taps the button, fills the screens and submits.
    5. You receive the response (via webhook) and act on it: create a booking, add a lead to your CRM, reply with a confirmation.

    Endpointless vs endpoint-powered

    Endpointless Flow Endpoint-powered Flow
    Data Static, or injected when you send Live data fetched as the user moves through screens
    Example Lead form, feedback form, product interest survey Real-time slot availability, live pricing, stock checks
    Build effort Lower (no server needed) Needs an endpoint (server)
    Meta's advice Preferred where possible Use only for screens that need live data
    Time limit n/a Endpoint requests time out after 10 seconds

    Meta's Flows best practices say endpointless Flows "often offer better experience", are faster to build, and should be used unless live data is needed.

    6 use cases for Indian businesses

    Business Flow Category of the message that carries it
    Dental clinic Book appointment: treatment → doctor → date → slot Service (if patient messaged) or utility/marketing template
    Salon Choose service + stylist + time Service or template
    Coaching institute Demo class sign-up: course, class, preferred batch Often from a CTWA ad (free entry point window)
    Real estate Site visit request: project, budget, BHK, visit date Service (from ad or website click-to-chat)
    D2C skincare Skin quiz → product recommendation Marketing template if proactive
    Any business Post-visit feedback form for a specific visit Utility template

    Hypothetical example: A Bengaluru coaching institute runs Click-to-WhatsApp ads. When a parent taps the ad and says "Hi", the bot replies with a "Book a free demo" Flow: student class, subject, preferred day, and a consent checkbox for updates. The submission lands in the lead pipeline, and a counsellor follows up the same day.

    Pricing: what you actually pay

    Meta's pricing page charges per message by category and doesn't list a separate Flows fee. In practice:

    • Flow sent in a service window (customer messaged first): a service message, free for the first 1,000 per business number per month (from October 1, 2026), then ₹0.115 to Indian numbers at list rate.
    • Flow sent via a marketing template: ₹0.8631 list rate (India, from October 1, 2026).
    • Flow sent via a utility template: ₹0.115 list rate.
    • From a Click-to-WhatsApp ad: messages in Meta's free entry point window aren't charged.

    All rates exclude taxes. Your platform may charge for Flow features separately.

    Best practices (from Meta's guidance)

    1. Keep it short. Meta suggests tasks take no more than 5 minutes.
    2. One task per screen, not too many components, and no more than 10 options per screen.
    3. Clear screen titles and CTAs ("Book appointment", "Confirm booking").
    4. End with a summary screen so users can review before submitting.
    5. Avoid login screens unless absolutely necessary.
    6. Make the first screen endpointless so the Flow opens fast.
    7. Set flow token expiry to 2–3 days so people can come back to it.

    Health monitoring: Throttled and Blocked

    Meta watches endpoint health. If your endpoint or screen navigation is unhealthy, a Flow becomes Throttled: it can still be sent, but only 10 messages per hour. If it gets worse, it's Blocked: it can't be sent or opened. When health improves, it moves back to Published. Keep your backend fast and monitored, especially during ad campaigns.

    Where WatsBerry fits

    WatsBerry gives slot sellers forms and Google Calendar booking inside WhatsApp, feeding a lead pipeline and reminders, and gives product sellers catalogue and order flows, all on the official Cloud API. Meta bills WhatsApp usage to your own payment method (0% markup on Meta's per-message rates), and WatsBerry charges a separate platform plan (₹1,599 / ₹2,999 / ₹5,999 per month + GST).

    Next step

    Describe the form or booking you'd like customers to complete in WhatsApp via watsberry.com, and I'll sketch the screens with you.

    Abbas Ali, Founder, WatsBerry

    Frequently asked questions

    What are WhatsApp Flows?

    WhatsApp Flows are structured, multi-screen experiences such as forms, booking screens and product selectors that open inside a WhatsApp chat. Meta describes them as a way to build structured interactions for business messaging, used for leads, recommendations, sign-ups and bookings.

    How much do WhatsApp Flows cost?

    Meta's pricing page doesn't list a separate Flows fee. You pay for the message carrying the Flow: a marketing or utility template if you start the conversation, or a service message if you send it inside an open customer service window. Your provider may charge for Flow features in its plan.

    Can I use WhatsApp Flows for appointment booking?

    Yes. A booking Flow can show services, staff, dates and available slots. Showing live availability needs a data endpoint connected to your calendar or booking system, and Meta says endpoint requests time out after 10 seconds, so the backend must be fast.

    Do I need a developer to build WhatsApp Flows?

    Simple endpointless Flows can be built in Meta's Flow Builder or a provider's no-code builder. Flows that fetch live data, such as slot availability or pricing, need an endpoint, which usually needs a developer or a platform that provides one.

    What happens if my Flow's endpoint is slow or failing?

    Meta monitors Flow health. An unhealthy Flow becomes Throttled, limited to 10 messages per hour, and if it gets worse it becomes Blocked, meaning it can't be sent or opened until health improves.

    Sources

    Start 14-day free plan · Pricing · Features

    Ready to grow revenue on WhatsApp?

    Start a 14-day free plan. Join the waitlist for invite-only access. Broadcast, automate, recover carts, and support customers on official WhatsApp Business API.