A Click-to-WhatsApp ad is a Facebook or Instagram ad whose button opens a WhatsApp chat with your business instead of a website. You build it in Meta Ads Manager, or from a post on your Facebook Page, and it needs a WhatsApp number connected to that Page or to your business portfolio. The number can run on the WhatsApp Business app or on the WhatsApp Business Platform, the official API (Meta Business Help Center).
You pay Meta for the ad at the budget you set. On the official API, the conversation that follows can cost nothing: when a customer taps the ad in the WhatsApp app for Android or iOS and you reply within 24 hours, Meta opens a 72-hour free entry point window in which every message is free, templates included (Meta pricing docs). Meta kept that window free when it started charging for service messages on 1 October 2026.
The API also tells you which ad each chat came from, so a bot can greet the lead with the right offer and your platform can later report the sale back to Meta.
How to set up a Click-to-WhatsApp ad in Ads Manager
First connect the WhatsApp number to your business's Facebook Page, with yourself as a Page admin, or add it to your business portfolio. Then, following Meta's Help Center steps for the Sales, Traffic or Engagement objective:
- In Ads Manager, click + Create and pick the objective. Meta documents WhatsApp as a destination for Traffic, Engagement, Leads, Sales and Awareness.
- In the ad set's Conversion section, choose Message destinations as the conversion location, select the Facebook Page and tick WhatsApp. With the Leads objective you select WhatsApp directly, and the performance goal defaults to "Maximize number of conversations". If WhatsApp is grayed out, click Connect account and enter the number.
- Set the budget, schedule, audience and placements. Meta may show Advantage+ switched on for audience and placements.
- At the ad level, open Message template. "Start conversation" sets a greeting and suggested prompts that people tap to send. "Collect info with a form in WhatsApp" attaches a WhatsApp Flow, a form inside the chat, not yet available to every advertiser.
- Preview, then publish.
The shorter route starts on your Facebook Page: Advertise, the goal "Get more messages", WhatsApp as the app, then a welcome message, audience and budget. It works only with posts that carry links, videos or single photos (Help Center). On the API, a developer can also create the greeting and quick replies through Meta's welcome message sequences endpoint and select them in Ads Manager.
The free 72-hour window, condition by condition
The window belongs to the official API's pricing, and every condition counts:
| Condition | What Meta's pricing page says |
|---|---|
| Entry point | A Click to WhatsApp ad or a Facebook Page call-to-action button. A wa.me link on a website or profile is not on the list. |
| Device | The customer uses WhatsApp on Android or iOS; desktop and web are not supported. |
| Your reply | Within 24 hours, any message type. That reply is free and starts the window. |
| Length | 72 hours from your reply. Every message, templates included, is free. |
| Customer silence | The 24-hour customer service window runs separately. If it closes, you can send only templates, still free while the 72 hours last. |
An example. A customer in Recife taps your ad on Monday at 10:00 and writes. Your bot answers at 10:01, free, and the window runs until Thursday at 10:01. If the customer goes quiet on Monday afternoon, from Tuesday afternoon you can send only templates, at no charge. From Thursday at 10:01 Meta's normal rates return: R$0.3217 for a marketing template, while free-form replies count against the number's 1,000 free service messages a month and then cost R$0.0350 each.
Meta's page on the October 2026 changes says messages in this window "remain free for message delivery"; replies written by Meta Business Agent, Meta's own AI agent, are still charged for tokens. The pricing guide adds up the rest of a monthly bill.
Qualifying ad leads with a bot
An ad lead comes with a deadline: reply within 24 hours or lose the free window. A bot answers in seconds, at night and on Sundays too, which is the practical reason to connect the ads to an API platform rather than one phone. It can recognize the lead in three ways:
- A keyword from the ad. The suggested prompts are ordinary messages the customer sends (Help Center), so a bot with keyword triggers catches them if the keyword sits inside the prompt.
- Ad data in the webhook. On the Cloud API, a message that starts from an ad carries a
referralobject with the ad ID, headline, primary text, media andctwa_clid, the click ID (Meta webhook reference). A flow can branch on the ad ID, so the Black Friday ad gets the Black Friday answer. The webhooks guide covers receiving these events. - A form in the ad. With "Collect info with a form", the customer fills in budget, timeline or preferences, or chooses to chat instead. Responses appear in the chat thread on the Business app; on the Cloud API they arrive by webhook for your CRM (Help Center). Forms work only on ads with WhatsApp as the single destination, and the Flows guide explains how to build one.
Meta recommends its ready-made "Automated chat" questionnaire for Messenger and Instagram Direct; on WhatsApp the questions come from a form or your own bot. Meta's advice: ask only what qualifies the lead, most important question first. For a Brazilian store that is usually the product, the CEP for shipping and Pix or card. Then hand the chat to a seller while the window is open, as the chatbot guide describes.
Tracking which ad produced the sale
Ads Manager counts "Messaging conversations started", people who wrote for the first time or after 7 days of inactivity (Help Center): chats, not revenue.
To tell Meta which chats became leads or orders, Meta documents the Conversions API for Business Messaging. You store the ctwa_clid with the conversation. When the sale happens, you send an event such as Purchase or LeadSubmitted to your dataset, with action_source set to business_messaging, messaging_channel set to whatsapp and your WhatsApp Business Account ID. The event shows up in Events Manager and feeds the ad's optimization. Meta addresses that guide to messaging partners and asks for advanced app permissions and Marketing API access, so in practice your platform sends the events.
Two limits: the click ID is omitted for ads placed in WhatsApp Status, and Meta's Automatic Events API, which spots lead and purchase events in new ad threads with pattern matching and language analysis, reaches only businesses onboarded through a tech provider's Embedded Signup that opt in. It is not offered in the European Union, the United Kingdom or Japan.
Which platforms document ad-lead flows
The catalog does not record ad features, so this list comes from each vendor's own pages, read on 25 September 2026:
| Platform | What its documentation describes |
|---|---|
| Blip Platform | Blip Ads Manager creates the ad inside Blip and sends replies to a chosen bot flow |
| Botmaker | A Meta Ads integration that reports conversion events from bot blocks |
| Gupshup | Console links ads to journeys with Lead and Qualified Lead goals |
| Huggy | Flow variables with the ad ID, headline and click ID, on Huggy's own WhatsApp provider only |
| Infobip | Meta Ads reporting, a conversions API and a chatbot block for Purchase and LeadSubmitted |
| Kommo | Ad UTMs on the lead card and a Conversions API widget, Pro plan only for connections made since 1 June 2026 |
| Manychat | A "User clicks a CTWA Ad" trigger tied to an ad; its Conversions API article covers Messenger and Instagram only |
| respond.io | A Click-to-Chat Ads trigger with ad and campaign data, and a step that sends Lead and Purchase events |
| SendPulse | Ad questions that start chatbot flows by keyword, and a Conversions API switch for subscriptions, form submissions and purchases |
| Sinch | Ad referral data, click ID included, on inbound Conversation API messages |
| Treble | An "Eventos da Meta" block that sends purchase and cart events, only for chats started from an ad |
| Twilio | A ReferralCtwaClid parameter on inbound webhooks since March 2024 |
| WATI | A bot that asks qualifying questions (product, budget, location) and routes to a team, store or agent |
| Zenvia | A Zenvia chatbot picked per campaign inside Meta's ad setup; in beta, switched on by request |
360dialog documents the ad setup and the 72-hour window, and Octadesk's help center explains the window; neither page describes an ad trigger. On the public pages of Blip Go, BotConversa, Digisac, Poli Digital, RD Station Conversas, Umbler Talk and VTEX CX Platform (Weni) we found blog posts or chat links, but no help page for an ad trigger or conversion reporting. Per the cards, Manychat's ad trigger needs Pro or above, and respond.io's workflows start on Growth.
What it costs, and the cheapest way to answer ad leads
Three costs, and only the platform's plan is a fixed monthly amount:
- The ad. Whatever budget you set in Ads Manager, billed by Meta. The catalog does not track ad prices.
- Meta's message fees. Zero inside the 72-hour window. After it, a follow-up offer is a marketing template at R$0.3217, and it needs the customer's opt-in; the marketing messages guide covers the rules.
- The platform. Meta's zero is not always the provider's zero. Passing Meta's fees through at cost adds nothing per message; a provider fee or an all-in price may apply inside the free window too. The catalog does not record that rule, so ask before launch. Per template sent after the window:
| Platform | Marketing | Utility | How it bills |
|---|---|---|---|
| 360dialog | R$0.3217 | R$0.035 | Meta's rate at cost |
| Kommo | R$0.3217 | R$0.035 | Meta's rate at cost |
| respond.io | R$0.3217 | R$0.035 | Meta's rate at cost |
| Twilio | R$0.3474 | R$0.0607 | Meta's rate + provider fee |
| Gupshup | R$0.3628 | R$0.0761 | Meta's rate + provider fee |
| RD Station Conversas | R$0.39 | R$0.04 | Provider's all-in price |
| SendPulse | R$0.39 | R$0.051 | Provider's all-in price |
| BotConversa | R$0.50 | R$0.05 | Provider's all-in price |
| VTEX CX Platform (Weni) | R$0.5141 | R$0.0566 | Provider's all-in price |
| Zenvia | R$0.55 | R$0.55 | Provider's all-in price |
| Huggy | R$0.5913 | R$0.2571 | Provider's all-in price |
| Blip Go | R$0.69 | R$0.69 | Provider's all-in price |
For the bot, the cheapest route is the lowest plan with keyword triggers. The catalog confirms them on these scored plans, cheapest first:
| Platform | Plan | Price | Setup fee | Score |
|---|---|---|---|---|
| Twilio | Pay-as-you-go (Programmable Messaging + Studio) | No monthly fee, pay per message | No setup fee | 44.4 |
| SendPulse | Profissional (Pro), 500 subscribers | from R$95/month | No setup fee | 81.4 |
| Kommo | Avançado (Advanced) | from $30/month | No setup fee | 61.3 |
| Manychat | Pro | from $39/month | Setup fee not published | 38.0 |
| BotConversa | Plano Pro + API Oficial | from R$299/month | Setup fee not published | 56.5 |
| WATI | Growth | from R$369/month | No setup fee | 40.8 |
| Poli Digital | Plano Entrada | from R$369.90/month | + from R$1,197.90 one-time setup | 52.5 |
| Gupshup | Console (Automate & Grow) | from $100/month | No setup fee | 44.9 |
| Botmaker | Standard | from R$600/month | Setup fee unclear: sources disagree | 64.6 |
| Zenvia | Specialist | from R$700/month | + R$649 one-time setup | 62.8 |
| Huggy | Intermediário | from R$729/month | No required setup fee (optional service R$1,250) | 49.1 |
| respond.io | Growth | from $199/month | Setup fee not published | 49.5 |
| RD Station Conversas | Basic | from R$1,099/month | + R$1,999 one-time setup | 45.6 |
| VTEX CX Platform (Weni) | A partir de 1.000 conversas/mês | from R$1,900/month | No setup fee | 63.7 |
| Treble | Base plan (SMB) | from $399/month | Setup fee not published | 42.9 |
| Octadesk | One | from R$2,499/month | + one-time setup fee on request | 51.4 |
| Infobip | AgentOS | from $530/month | + one-time setup fee on request | 57.3 |
| Blip Platform | Super | from R$7,292/month | Setup fee not published | 64.4 |
| Digisac | Configuração de entrada (proposta comercial, sem WABA) | from R$197/month + official WhatsApp API on request | No setup fee | 56.1 |
| Sinch | Conversation API — WhatsApp channel | Enterprise: price on request | Setup fee not published | 46.8 |
In the catalog's small-business scenario, the lowest complete monthly cost belongs to SendPulse, R$146.00 a month. Gupshup and Twilio charge no monthly fee on their cheapest official-API plan and bill per message instead.
Related guides
- WhatsApp API pricing in Brazil
- WhatsApp chatbots for Brazilian businesses
- WhatsApp Flows for business
- WhatsApp marketing messages
- Setting up WhatsApp webhooks
- Choosing a WhatsApp CRM for Brazil
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 pricing pages, Help Center articles on ads that click to WhatsApp, the webhook reference, the Conversions API and Automatic Events API guides, and the vendor pages in the sources. Ad features are not catalog facts, so each platform statement cites the vendor's own page; plan limits come from the platform cards. Prices, Meta rates and scores render from the catalog data, as the methodology explains. No ad was run and nothing was tested hands-on.
Last updated
6 November 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 messages from Click-to-WhatsApp ads free?
On the official API, yes, for 72 hours, if the customer tapped the ad in the WhatsApp app on Android or iOS and you replied within 24 hours. The ad itself is paid, and your platform may still bill its own per-message fee.
Do I need the WhatsApp Business API to run these ads?
No. Meta accepts a number on the WhatsApp Business app. The API adds the ad data in each chat, bots, form responses by webhook and conversion reporting. To keep the app on the same number, see the coexistence guide.
Why was a chat from an ad charged?
A condition failed: the reply came after 24 hours, the customer used WhatsApp Web or desktop, the chat began from a link, or the message went out after 72 hours.
Can I message an ad lead after the window closes?
Only with an approved template, charged at Meta's rate for its category. A marketing template also needs the customer's opt-in.