Summarise this article with:
On this page
- What a Click-to-WhatsApp ad is, and what it replaces
- The Free Entry Point conversation: 24 hours to reply, 72 hours to work
- Designing the funnel around those 72 hours
- Creative and pre-filled message pairings by objective
- Worked example: a hypothetical Kota coaching institute
- Attribution: carrying the ad reference through to your CRM
- What most teams get wrong about Click-to-WhatsApp ads
- Get started with InfiQ
Most teams run Click-to-WhatsApp ads the way they run lead-form ads. They buy the click, dump the contact into a sheet or a CRM, and a salesperson gets to it the next working morning. The ad spend is identical to a lead-form campaign, the follow-up is identical, and the result is roughly identical too — which is exactly why the channel disappoints so many of them.
The reason it disappoints is that they paid for a mechanic and then threw it away. When a user taps a Click-to-WhatsApp ad from the WhatsApp mobile app surface, Meta opens what its pricing documentation calls a Free Entry Point conversation. Your reply within 24 hours costs nothing, and that reply opens a 72-hour window in which every message you send — including templates that would otherwise be billed as marketing — is free. Reply on Monday morning to a Saturday click and you get none of it.
This guide is built around those 72 hours: how the window actually opens, what it excludes, how to design a greeting-and-qualification sequence that finishes inside it, and how to measure the result without inventing the numbers that most CTWA content is padded with.
Key points
- A Click-to-WhatsApp ad is a Meta ad whose call to action opens a WhatsApp conversation with a business number rather than sending traffic to a website or a lead form.
- A Free Entry Point conversation is a WhatsApp conversation that begins when a user messages a business from a Click-to-WhatsApp ad or a Facebook Page CTA button, and a business reply within 24 hours is free.
- The Free Entry Point mechanic applies to the WhatsApp mobile app only — not to WhatsApp Web or desktop — so a share of your ad-sourced conversations will never qualify no matter how fast you answer.
- Replying inside the Free Entry Point window opens 72 hours in which all messages, including template messages, are free, which makes the whole qualification and nurture sequence a cost question of timing rather than volume.
- Messages sent inside an open 24-hour customer service window do not count toward your per-user marketing message limit, and messaging limits only cap unique users contacted outside an open window.
- Meta may only change pricing on 1 January, 1 April, 1 July or 1 October, with one month's notice for a rate-card update and six months for a full pricing-model change, so verify the Free Entry Point terms on Meta's live pricing page before you build a budget on them.
What a Click-to-WhatsApp ad is, and what it replaces
A Click-to-WhatsApp ad is a paid placement on Meta's surfaces — Facebook and Instagram feeds, Stories, Reels and the placements Ads Manager currently offers for the objective you select — where the call to action opens a WhatsApp thread with your business number and, usually, drops a pre-written first message into the user's compose box. The user taps, the chat opens, they send that message, and you now have an inbound conversation from a person who has never given you an email address.
That last point is the structural difference. A landing-page funnel asks a stranger to load a page, read it, fill a form, and then wait for you to call a number they may not answer. A CTWA funnel moves them into a thread they already have open forty times a day, on an identity they cannot mistype, in a surface where your reply arrives as a notification rather than as an entry in a promotions tab.
CTWA versus a landing-page funnel
The honest comparison is not "CTWA is cheaper". Ad delivery costs are set in Meta's auction by your creative, audience and objective, and no article can tell you what a click will cost you this month. What differs is the shape of the funnel and where it leaks.
| Dimension | Landing-page or lead-form funnel | Click-to-WhatsApp funnel |
|---|---|---|
| Steps between ad and first contact | Tap, page load, read, form fill, submit | Tap, send pre-filled message |
| Identity you capture | Typed phone or email, often wrong | Verified WhatsApp number, always reachable |
| Time to first business response | Minutes to next business day | Seconds, if automated |
| Cost of the follow-up messages | Your own email or SMS cost | Free inside the 72-hour window, then per-message |
| Where the drop-off happens | Page load and form abandonment | Users who read the greeting and never reply |
| What you must build | Page, form, CRM hook, dialler discipline | Greeting logic, qualification, inbox routing |
| Consent captured | Explicit, on the form | Implied for this conversation only, not for marketing |
The last row is the one that costs teams their quality rating, and it comes back later in this guide.
The Free Entry Point conversation: 24 hours to reply, 72 hours to work
Meta's WhatsApp pricing documentation sets out the mechanic. If a user messages a business from a Click-to-WhatsApp Ad or a Facebook Page CTA button, and the entry happens from the WhatsApp mobile app rather than desktop or web, then a business reply within 24 hours is free and opens a 72-hour Free Entry Point window in which all messages — including templates — are free.
Read that as three separate conditions, because failing any one of them silently returns you to standard per-message billing.
| Condition | What it means in practice | What happens if you miss it |
|---|---|---|
| Entry surface | The user must arrive via a Click-to-WhatsApp ad or Facebook Page CTA button | An organic inbound message opens a normal 24-hour customer service window, not a Free Entry Point window |
| Device | Mobile app only — not WhatsApp Web, not desktop | The conversation is billed normally from the first reply, however fast you are |
| Reply timing | Your first reply must go out inside 24 hours of their message | No Free Entry Point window opens at all; templates in your sequence become chargeable |
Two things follow that are worth stating plainly. First, the device condition means a fixed share of your CTWA traffic can never be free, and you do not control that share — it is decided by which surface each user happens to be on. Second, the 24-hour reply condition is the only one of the three you fully own, which is why automated first response is not a nice-to-have on this channel. It is the price control.
The 72 hours are the actual product
Once the window is open, the economics invert. Outside a window, a marketing template to an Indian number is billed at whatever Meta's current India rate card says, and cost discipline means sending fewer messages. Inside the Free Entry Point window, all messages are free, and cost discipline means finishing the job before hour 72.
That changes funnel design in a specific way: you stop rationing touches and start sequencing them. A three-message qualification path you would never send to a cold list is fine here. A follow-up at hour 20, another at hour 44, a last-call at hour 68 — all free, if the window opened. The constraint is no longer money. It is attention and tolerance, which are real constraints, and the section on quality rating below is about respecting them.
One caution on durability. Meta may only change pricing on 1 January, 1 April, 1 July or 1 October, with defined notice periods — one month for a rate-card update, three months for a pricing add-on, six months for a full pricing-model change. Meta has already announced that from 1 October 2026 it resumes charging for service messages and for utility messages sent inside an open customer service window, both of which are free today. That announcement concerns the customer service window, not the Free Entry Point window, and the two are separate mechanics — but a channel strategy resting on a free allowance should be re-verified against the live pricing page every quarter. The Meta Business Agent Platform pricing breakdown covers what October actually changes.
Designing the funnel around those 72 hours
Here is the sequence shape that follows from the mechanic. Timings are a starting design, not a benchmark — adjust from your own reply-rate data.
| When | Move | Message type | Cost inside the window |
|---|---|---|---|
| Seconds after inbound | Automated greeting that names the ad's promise back to them | Non-template reply | Free |
| Same interaction | Qualification Flow: 3–5 fields, one submission | Interactive message | Free |
| Within minutes | Routed to a human with the ad reference and Flow answers attached | Non-template reply | Free |
| Hour 2–4 | The specific asset they qualified for — price list, brochure, slot options | Non-template or template | Free |
| Hour 18–24 | Follow-up on the single next action, no new offer | Template | Free |
| Hour 44–48 | Objection handling or an alternative path | Template | Free |
| Hour 66–70 | Explicit last message inside the window, plus a marketing opt-in ask | Template | Free |
| After hour 72 | Any further contact | Marketing template, chargeable | Billed at India marketing rate |
The hour-68 message is the one most teams do not have and most need. It is where you convert a free ad-sourced conversation into a contact you may legitimately message later, by asking for marketing consent in plain words while the window is still open and the context is still fresh. Ask on day six and you are paying for the privilege of asking.
The first reply must arrive in seconds, not minutes
The automated greeting is doing three jobs at once, and it is worth being explicit about them. It satisfies the 24-hour reply condition that opens the free window. It catches the user while they are still in the app, seconds after a tap, when reply probability is at its highest. And it sets the frame for the qualification questions that follow, so the Flow does not feel like an interrogation from a stranger.
Automate it. A human first response cannot be fast enough at any meaningful volume, and CTWA clicks do not respect IST office hours — a chunk of them land at 11pm and on Sundays. A greeting that fires from your platform in under five seconds, then hands off to a person during working hours with a stated response time, beats a human-only model at every volume above a trickle. InfiQ's chatbot and automation builder plus a shared team inbox is the standard arrangement for this.
Qualify inside the free window with a Flow, not twenty questions
Qualification by conversational bot costs you a message per field and a drop-off risk per turn. A WhatsApp Flow collects the same fields as one structured submission inside the chat, which is both a better experience and fewer messages — and after 1 October 2026, fewer in-window messages will matter for the customer service window too.
For a CTWA funnel, keep the Flow to three to five fields that decide routing and nothing else: intent, budget band, city or locality, timeline, preferred contact time. Everything else can be asked by the human who now has a reason to talk. Non-endpoint Flows are enough for almost all qualification because the options are static — the WhatsApp Flows implementation guide covers the endpoint decision and the version tracks that break Flows in production, and InfiQ Flows is a drag-and-drop way to build one without hand-authoring Flow JSON.
The contact you just acquired has not opted into marketing
A user who tapped an ad and sent a pre-filled message has started a conversation. They have not consented to a promotional broadcast next Thursday. Treating CTWA contacts as a marketing list is the fastest way to turn a healthy number yellow.
The mechanics back this up. WhatsApp dynamically caps how many marketing template messages any single user receives across all businesses, based on that user's recent read rate and inbox load, per Meta's per-user marketing limits documentation. It is not a fixed number, it adapts, and India is not among the excluded regions — the cap applies here. A throttled send returns error 131049, and retrying inside 24 hours risks further failures. Meanwhile quality rating is driven by user blocks and report taps, not by delivery success, so a list of people who never asked for marketing is a rating liability. The WhatsApp quality rating guide covers recovery when it has already gone wrong; the opt-in and DPDP guide covers collecting consent that holds up under India's DPDP regime.
There is a quieter upside here too. Messages sent inside an open 24-hour customer service window do not count toward the per-user marketing limit, and a messaging limit caps the number of unique users you contact outside an open window. A new business portfolio starts at a 250 messaging limit, so for a young account, ad-sourced inbound conversations are the one way to talk to more people than that tier suggests.
Creative and pre-filled message pairings by objective
The pre-filled message is the most under-used control in the whole setup. It is the first line of your funnel, it is visible in the ad before the tap, and because different ads can carry different pre-filled text, it is a free segmentation signal — you know which ad a person came from by what they said, before any attribution plumbing exists.
Write it as the user, in the user's words, specific enough to route on. "Hi" tells you nothing. "I want the 2BHK price list for Wakad" routes itself.
| Objective | Creative angle | Pre-filled message | What it segments | What the first reply should do |
|---|---|---|---|---|
| Lead generation, real estate | Single project, one configuration, price band on the creative | "Send me the price list and floor plan for [project name]" | Project and configuration interest | Send the floor plan, then a Flow for budget, possession timeline and loan need |
| Admissions, coaching or test prep | Batch start date and exam name, not the institute's history | "I want details of the [exam] batch starting [month]" | Exam, batch and urgency | Confirm batch details, then a Flow for class, target year and preferred centre |
| D2C product discovery | One hero product, one problem it solves | "Help me pick the right [product] for my skin type" | Category and use case | Two clarifying options, then a catalogue or size Flow |
| Cart and catalogue re-engagement | The product they viewed, plus availability, no discount | "Is [product] back in stock in size M?" | SKU and variant | Stock answer plus a one-tap resume path |
| Appointment booking, clinics | Service and location, with a booking verb | "I want to book a [service] appointment at [locality]" | Service line and branch | A slot-picker Flow against live availability |
| High-ticket B2B or BFSI | The specific outcome, no product name | "I want to understand [product] eligibility for my business" | Segment and intent depth | Two qualification questions, then a human with a named calendar slot |
| Offer or seasonal push | The offer terms stated on the creative | "Tell me more about the [offer name] offer" | Offer awareness and price sensitivity | Full terms in one message, then the next step, no drip |
| Support deflection from paid | The problem, in the customer's phrasing | "I need help with my order [order number]" | Existing customers, wrongly in a paid funnel | Order lookup Flow, then exclude this audience from the ad set |
That last row is a diagnostic. If a meaningful share of your CTWA inbound is existing customers with support questions, you are paying auction prices for conversations your organic channels should be absorbing, and your audience exclusions need work.
Worked example: a hypothetical Kota coaching institute
Take a hypothetical coaching institute in Kota running admissions ads for a January batch, receiving 3,000 CTWA conversations in a month. The numbers below are illustrative — the point is the structure of the arithmetic, not the values.
Assume, and then verify in your own data, that 2,400 of those 3,000 conversations arrive from the WhatsApp mobile app and 600 from desktop or web. Only the 2,400 are Free Entry Point eligible. Assume the nurture sequence inside 72 hours contains two template messages: a day-one follow-up and a day-two objection-handling message.
Design A — replies handled by the counselling team during office hours. Weekend and late-night clicks get answered the next working day, so on this illustration half the mobile-sourced conversations are replied to after the 24-hour deadline. That is 1,200 conversations where no Free Entry Point window ever opens.
- 1,200 conversations × 2 templates = 2,400 chargeable templates
- Plus the 600 desktop-sourced conversations × 2 templates = 1,200 chargeable templates
- Plus the 1,200 conversations that did open a window: 0 chargeable
- Monthly total: 3,600 chargeable marketing templates
Design B — automated greeting inside five seconds, every hour of every day. All 2,400 mobile-sourced conversations get a reply inside 24 hours, so all 2,400 open a 72-hour free window.
- 2,400 conversations × 2 templates = 0 chargeable templates
- Plus the 600 desktop-sourced conversations × 2 templates = 1,200 chargeable templates
- Monthly total: 1,200 chargeable marketing templates
The difference is 2,400 marketing templates a month, moved from chargeable to free by one operational change: answering fast enough. Multiply by the current India marketing rate — ₹0.94 per delivered message (ex-GST) — for the arithmetic in rupees: 2,400 × ₹0.94 a month.
Then note the third scenario, which is where most spend actually leaks. If the sales cycle runs past 72 hours — normal for admissions — every touch from day four onward is a chargeable marketing template that also needs valid marketing consent. On these volumes, a single day-five follow-up to all 2,400 is another 2,400 chargeable templates. That is the real argument for the hour-68 consent ask: it is the only cheap moment you will get. Pull Meta's current rate card or use InfiQ's WhatsApp cost calculator before you commit any of this to a budget, and the 2026 pricing guide explains the two-layer bill — Meta's rates plus your platform's — that this arithmetic sits inside.
Attribution: carrying the ad reference through to your CRM
The honest position on CTWA measurement is that it is harder than web attribution, not easier, and that most published CTWA performance figures are unsourced. There is no verified India-specific benchmark for CTWA cost per lead, click-through rate or conversion rate that this guide can give you. What you can do is build a measurement chain that produces your own numbers.
Three layers, and each one can be wired without guesswork.
Layer one: the referral payload. An inbound message that originates from a Click-to-WhatsApp ad arrives at your webhook with referral context identifying the ad it came from. Capture it on the first message and store it against the contact permanently — not on the conversation, which will be archived, and not in a log you never join to anything. The WhatsApp webhooks guide covers the plumbing, and InfiQ's CRM and e-commerce integrations are where this normally lands.
Layer two: the pre-filled message as a fallback key. Because you control the pre-filled text per ad, distinct wording gives you a second, independent signal of ad origin that survives even when the referral payload does not reach your CRM cleanly. Use it as a cross-check, not a substitute.
Layer three: your own outcome definition. Decide before the campaign what counts, and count it in your CRM rather than in Ads Manager: conversation started, Flow submitted, qualified, meeting or site visit booked, closed. Ads Manager can tell you what a conversation cost; only your CRM can tell you what a qualified conversation cost, and the gap between those two numbers is the whole point of the exercise.
Two disciplines make the resulting numbers trustworthy. Hold a control: run one ad set to a landing-page or lead-form destination alongside the CTWA set, same creative and audience, and compare qualified-lead cost rather than lead cost. And define your denominators once — count unique contacts, not conversations, or repeat enquirers will flatter every ratio you report. Teams that want this wired end to end usually start on InfiQ's 7-day free trial and connect the CRM before spending anything on ads.
What most teams get wrong about Click-to-WhatsApp ads
| Mistake | What actually happens | The fix |
|---|---|---|
| Replying during office hours only | Clicks that land at night or on Sunday miss the 24-hour deadline, no Free Entry Point window opens, and the whole nurture sequence becomes chargeable | Automated greeting within seconds, every hour, with a stated human response time |
| Assuming every CTWA conversation is free | The Free Entry Point mechanic is mobile-app only; desktop and web entries are billed normally from the first reply | Model your budget on a share of conversations qualifying, and track that share |
| Using "Hi" as the pre-filled message | You lose the cheapest segmentation signal available and every conversation starts from zero context | Write pre-filled text as a specific, routable request per ad |
| Letting the sequence spill past hour 72 | Day-four messages are chargeable marketing templates and need marketing consent you probably do not have | Compress the qualification and asset delivery into the first 24 hours; ask for marketing consent before hour 72 |
| Adding ad-sourced contacts to broadcast lists | Blocks and report taps drive quality rating down, per-user marketing caps throttle sends, and error 131049 starts appearing | Treat CTWA consent as conversation-scoped; run a separate, explicit marketing opt-in |
| Qualifying with a twenty-turn bot | Every turn is a drop-off point and a message, and the fields arrive as text you have to parse | One Flow, three to five fields, one structured submission |
| Optimising the ad and ignoring the greeting | Cheaper clicks into a weak first reply produce more conversations and fewer customers | Treat the greeting and first Flow as ad creative, and test them as often |
| Judging the channel on Ads Manager numbers | Cost per conversation says nothing about lead quality, and CTWA attracts existing customers with support queries | Measure qualified-lead cost in your CRM against a landing-page control set |
| Running one number for ads and broadcasts | A marketing-driven quality drop on a shared number damages your ad funnel and your transactional messaging together | Watch quality rating per number and separate high-risk sending where volume justifies it |
The pattern across all nine is the same. CTWA rewards operational readiness far more than creative cleverness, because the mechanic that makes it economically distinctive is triggered by your response time and destroyed by your calendar.
Get started with InfiQ
The teams that make Click-to-WhatsApp ads work are rarely the ones with the best creative. They are the ones whose first reply fires in seconds at 11pm on a Sunday, whose qualification takes one Flow rather than twenty messages, and whose CRM knows which ad set produced the site visit three weeks later. The mechanic Meta gives you is generous and narrow at the same time: 72 free hours, forfeited by a slow morning.
Ready to answer every ad-sourced conversation inside the free window? Start your 7-day free trial — InfiQ gets you live on the official WhatsApp Business API in about 2 hours, with InfiQ Flows for in-chat qualification and a shared team inbox that routes the conversation with its ad reference attached. Or book a walkthrough if you want to see it mapped to your own campaigns first.
