Meta documentation read on 2 September 2026, English render: Pricing on the WhatsApp Business Platform (page stamp 5 August 2026), Upcoming pricing updates for Meta Business Agent, service and utility messages (25 August 2026), the Text messages and Status webhook references (both 21 May 2026), Conversions API for Business Messaging (5 May 2026), Conversational components (16 June 2026), and three undated Business Help Center articles on creating ads that click to WhatsApp. Every count of our own reviews below is a tally of the fifteen files matched by sample-reviews/*-review.md, with the search string printed in Sources.

Click-to-WhatsApp ads (CTWA)· Channel feature

A Click-to-WhatsApp ad is a Meta ad, shown on Facebook, Instagram or WhatsApp, whose destination is a WhatsApp conversation with the advertiser rather than a web page. Tapping it opens a chat with a pre-written greeting and optional suggested questions; the user's first message reaches the business as an ordinary inbound message carrying a referral block that names the ad. If the user messaged from the Android or iOS WhatsApp app and the business replies within 24 hours, Meta opens a 72-hour free entry point window, timed from the reply, in which every message type is free of delivery charges. A click ID in the referral block lets the business report a later purchase or qualified lead back to Meta through the Conversions API.

By Chatbotscape Editorial· Methodology· Published 3 September 2026· Updated 3 September 2026

Click-to-WhatsApp Ads — The Ad That Opens a Chat, the 72-Hour Window It Can Earn, and Where Our Own Pages Got the Trigger Wrong

Quick answer: A Click-to-WhatsApp ad (Meta's help center writes "ads that click to WhatsApp"; the industry abbreviation is CTWA) is a paid Meta placement whose call to action opens a WhatsApp chat with your business instead of a landing page. Three things make it different from a link in a bio. First, the chat arrives pre-labeled: the user's opening message carries a referral object with the ad's ID, headline, body, media and a per-click identifier called ctwa_clid, so a chatbot can branch on which ad brought the person in before it says a word. Second, it can earn a free entry point window: Meta's pricing page says that if the user came from a Click to WhatsApp ad or a Facebook Page call-to-action button on the Android or iOS app and "you respond within 24 hours using any type of message, the message will be free, and a Free Entry Point ('FEP') window will be opened, starting from the time when you responded," and that "FEP windows remain open for 72 hours" during which "you can send any type of message to the user at no charge." Third, the click ID closes the loop: send it back with a purchase or lead event through the Conversions API and Meta can optimize the campaign toward people who actually buy in the chat. The part this entry adds is an audit of ourselves. Two of our own pages, in seven places, described the click or the user's first message as the thing that opens the 72-hour window. Meta's page says the business's reply opens it, and that the reply has to land within 24 hours. A bot that greets within a second makes the distinction invisible; a human inbox that answers on Monday morning does not get the window at all.

What the ad is, and what the user sees

In Ads Manager the format is a destination, not a campaign type. Meta's help center puts it plainly: "Ads that click to WhatsApp send people that click on your ads directly into conversations with your business on WhatsApp," and the same page lists the objectives that can carry it, with separate walk-throughs for the traffic or engagement, leads, sales and awareness objectives. The prerequisite is a connection between the WhatsApp number and either the Facebook Page or the business portfolio: "Under Facebook Page, choose the relevant Facebook page. The WhatsApp number connected to your Facebook page will be the one connected with the campaign." A grayed-out WhatsApp option means that connection is missing, and the same page walks through making it. Under the leads objective the default performance goal is "Maximize number of conversations," which is worth noticing because it is the goal the campaign will optimize toward until you give it a better signal (see attribution, below).

What the user sees on tap is a WhatsApp thread that already contains a message from you. Meta calls this the greeting, and the ad template lets you add suggested prompts: "Suggest prompts for people to tap and to encourage them to start conversations with your business. You can set up a greeting or suggest questions or messages that people can send." Newer ad setups can also open a WhatsApp Flow directly ("Collect info with a form in WhatsApp"), which Meta flags as not yet available to every account. The user then sends something, either a tapped prompt or their own words, and that send is what your systems receive.

A regional note from the same help page, because it changes what an EU business can buy: "Certain messaging-related metrics, ad campaigns and organic messaging features for businesses and ads delivered to and from Europe, Japan and South Korea will be unavailable." Meta does not enumerate which features on that page, and we did not find a page that does.

What your chatbot receives: the referral object

The first useful fact for a builder is that a CTWA conversation is not a special API. It is an ordinary inbound message webhook with one extra block. Meta's text-message webhook reference describes the trigger as "A WhatsApp user sends a text message to a business via a Click to WhatsApp ad (an ad with a WhatsApp message destination)," and the payload carries a referral object, annotated in Meta's own sample as "only included if message sent via a Click to WhatsApp ad," with these fields:

Field	What it holds	Meta's note
`source_url`	The ad's URL (an `fb.me` short link in the example)
`source_id`	The ad ID
`source_type`	`"ad"`
`headline`, `body`	The ad's headline and primary text
`media_type`	`image` or `video`
`image_url` / `video_url` / `thumbnail_url`	The creative	"Only included if the ad is an image ad" / "if ad is a video ad"
`ctwa_clid`	The per-click identifier	"omitted entirely for messages originating from an ad in WhatsApp Status"
`welcome_message.text`	The greeting text the ad carried	Example: "Hi there! Let us know how we can help!"

Two practical consequences. A flow builder that can read the referral block can route by source_id (one ad, one offer, one branch) and can echo headline back to the user to confirm which promotion they tapped, which is a cheap way to make an automated opener feel less generic. And ctwa_clid is the field to store immediately, against the contact, because it is the identifier the Conversions API requires to tie a sale in the chat back to the click that produced it. Meta's Conversions API page is explicit about the sequence: "Upon receiving the ctwa_clid, store it with the conversation. When a conversion has happened within a conversation, send the corresponding ctwa_clid via the Conversions API."

One thing we looked for and did not find: a sentence saying the referral block is attached only to the first message after the click. Meta's page says it is included when the message was "sent via a Click to WhatsApp ad," and no more. Partner write-ups commonly state the first-message-only rule; we have not seen it in Meta's text and are not repeating it as Meta's.

The free entry point window, read carefully

This is the part that is most often paraphrased and most often paraphrased wrong, so here is Meta's pricing page in its own order, as read on 2 September 2026:

"If a WhatsApp user messages you via a Click to WhatsApp Ad or Facebook Page Call-to-Action button using a device running our Android or iOS app (our desktop and web apps are not supported):"
"A 24-hour customer service window is opened (as normal)."
"If you respond within 24 hours using any type of message, the message will be free, and a Free Entry Point ('FEP') window will be opened, starting from the time when you responded."
"FEP windows remain open for 72 hours. While open, you can send any type of message to the user at no charge."
"Note, however, that the customer service window is independent of the FEP window, so if the customer service window closes, you will only be able to send template messages."

Four things follow that a shorter summary loses.

The reply opens the window, not the click. Until you respond, all that exists is the ordinary 24-hour customer service window that any inbound message opens. Respond at hour 23 and you get 72 hours from hour 23. Respond at hour 25 and there is no free window; the conversation is a normal one and every template you send is billed at its category rate. This is the single strongest argument for an automated first reply on an ad-fed number, and it is an argument about money rather than about experience.

Desktop and web clicks do not qualify. Meta says so in the first sentence. A user who taps your Instagram ad in a desktop browser and continues in WhatsApp Web opens a customer service window and nothing more. If the referral block arrives, your analytics will show a conversation that came from an ad and was charged anyway, and this is why.

The two windows run independently. The customer service window resets with each user message and closes 24 hours after the last one; the FEP window is a fixed 72 hours from your reply. If the user goes quiet for a day inside the 72 hours, you can still message them free, but only with a template, because free text needs an open customer service window. In practice a nurture sequence for an ad lead is a template sequence after day one, and those templates are free only until the FEP clock runs out.

The window is about delivery charges, and one thing is now excluded. Meta's page on the pricing changes dated 25 August 2026 says: "The 72-hour free entry point window is unchanged for message delivery. Messages sent within the 72-hour free entry point window, from Click to WhatsApp Ads or Facebook call-to-action buttons, remain free for message delivery." Its table answers "Is this message free in the 72-hour FEP?" with "Yes" for marketing, utility, authentication and service messages, and "No" for Meta Business Agent messages, which since 1 August 2026 are billed per token ("One global rate of $2.00 USD per 1 million (M) tokens," roughly "4–5 cents (USD) per message" by Meta's own estimate) regardless of window.

The status webhook lets you see the window working. Each delivered message's pricing block carries a type of regular, free_customer_service or free_entry_point, the last defined as "the message is free because it was sent within an open free entry point window," and a category that can read referral_conversion, which Meta glosses as "Indicates a free entry point conversation." If you want one number that tells you whether your first-reply automation is doing its job, it is the share of ad-sourced conversations whose messages carry free_entry_point.

The 1 October 2026 pricing change, and what it does to the window's value

Meta's pricing page, as read on 2 September 2026, states that "Effective October 1, 2026 – Meta will charge on a per-message basis for service messages," at the same rate as utility and authentication by market, with "a free monthly tier of service messages. Each month, every business phone number will receive 1,000 free service messages; Meta will only charge as of the 1,001st." It also states that from the same date "Meta will charge for utility messages sent in an open 24-hour customer service window." Per the same page, non-template messages have not been charged since 1 November 2024 and in-window utility templates since 1 July 2025. Neither change touches the FEP window, which Meta says "is unchanged for message delivery." The consequence is arithmetical: from October, a free-text reply to an ad lead is free inside the FEP and, past the 1,000-message allowance, billed outside it, so the window becomes worth more per conversation than it was in September, and an unanswered ad click forfeits more than it did. Meta also says that a business "that does not have a payment method on file by September 30, 2026" will have service messages stop delivering when they become chargeable. If your number was set up on a free tier and has never been billed, check that before October.

Attribution: the click ID and the Conversions API

The maximize-conversations goal optimizes toward people who send a message. If what you want is people who buy, Meta needs to be told who bought, and the mechanism is the Conversions API for Business Messaging. Meta's page defines the identifier: "The Click-to-WhatsApp Click ID (ctwa_clid) is a personal identifier, unique per click, that is exposed to the business when the user entering the conversation originated from a click to WhatsApp ad. This identifier needs to be sent back to Meta via the Conversions API call." The event payload names the channel ("action_source": "business_messaging", "messaging_channel": "whatsapp") and carries the WhatsApp Business Account ID and the click ID in user_data. The supported events are the ones a chat funnel actually produces: Purchase, LeadSubmitted, InitiateCheckout, AddToCart, ViewContent, the order-lifecycle set (OrderCreated, OrderShipped, OrderDelivered, OrderCanceled, OrderReturned), CartAbandoned, QualifiedLead, RatingProvided and ReviewProvided.

Three constraints from the same page are the ones that bite. Events "should only represent customer interactions that occur in the messaging thread, not conversions that occur on other channels like websites," so a lead who leaves the chat and buys on your site is a website conversion for pixel purposes, not a messaging one. "Meta does not assist with deduplicating events for Conversions API for Business Messaging," so the deduplication is yours. And purchase optimization through this API is available "for ads that click to Messenger and ads that click to WhatsApp only, but is not available for Instagram ad optimization at this time." The page states no retention period for a click ID and no attribution window; we looked, and are not inventing one.

For most small businesses the practical question is whether the platform does this for you. A vendor that says "Conversions API integration" for CTWA is claiming to store ctwa_clid from the referral block and post events with it; a vendor that says "CTWA analytics" may only be counting conversations by source_id. The two are not the same, and the question to ask is which events the platform sends and whether you can mark a conversation as a QualifiedLead from the inbox.

What our fifteen reviews say about CTWA, and what they do not

Six of our fifteen platform reviews mention Click-to-WhatsApp ads at all: AiSensy (29 matches, including a "CTWA Partner of the Year 2024" award that the review treats as conferred by Meta's global team; we did not re-verify the award for this entry), Wati (11), Blip (10), Chatbase (2), Botpenguin (1) and Chatfuel (1, for its Conversions API integration, which the review reads as enabling "CTWA ad-attribution closure server-side"). Nine reviews, including Manychat and SendPulse, do not use the phrase, which for a WhatsApp-capable platform is a gap in the review rather than evidence about the product.

Two reviews publish a score for it. Wati's "Click-to-WhatsApp Ad conversion tracking: 4.5/5" carries no projection label; Blip's "Projected Click-to-WhatsApp Ad conversion tracking: ~4.5/5" is labeled as anchored on the vendor's launch-partner status. Neither review, and no review in the corpus, mentions ctwa_clid, the referral object, the Conversions API for Business Messaging by that name, or the free_entry_point pricing type. Searching the fifteen files for ctwa_clid or "referral object" or "free entry point" returns nothing. So the two conversion-tracking scores rest on vendor documentation of an integration, not on a click ID followed from webhook to event, and the honest reading of both is "the vendor says it closes the loop, and we have not watched it close."

Where our own pages had the trigger wrong

Our WhatsApp channel guide stated in four places that a Click-to-WhatsApp ad "opens a conversation with a 72-hour free entry point window," or that Meta "grants" the window when the user "starts a conversation." Our WhatsApp automation guide said in three places, one of them a table cell, that the window opens "once the customer messages you" or "when someone starts a conversation from a Click-to-WhatsApp ad." What those pages said about the window's contents, that every outbound message including marketing is free inside it, was correct and stands. What was wrong was the trigger. Meta's page says the window opens "starting from the time when you responded," only if you respond within 24 hours, and only for conversations begun from the Android or iOS app. Our lead nurturing automation guide had it right and quoted Meta's sentence. At publish, all seven passages were corrected to say that the business's reply within 24 hours opens the window, and they now point here; the channel guide's sentence calling the window "the highest-leverage paid-acquisition channel" was left in place, because it is a judgment rather than a mechanic. The two review scores above were not edited; reviews are hand-edited and the flag is for that track.

How to check your own CTWA setup, in order

Is the first reply automated, and is it under 24 hours in every case? Read the pricing.type on the status webhooks for a week of ad-sourced conversations, or ask your platform for the equivalent report. Any ad-sourced conversation whose messages are regular rather than free_entry_point either came from a desktop click, got its first reply late, or is a template sent after the 72 hours ran out (a marketing template is billed either way; a utility template only once the customer service window has also closed, and from 1 October 2026 inside it too). Each of those has a different fix. (Free-text replies inside an open customer service window show free_customer_service, not regular, and are not anomalies.)
Is ctwa_clid stored? If your platform exposes the referral block, confirm the click ID is written to the contact record and not just logged. If it does not expose it, you cannot report conversions and should stop paying for a conversions-optimized campaign.
Which events go back? LeadSubmitted or QualifiedLead is enough for a service business; Purchase needs an order confirmation inside the thread, which the Conversions API page requires and which a website checkout does not satisfy.
What happens at hour 72? The FEP window closes; the customer service window may already be closed. Everything after that is a template, priced by category, and if the follow-up is promotional it is a marketing template, the category Meta prices highest in most markets and the one subject to the per-user marketing limit described in the WhatsApp message template entry. Our lead nurturing automation guide sets out the sequence that fits inside the window and the one that has to be paid for after it.
Is the ad's greeting the bot's first turn? The welcome_message.text you set in Ads Manager appears in the thread as if you sent it. Make sure the bot's opening line does not repeat it. This greeting is distinct from the up-to-four ice breakers configured at the phone-number level (80 characters each, no emoji, per Meta's conversational-components page), which show to anyone who opens a chat without an ad.

WhatsApp message template — the only message type allowed once the customer service window closes; free inside the FEP window, priced by category outside it.
WhatsApp Business API — the platform the ad delivers into, the BSP model and the history of conversation-based pricing.
WhatsApp Flows — the in-chat form an ad can now open directly, where the feature is available.
Webhook — the delivery mechanism for the referral block and the pricing type on every status update.
Lead generation chatbot — the bot that most often sits behind a CTWA number, and the qualification pattern it runs.
Chatbot broadcast — the opted-in follow-up campaign that begins once the free window has closed.

FAQ

What is a Click-to-WhatsApp ad?

A Meta ad on Facebook, Instagram or WhatsApp whose call to action opens a WhatsApp chat with the advertiser instead of a web page. The chat opens with a greeting and optional suggested prompts set in Ads Manager, and the user's first message reaches the business with a referral block identifying the ad.

Is a Click-to-WhatsApp conversation free?

It can be. If the conversation began on the Android or iOS WhatsApp app and the business replies within 24 hours, Meta opens a 72-hour free entry point window from the reply, in which marketing, utility, authentication and service messages are all free of delivery charges. Clicks from desktop or web WhatsApp, and conversations answered after 24 hours, get no free window. Meta Business Agent messages are billed per token in any window.

When does the 72-hour window start?

At the moment the business responds, per Meta's pricing page, not at the click and not at the user's first message. Respond at hour 23 and the window runs to hour 95; respond at hour 25 and there is none.

What is ctwa_clid?

The Click-to-WhatsApp click ID: a per-click identifier delivered in the referral block of the user's message. Stored against the contact and sent back with a Purchase, LeadSubmitted or similar event through the Conversions API for Business Messaging, it lets Meta attribute that outcome to the click and optimize the campaign toward it. It is omitted for ads placed in WhatsApp Status.

Can I send a marketing template inside the free entry point window?

Yes, and it is free of delivery charges while the window is open. If the customer service window has closed inside the 72 hours, a template is the only thing you can send, and it is still free until the FEP window closes.

Does the referral block arrive on every message from an ad lead?

Meta's webhook reference says the block is included when the message was sent via a Click to WhatsApp ad, and does not say whether later messages in the same thread carry it. Store the click ID on the first message and do not rely on seeing it again.

Which chatbot platforms handle Click-to-WhatsApp ads best?

Our reviews cannot rank this. Six of fifteen mention the format, two publish a conversion-tracking score, and none records following a click ID from the webhook to a Conversions API event. The WhatsApp channel guide tabulates partner status and integration depth, which is the closest proxy the corpus offers.

Sources

Meta for Developers, Pricing on the WhatsApp Business Platform (page stamp 5 August 2026), read 2 September 2026 in the English render: the history lines "As of November 1, 2024 - Meta does not charge for non-template messages" and "As of July 1, 2025 - Meta does not charge for utility templates in response to users"; the five-sentence free entry point definition quoted in full in the body ("using a device running our Android or iOS app (our desktop and web apps are not supported)", "starting from the time when you responded", "FEP windows remain open for 72 hours", "the customer service window is independent of the FEP window"); the per-message pricing statements effective 1 July 2025; the 1 October 2026 changes to service and in-window utility pricing and the 1,000-message monthly service allowance; the quarterly pricing calendar; and the volume-tier note that utility templates delivered within a free entry point window do not count toward tiers.
Meta for Developers, Upcoming pricing updates for Meta Business Agent, service and utility messages (page stamp 25 August 2026), read 2 September 2026: "The 72-hour free entry point window is unchanged for message delivery"; the table answering whether each message type is free in the FEP (marketing, utility, authentication, service: yes; Meta Business Agent: no); the per-token rate ("$2.00 USD per 1 million (M) tokens", "approximately 4–5 cents (USD) per message") effective 1 August 2026; the payment-method deadline of 30 September 2026; and "Meta will not offer volume tiers for service messages."
Meta for Developers, Text messages webhook reference (page stamp 21 May 2026), read 2 September 2026: the trigger sentence, the referral object's fields and Meta's annotations quoted in the table, the sample greeting text, and the statement that ctwa_clid is omitted for WhatsApp Status placements. The absence of a first-message-only rule is an argument from absence across this page and the Messages overview (17 June 2026), and is stated that way.
Meta for Developers, Status webhook reference (page stamp 21 May 2026), read 2 September 2026: the pricing.type values regular, free_customer_service and free_entry_point with their definitions, and the pricing.category value referral_conversion ("Indicates a free entry point conversation"), alongside marketing_lite, service and utility.
Meta for Developers, Conversions API for Business Messaging (page stamp 5 May 2026), read 2 September 2026: the definition of ctwa_clid as "a personal identifier, unique per click"; the store-then-send instruction; the event list; the messaging-thread-only rule; the no-deduplication statement; the Messenger-and-WhatsApp-only scope for purchase optimization; the required permissions whatsapp_business_management and whatsapp_business_manage_events. The page states no retention period or attribution window.
Meta Business Help Center, three undated articles read 2 September 2026: Create Ads that Click to WhatsApp in Ads Manager (the definition sentence, the objectives, the Page-and-number connection requirement, "Maximize number of conversations" as the default leads goal, the "Start conversation" prompts and the WhatsApp Flows form option, and the Europe/Japan/South Korea availability banner); About ads that click to message on Meta technologies (destinations and placements); Create ads that click to WhatsApp from your Facebook Page (the "Get more messages" goal and welcome-message step).
Meta for Developers, Conversational components (page stamp 16 June 2026), read 2 September 2026, for the distinction between phone-number-level ice breakers ("up to 4 ice breakers on a business phone number", 80 characters each, no emoji) and the ad-level greeting delivered in referral.welcome_message.text.
Chatbotscape review corpus (the fifteen platform reviews listed at /reviews), searched 2 September 2026 from the repository root. Denominator: ls sample-reviews/*-review.md | wc -l returns 15. Files mentioning the format: grep -liE 'click[- ]to[- ]whatsapp|CTWA' sample-reviews/*-review.md returns 6 (aisensy, blip, botpenguin, chatbase, chatfuel, wati); per-file match counts from grep -ciE on the same pattern are 29, 10, 1, 2, 1, 11. The absence claim: grep -rliE 'ctwa_clid|referral object|free entry point' sample-reviews/*-review.md returns nothing. The Wati score is quoted from wati-review.md ("Click-to-WhatsApp Ad conversion tracking: 4.5/5"); the Blip score from blip-review.md ("Projected Click-to-WhatsApp Ad conversion tracking: ~4.5/5 — anchored against Blip's documented launch-partner status"); the Chatfuel reading from chatfuel-review.md ("enables CTWA ad-attribution closure server-side without separate pixel work"). The corrected sentences are quoted from sample-reviews/channels/whatsapp-chatbot-guide.md and academy/whatsapp-automation-guide.md as they stood before this entry's publish edit.
Ahrefs Keywords Explorer, US overview and volume-by-country, queried 2 September 2026 — the demand, difficulty, CPC, global-volume, parent-topic and country-split figures in this entry's keyword note.
Chatbotscape evaluation methodology. /methodology (continuously updated).