WhatsApp Flows are forms that open inside a WhatsApp chat. The customer taps a button in your message, a full-screen form opens, and they fill in one or more screens (text fields, dropdowns, a date picker, a consent box) and submit. The answers reach your system as structured data, not free text to parse. A Flow lives in a WhatsApp Business Account and is sent through Meta's Cloud API, so QR-code tools built on WhatsApp Web have no access to it.

Meta's pricing has no Flow fee; you pay for the message that carries it. Sent as a template to a Brazilian number, it costs what its category costs: R$0.3217 for marketing, R$0.0350 for utility. Sent as a reply inside the 24-hour customer service window, it is a service message, charged since 1 October 2026 at R$0.0350 after 1,000 free per business number per month. The customer's answers are inbound messages, and Meta does not charge for those.

Of the 23 platforms in the catalog, 14 document Flows on their own pages; the table at the end shows which plans include them.

What a WhatsApp Flow looks like to your customer

A Flow starts as an ordinary message with a call-to-action button such as "Agendar horário". The button opens the first screen. Each screen has a title, up to 50 components and one footer button that moves forward or submits. Components include:

  • Inputs: short and long text (typed as email, phone or number), dropdowns with up to 200 options, radio buttons, checkboxes, date pickers, opt-in boxes, photo and document upload.
  • Display and logic: headings, body text, images, links, and If or Switch to show fields conditionally.

On submit, WhatsApp posts a summary bubble in the chat and your webhook receives the answers with the flow_token you set. Fields marked sensitive are masked in that summary.

Check devices before launch: Meta's Flows overview lists Android 6.0+ and iOS 12+ and excludes WhatsApp Web, yet its changelog of 11 November 2025 announced Flows on WhatsApp Web from December 2025. Test on what your customers use.

Where Flows fit for a business in Brazil

Flows replace the bot that asks for name, city, date and time in separate messages and gets typos back:

UseScreensUsual way to send itWhat Meta bills
Lead form from a Click to WhatsApp ad (name, interest, city, consent)1–2Reply in the 72-hour free entry point windowNothing in that window
Clinic or salon booking (service, unit, date, free slot)3–4, live slotsReply after "quero agendar"Service message
NPS after delivery of order 48211TemplateUtility if it names the order; marketing if generic
Quote request (product, quantity, CEP)2Reply in the windowService message
Webinar or event sign-up1–2Template to opted-in contactsMarketing

Meta's usual rules set the category: a feedback survey is utility only when it refers to a specific order or interaction (see the WhatsApp message templates guide).

How to build a Flow: three routes

  1. WhatsApp Manager, no code. Under Account tools, then Flows, name the Flow, pick a category (sign-up, appointment booking, lead generation, survey and others) and a starting template with or without an endpoint. The editor shows a live preview beside the Flow JSON. Meta also offers simple form Flows while you create a message template.
  2. Your platform's editor. BotConversa, Kommo, WATI and Twilio have their own form builders; others add a block that sends a Flow built in WhatsApp Manager (table below).
  3. Flow JSON through an API. Developers create and publish Flows with Meta's Flows API or a provider's API.

A new Flow is a draft that only test sends can reach. Publishing locks it: per Meta's Flows API, a published Flow cannot be modified or deleted, only deprecated, so a change means a new Flow (and a new template if it rode on one). Meta also requires a verified business and high message quality before customers get Flows.

A static one-screen lead form in the shape Meta documents, with Portuguese labels as a Brazilian store would ship it:

{
  "version": "7.3",
  "screens": [{
    "id": "LEAD",
    "title": "Fale com um consultor",
    "terminal": true,
    "layout": {
      "type": "SingleColumnLayout",
      "children": [
        { "type": "TextInput", "name": "nome", "label": "Nome", "required": true },
        { "type": "TextInput", "name": "cidade", "label": "Cidade" },
        { "type": "OptIn", "name": "aceite", "label": "Aceito receber ofertas pelo WhatsApp" },
        { "type": "Footer", "label": "Enviar",
          "on-click-action": { "name": "complete",
            "payload": { "nome": "${form.nome}", "cidade": "${form.cidade}", "aceite": "${form.aceite}" } } }
      ]
    }
  }]
}

The complete action closes the form and sends the three answers to your webhook.

Endpoint or no endpoint

A Flow without an endpoint carries everything in its JSON: fixed options, fixed screens, answers delivered at the end. That covers most lead forms, surveys and sign-ups.

You need an endpoint when a screen depends on live data: open slots in a clinic's calendar, stock at a store, shipping cost for a CEP. WhatsApp then calls your HTTPS server on each data_exchange action, and the server returns the next screen. Meta's requirements:

  • Encryption: a signed public key per number; requests arrive encrypted (RSA and AES-GCM) and replies go back encrypted.
  • Speed: requests time out after 10 seconds; Meta's monitoring guide asks for replies under 1 second.
  • Health: the endpoint answers Meta's periodic ping, and the account subscribes to Flows webhooks.
  • Penalties: high error rates or latency move the Flow to Throttled (10 Flow messages per hour), then Blocked (nobody can send or open it) until it recovers.

Ask who runs that server; Sinch, for one, routes data-channel Flows through its Professional Services team. Submissions arrive as webhook events, covered in the WhatsApp webhooks setup guide.

What a WhatsApp Flow costs in Brazil

How the Flow is sentMeta's charge per delivered message to Brazil
Marketing template (lead form, event sign-up, offer)R$0.3217
Utility template outside the window (survey on a named order)R$0.0350
Utility template inside the 24-hour windowR$0.0350 since 1 October 2026
Flow message (not a template) replying inside the windowR$0.0350 since 1 October 2026, after 1,000 free per number per month
Any of these in the 72-hour free entry point window (Click to WhatsApp ad, Facebook Page button)Free

Taps, screen changes and the submission come from the customer, so a four-screen Flow is billed as one message, not four (BotConversa's help says the same). Your confirmation afterwards is a second message, and your provider may add a fee per template. The monthly picture, plan included, is in WhatsApp API pricing in Brazil.

The cheapest way to run WhatsApp Flows

Building is free in WhatsApp Manager, and the Flow itself has no price. The bill is messages plus whatever the platform charges.

  • Straight on the Cloud API, you pay Meta's rates only, but a developer has to send the Flows and store the answers.
  • No monthly fee: in the catalog, Gupshup and Twilio. Gupshup and Twilio both document Flows.
  • Per template sent, on each platform's scored plan, cheapest marketing template first. A row shows the template price, not Flows support:
PlatformMarketingUtilityHow it bills
360dialogR$0.3217R$0.035Meta's rate at cost
KommoR$0.3217R$0.035Meta's rate at cost
respond.ioR$0.3217R$0.035Meta's rate at cost
TwilioR$0.3474R$0.0607Meta's rate + provider fee
GupshupR$0.3628R$0.0761Meta's rate + provider fee
RD Station ConversasR$0.39R$0.04Provider's all-in price
SendPulseR$0.39R$0.051Provider's all-in price
BotConversaR$0.50R$0.05Provider's all-in price
VTEX CX Platform (Weni)R$0.5141R$0.0566Provider's all-in price
ZenviaR$0.55R$0.55Provider's all-in price
HuggyR$0.5913R$0.2571Provider's all-in price
Blip GoR$0.69R$0.69Provider's all-in price
  • Whole month in the catalog's small-business scenario (plan, seats, Meta fees and markup), cheapest first:
PlatformCore monthly cost
SendPulseR$146.00
HuggyR$326.97
KommoR$343.48
GupshupR$672.53
respond.ioR$1,058.14
ZenviaR$1,150.00
VTEX CX Platform (Weni)R$2,013.11

Before choosing on price, match each row with the next section: respond.io lists Flows as an open request, VTEX CX uses them only inside its payment agent, and Zenvia ties them to certain account types.

Which platforms in the catalog document WhatsApp Flows

What each vendor's own page said on 25 September 2026, alphabetical:

PlatformHow Flows work there, per its docsPlan or account condition
360dialogBuilt in WhatsApp Manager or via its Partner API; sent as template or regular messageNone stated
Blip PlatformCreated through Blip's command API, sent from Blip Builder; paid third-party editor in the Blip StoreNone stated
BotConversaOwn form editor; sent by a "Fluxo completo" button or in a templateOfficial API connection
BotmakerWritten in JSON or created in Meta (synced in about 30 minutes); sent from Bot DesignerNone stated
GupshupBuilt in Meta's editor, run as a Flow journey in Bot Studio; partner APIs tooNone stated
Huggy"Enviar WhatsApp Flow" action; answers saved as variablesHuggy as WhatsApp provider
InfobipMeta's editor, Infobip's API or an AI builder (early access); templates, Broadcast, Answers chatbotsNone stated
KommoFlow templates built in Kommo, up to 8 screens, answers saved to CRM fieldsAdvanced or higher for Salesbot and Broadcasting
SendPulseForm template made in WhatsApp Manager, sent from chatbot flows, campaigns, chat or APINone stated
SinchSent through the Conversation APISet up by Sinch Professional Services
TrebleFlows block in the conversation editor; answers to variables, HubSpot or Google SheetsNone stated
Twiliotwilio/flows from its Content Template Builder (no endpoint) or whatsapp/flows built in MetaApproved template for twilio/flows
WATIDrag-and-drop editor; sent in templates, campaigns, API or chatbot nodeGrowth: 0 Flows; Pro: 2; Business: 10
Zenvia"WhatsApp Flow" content in the Customer Cloud bot builder; Flow made in MetaNLU Enterprise, or Customer Cloud with interoperability

Narrower use. VTEX CX Platform (Weni) collects a saved card's CVV through a WhatsApp Flow inside its One-click Payment agent for VTEX stores; its docs do not cover building your own Flows. In-chat payments are in the Pix and payments guide.

Requested, not documented. respond.io lists Flows as an open request on its public roadmap (team reply of 29 May 2026: "looking into this"). Manychat has no help article on Flows; a request for native WhatsApp forms is open in its community.

Not found on public pages on 25 September 2026: Blip Go, Digisac, Octadesk, Poli Digital, RD Station Conversas and Umbler Talk. Ask them, and ask any vendor whether it hosts the endpoint when a Flow needs live data.

About this guide

Written by the editorial team of WABA Index, an independent catalog of WhatsApp Business platforms for companies selling in Brazil. No platform pays for its position or coverage, and the page carries no affiliate links.

Methodology

On 25 September 2026 we read Meta's WhatsApp Flows documentation and pricing pages, and searched the site and help center of every catalog platform for Flows; the pages we cite are listed in the sources. The catalog cards do not record Flows yet, so platform statements come from each vendor's own pages as opened that day. Meta's rates, platform prices and monthly costs render from the catalog data, as the methodology explains. Nothing was tested hands-on, and no Flow was built or sent.

Last updated

7 October 2026. Facts and sources were checked on 25 September 2026; prices, Meta rates and scores in the tables are read from the catalog data when the page loads.

FAQ

Are WhatsApp Flows free?

The Flow is; the message carrying it is billed as a template by category, or as a service message inside the 24-hour window after 1,000 free per number each month.

Do I need a developer?

Not for static forms built in WhatsApp Manager or a platform's editor. You need one for an endpoint, or to receive answers on the bare Cloud API.

Can I edit a Flow after publishing it?

No. Meta locks published Flows; deprecate the old one and publish a new one.

Do Flows work in the WhatsApp Business app?

Meta documents Flows only for the WhatsApp Business Platform, not for the app.

How long can a Flow be?

Meta allows 50 components per screen and 10 branches in the routing model, and advises one task per screen. Builders add caps, such as Kommo's 8 screens.