Click-to-WhatsApp ads: automating the conversation after the click

Updated 2026-10-23 · 4 min read · By the Convo360 team

What happens the moment someone clicks

A Click-to-WhatsApp (CTWA) ad opens WhatsApp with a pre-filled message already typed in, ready for the user to hit send. The moment that message arrives, you have a warm, high-intent contact, but only for a short window. What your flow does in the first exchange decides whether that click becomes a qualified lead or an abandoned chat.

CTWA differs from a normal WhatsApp enquiry in one important way: the person has not yet decided to talk to you, they have decided to click a button on an ad. Some of that click is genuine interest and some is idle curiosity, so the first automated reply carries more weight in a CTWA flow than in an organic enquiry, where the customer has already done more of their own research before reaching out.

Matching flows to pre-filled messages

1. In Meta Ads, set a distinct pre-filled message for each ad or ad set, for example 'Hi, I saw your Diwali sale ad' versus 'Hi, I want to know about your EMI plans'.
2. In Convo360's Flow Builder, create a keyword trigger matching each pre-filled phrase.
3. Each trigger opens a flow written specifically for that ad's promise, not a single generic welcome message everyone gets regardless of which ad they clicked.

The same pattern extends naturally to ads that open an Instagram DM instead of WhatsApp. Instagram DM automation can use the same idea, a specific opening context or a story-reply keyword tied to a particular ad, so a founder or marketing head running ads across both channels does not need two entirely different measurement approaches, just the same source-tagging discipline applied consistently.

Capturing campaign context as a variable

As soon as the flow opens, use Set Variable to tag the contact with the ad or campaign name. This single step is what lets you later see, in your CRM pipeline and analytics, which ad actually produces qualified leads versus which one just produces cheap clicks that go nowhere.

Since a CTWA click usually comes from a specific ad promising a specific product or offer, the flow's first substantive reply should match that promise exactly, correct price, correct availability, rather than a generic response that makes the customer feel bait-and-switched. Keeping the flow's content synced with your actual live pricing and stock, rather than a static message written once and forgotten, protects both conversion rate and trust.

Review this alignment specifically whenever you pause, change or launch a new ad creative. An outdated flow still referencing last month's offer, while the live ad shows a new one, is a common and entirely avoidable source of confused, low-converting chats.

Qualifying fast, before interest cools

CTWA leads are impulsive by nature, they clicked because something caught their eye right then. Keep the qualifying flow to one or two targeted questions matched to that specific ad's offer, then move straight into next steps: a Razorpay payment link for a direct-purchase ad, an appointments slot for a consultation ad, or an immediate AI Reply for a question-heavy enquiry ad. A long generic qualification form kills the momentum a CTWA click creates.

Once the basic pattern is working, a useful next step is testing two different qualifying questions or offers for the same ad using a Split (A/B) block, rather than assuming the first version of your flow is the best one. Even small changes, asking budget before or after showing the product, offering a call versus a payment link first, can shift qualification rates meaningfully, and CTWA's clear source tagging makes this easy to measure cleanly.

Handling replies that don't match the pre-filled message exactly

Some users edit the pre-filled message before sending, or Meta's matching is not always exact. Set a fallback: if no specific keyword matches, route to a general welcome flow that asks 'which ad brought you here' as a quick menu, so you still capture attribution even when the exact trigger phrase does not match.

Convo360 tags contacts by source inside its own CRM pipeline and analytics, which tells you qualification and conversion rate per ad. To connect this back to your ad spend for a full cost-per-qualified-lead view, export or sync the tagged lead counts to a simple sheet alongside your ad platform's spend numbers, using a Google Sheets block if you want this to update automatically rather than being pulled manually each week.

What to review weekly

Look at Flow Logs and CRM stage movement by source tag weekly: cost per chat opened tells you if the ad itself is working, but cost per qualified lead tells you if the ad and the flow together are working. An ad producing lots of chats that never qualify usually means the ad's promise and the flow's offer are mismatched.

Step by step

1. Set a distinct pre-filled message per adConfigure each Click-to-WhatsApp ad with its own opening message text.
2. Build a matching keyword triggerCreate a Flow Builder trigger for each pre-filled phrase to open the right flow.
3. Tag the source variableUse Set Variable to record which ad or campaign the contact came from.
4. Qualify with one or two questionsKeep the qualifying flow short and specific to that ad's offer.
5. Move straight to the next stepRoute to a payment link, appointment booking or CRM lead save based on intent.
6. Add a fallback for unmatched messagesAsk which ad brought the contact in if the exact trigger phrase doesn't match.
7. Review qualified-lead cost weeklyCompare cost per chat versus cost per qualified lead across ads.

Example conversation

Frequently asked questions

Related reading

Available across India — see WhatsApp & AI calling automation by state and city.