WhatsApp Business Platform
Click-to-WhatsApp ads in India: setup, auto-reply, and measurement playbook
How Indian brands run Click-to-WhatsApp ads on official Cloud API: Page–WABA link, ice-breaker handoff to inbox or flows, auto-reply rules, and measurement without invented ROAS.
Join the beta waitlist See pricing Explore features Blog Resources
What Click-to-WhatsApp ads are (and are not) in India
A Click-to-WhatsApp (CTWA) ad sends the tap from Facebook, Instagram, or Audience Network straight into WhatsApp chat — not a landing page that leaks UPI intent.
That only works cleanly on official Cloud API: a WABA, a Facebook Page linked to that WhatsApp number, and an Ad Account. It is not a grey blaster on the founder’s phone. If you still need the API itself, start with how to get WhatsApp Business API in India.
WatsBerry splits CTWA into two layers (features / solutions):
| Layer | Job | What you connect |
|---|---|---|
| A — Conversation | Click → chat. Capture referral / ctwa_clid, show Results, optionally send Conversions API events |
Your existing WABA token. No ads_management required. |
| B — Ads management | Create/pause CTWA campaigns from WatsBerry Ads Manager | Separate Login for Business: Business portfolio + Ad Account + Page. Spend stays on Meta. |
You can run ads in Meta Ads Manager and still use Layer A. Creating every campaign type inside WatsBerry is higher ads-management access, not a claim that every plan is a full Ads Manager clone. Comparison cards list CTWA attribution across plans; in-app create is the extra layer.
WatsBerry is invite-only beta. Join the waitlist before you pour spend onto a number that is not on Cloud API.
Setup checklist (India media buyers)
1. Official WABA on the destination number. Embedded Signup through WatsBerry Integrations. Unofficial tools will not give you durable CTWA webhooks.
2. Page ↔ WhatsApp link. In Meta Business Suite, the Facebook Page used for the ad must be linked to the WhatsApp number. Ads Setup in WatsBerry includes a Page–WhatsApp link guide because this is the #1 “ad won’t publish” failure.
3. Ad Account payment method. CTWA media spend is Meta’s ads invoice, separate from WhatsApp conversation fees and the WatsBerry plan. Three bills is normal: ads + Meta messaging + platform.
4. Create the ad — two valid paths
- Meta Ads Manager: engagement / messages objective, Click-to-WhatsApp destination, India geo, placements you actually want (Feed vs Stories).
- WatsBerry Ads Manager (Layer B): Ads Setup → connect Ad Account + Page → Campaigns → Create. Campaign = objective, Ad set = audience + budget, Ad = creative. Save Paused until the welcome path is ready.
5. Creative that belongs in chat. Product, price honesty, and a single next step. COD-heavy catalogues should not promise “instant delivery nationwide” in the primary text. Ice breakers belong here — they are the first reply, not a second ad.
6. Do not launch into a silent inbox. Wire auto-reply / bot / hours before you spend. A paid click into a dead chat trains the user to block you.
Auto-reply and handoff playbook
CTWA is won in the first two messages, not the seventh broadcast.
On the ad
- Use ice breakers (short suggested replies) that match the offer: “See price”, “Size guide”, “Talk to sales”.
- Keep the WhatsApp greeting / welcome aligned with the ad. Bait-and-switch (“50% off” on the ad, full price in chat) burns quality rating.
First automated reply (pick one stack, not all of them)
| Tool | Use when | Guardrails |
|---|---|---|
| Auto-reply | Off-hours or a single acknowledgement | WatsBerry sends one auto-reply per conversation per 24 hours. Exclude keywords like STOP. Platform blocks bot-to-bot loops. |
| Chatbot / AI FAQ | The same questions every click asks (price, pincode, COD) | Ground answers in Bot Knowledge. Handoff to a human when confidence is low. AI FAQ is on Pro and Growth. |
| Campaign flow | A structured path (form, catalogue, appointment) | Opt-in / keyword / commerce triggers. Don’t fire a marketing template at someone who just messaged you — you are already in the care window. |
| Shared inbox | Anyone who says “talk to someone” or looks ready to pay | Assign the thread. This is the support / convert job CTWA is for. |
Suggested India sequence (playbook, not a KPI claim)
- Ice breaker tap or first user message → capture
ctwa_clid. - Immediate useful reply (stock, pincode, or a catalogue card) — not “Dear sir we will get back.”
- If they stall, one reminder inside the open window. After 24 hours, use an approved utility or marketing template that matches the job — see marketing vs utility.
- Human inbox for objections, COD confirmation, and address quality. Recovery-style discount storms belong in cart recovery, not on every ad click.
Working-hours settings can swap in the auto-reply after hours. Agents should still pick up the same thread in the morning — the ad already paid for the conversation.
Measurement notes (no invented ROAS)
What we do ship, and what we will not invent:
- Ads Results show CTWA referrals (chats that arrived with a click id), cost-per-chat style metrics when spend is available, and attributed sales when a conversion can be tied back.
- Insights sync from Meta on a delay — on the order of about six hours for active in-app campaigns (or tap Sync). Do not reconcile finance to a five-minute dashboard.
- Conversions API (CAPI): when someone arrived with
ctwa_clidand later converts (purchase, lead, booking), WatsBerry can relay that event to Meta so the ad set can optimise. Attribution still works if CAPI is off; optimisation is weaker. - Instant Form / Google form leads appear under Leads. They are not the same as a WhatsApp CTWA chat.
We do not publish a “typical India CTWA ROAS” or a conversion-rate benchmark. Your COD rate, creative, and reply speed dominate. Track cost per started chat and revenue on attributed chats; ignore vanity clicks that never opened WhatsApp.
Meta ads billing ≠ WhatsApp template billing. A cheap conversation can still be expensive if you later blast that list as marketing templates. Plan the mix with WhatsApp Business API pricing in India 2026.
Next: features for inbox, flows, and CTWA; solutions for Click-to-WhatsApp growth; pricing for plans. Ready to run this on official API? Join the beta waitlist.
Frequently asked questions
Do I need WatsBerry Ads Manager to run Click-to-WhatsApp ads?
No. You can create CTWA ads in Meta Ads Manager. WatsBerry still captures the WhatsApp referral / ctwa_clid on the connected WABA and can show Results plus optional CAPI. In-app campaign create is the optional ads-management layer.
Are CTWA replies billed as marketing templates?
The ad click opens WhatsApp. When the customer messages you, the customer-care window typically opens — free-form inbox replies are not a marketing-template blast. Follow-ups after the window need an approved template in the right category. Confirm live Meta rules and rates on Meta’s pricing page.
Can unofficial WhatsApp tools run CTWA ads?
Serious Click-to-WhatsApp ads, catalogue, and durable webhooks expect an official WABA. Grey Web-automation tools are a poor destination for paid traffic. See /resources/official-whatsapp-api-vs-unofficial-tools.