Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Meta Ads › Campaign Structure

Click-to-Message Ads

How click-to-message ads work on Meta: choosing Messenger, Instagram or WhatsApp, the goal, a reply flow that qualifies, response times and counting customers.
Guideintermediate11 min readUpdated

What a click-to-message ad does

On Meta, a messaging app is a conversion location rather than a separate ad type. The campaign objectives guide lists messaging apps as a conversion location under the Traffic, Engagement, Leads and Sales objectives, with conversations as an optimisation goal, and for sales conversations on WhatsApp or Messenger it recommends optimising for conversations started, then using conversion events reported from the conversation where they are available. The Meta Ads hub gives messages and bookings one row of its start-by-objective table: one ad set, click-to-message ads and a reply flow that qualifies, measured by conversations started and conversations that became customers. One ad set is the campaign structure hub's consolidation principle applied: a messaging campaign learns from conversations, and splitting them across ad sets slows that learning for no reporting gain.

The format suits businesses that sell in conversation: services with a question or two before a booking, products people want to ask about, appointments that depend on availability. The person never has to fill in a form or find a page on a phone, and the business learns what they want in their own words. The cost is that a conversation is a commitment for the business. Every one needs an answer, and an unanswered message from someone who just tapped an ad is a worse outcome than a bounced click, because they told you they were interested.

The objectives guide's warning sits at the centre of everything below: conversations are only leads once the reply flow qualifies them. Delivery finds people who will start a conversation, as it finds people who click when asked to. The rest of the funnel is the business's to build and to count.

Choosing the app: Messenger, Instagram or WhatsApp

The choice is mostly about the business, not the platform. Each app is a separate inbox with its own habits, and the right one is where customers already talk to you and where your team can answer well.

QuestionPoints towardsWhy
Where do customers already message the business?That appPeople reply faster in the app they already use with you
Which inbox does the team actually watch?That appAn unwatched inbox turns ad spend into unanswered messages
Will the sale need follow-up days later?WhatsApp, with its rules understoodFollow-up outside the customer service window needs approved templates and an opt-in
Is the brand discovered mainly on Instagram?InstagramThe conversation stays in the app where the interest started
Does the flow rely on structured replies such as buttons?Check each app; WhatsApp's are documentedThe automation guide notes that Meta's WhatsApp documentation describes interactive messages with buttons and lists

Two cautions apply whatever the answer. Start with one app and add a second only when the first is staffed and counted properly; three inboxes answered slowly lose more customers than one answered fast. And check what Ads Manager offers for your objective before planning around one app: the objectives guide notes that some options depend on the Page or on features enabled for the business, and Ads Manager is the authority on what a given account can select. The business portfolio tutorial makes sure the Page and the Instagram account the conversations arrive at belong to the business in the first place.

Objective and goal: conversations, then what counts

Pick the objective from what the business is paid for, as with any campaign. Where the conversation is the start of a sale, the objectives guide points to Sales or Leads with a messaging location. Where the goal is attention and an audience to follow up, the Meta Ads setup for consideration uses the Engagement objective with messaging conversations as the goal for businesses that sell through conversation, and treats the people who messaged as an audience for later steps.

Under each of these, conversations started is the optimisation goal most accounts will use, because it is frequent enough for delivery to learn from. That is its strength and its weakness. A goal that is easy to produce will be produced by people who find messaging easy, including the merely curious, so the ad creative has to do some of the qualifying: name who the offer is for, the price band, the commitment involved. The objectives guide's sequence is to start on conversations started and then use conversion events reported from the conversation where they are available, which brings the goal closer to the outcome the business is paid for.

Instant forms are the other way to collect enquiries inside the app, and the Meta Ads setup for lead generation covers them, along with when a form or a landing page fits. Choose a messaging destination when the enquiry genuinely needs a conversation; choose a form when what you need is contact details and a few answers. The comparison of click-to-message ads and instant forms weighs the two routes on staffing, follow-up and how each lead is counted in the CRM.

Designing the reply flow

The reply flow is the qualifying step that turns a conversation into a lead. The guide to SMS and WhatsApp automation sets out the design rule for any conversational flow: a short tree with a human exit at every branch. The expected replies map to actions, anything unrecognised routes to a person with the history attached, and the automated steps pause until that person has replied. The worst outcome it names is a bot repeating its menu at someone who has asked a real question; the second worst is a question nobody answers.

For an ad-driven conversation the tree usually needs three things and no more. What the person wants, offered as a short list of choices. When they want it, because availability is what most service conversations are about. And one question that separates a likely customer from a browser, such as a budget band, a location or a level of experience. On WhatsApp the automation guide notes that Meta's documentation describes interactive messages with buttons and lists, which make each choice unambiguous. Whatever the app, keep a free-text route open at every step: the person who types a question instead of tapping a button is often the most serious one.

Write the first reply as carefully as the ad. It should thank them, say who they are talking to and what happens next, and ask the first question. If the setup can send a reply outside staffed hours, that reply should say when a person will respond, which is the automation guide's advice for any two-way flow. And record the outcome of every branch: qualified, not a fit, no reply. Those outcomes are the funnel the campaign will be judged on.

Staffing, hours and response time

A conversation started from an ad is an enquiry with a clock running. Lead response time matters more here than on a form, because the person is still holding the phone and an answer that arrives hours later meets someone who has moved on. The automation guide names staffing as the usual failure of two-way flows: launched without agreed cover for the human branches, they generate unanswered conversations within days. Agree who watches the inbox, in which hours and with what response expectation before the ads go live, and treat the conversation inbox with the same discipline the community management guide applies to comments and messages.

If the team cannot cover the hours the ads run, change the hours the ads run. The campaign versus ad set budgets comparison notes that ad scheduling, running ads only on chosen days and hours, requires a lifetime budget. Limiting delivery to staffed hours trades some reach for answered conversations, and for most service businesses that is the right trade. Whether faster replies actually raise bookings for a given business is testable: the lead response time test sets out how to compare response speeds and read the result on booked customers rather than on replies.

Lead routing completes the picture. When several people share the inbox, decide which enquiries go to whom, so that a booking question reaches someone who can book and a complaint reaches someone who can resolve it, and so that nothing waits because everyone assumed someone else had it. The call and message campaign launch checklist confirms the rota, the hours, the routing and the reply flow before the first ad goes live.

Following up after the first conversation

Not every conversation ends in a booking on the day. Follow-up is where the apps differ, and where the cited documentation is specific only for WhatsApp. The automation guide sets out what Meta's WhatsApp Business Platform documentation describes: when a person writes to the business, a customer service window opens in which the business can reply with free-form messages; outside that window, anything the business initiates must use a message template that Meta has reviewed and approved, declared in a category; an opt-in for business-initiated messages must make clear that the person is agreeing to messages from the named business on WhatsApp; and blocks and reports feed a quality rating that affects the account. A reply to a question is not a marketing opt-in, so a person who asked about prices has not agreed to promotions.

In practice that means asking, inside the conversation, whether the person would like a follow-up and recording the answer, and having approved templates ready for the follow-ups the business sends most often. For Messenger and Instagram follow-up, check Meta's current documentation for those apps; the pages this site cites do not describe their rules, so this guide does not.

Advertising is the other follow-up route. The custom audiences guide describes engagement audiences that include people who messaged a Facebook Page or an Instagram account, which lets a campaign reach people who started a conversation but did not book, with a stronger reason to return. The consideration setup builds exactly that sequence. A Custom Audience of messagers is also the right exclusion for a prospecting campaign whose job is to find new people.

Counting conversations that became customers

Meta reports conversations started. Everything after that lives in the inbox and the CRM, and the guide to measuring calls and chats sets out the principle: a messaging conversation is an enquiry once a request is recorded, and the CRM is the place where it becomes a customer, with the source recorded in the same fields as web forms so reports group them together.

StageDefinitionWhere it is countedWho records it
Conversation startedA person sent a message from the adAds ManagerMeta, automatically
RepliedThe business answered and the person repliedThe messaging inboxThe inbox, or the person handling it
QualifiedThe reply flow established what they want, when, and how to reach themThe CRM, as a lead with method and sourceThe person handling the conversation
BookedA booking or order was madeThe CRM or booking systemStaff, at the time of booking
PaidThe customer paid or attendedThe CRM, the till or the booking systemStaff or the system

Set the source when the lead is created, not later from memory. The calls and chats guide's approach for messaging links carries over: where a prefilled first message is possible, include a short reference for the campaign so the person handling the conversation can record the source, and write the conversation's identifier into the CRM record beside it. Then calculate cost per qualified lead, per booking and per paying customer from the CRM counts and the ad spend; the CPA calculator does the division. Cost per conversation started is a diagnostic for the creative. Cost per paying customer is the number that decides whether the campaign continues.

A dive school books courses by message (illustrative)

Illustrative example — not a real result

Kelpfinch Diving qualifies its WhatsApp conversations

Kelpfinch Diving, an invented dive school, sells a £390 beginner course through WhatsApp conversations started from ads on a Leads campaign. For four weeks the ads run around the clock on a daily budget, and the first reply is an open "Hi, how can we help?". The owner then switches to a lifetime budget scheduled to the hours the two instructors staff the inbox, and a reply flow that asks three questions as buttons: which course, which month, and how confident the person is in the water, with a free-text route at every step. Spend is the same in both periods.

Four weeksSpendConversations startedQualifiedBookedPaidCost per conversationCost per paying customer
Before: all hours, open reply£1,260420963122£3.00£57.27
After: staffed hours, qualifying flow£1,2603001415846£4.20£27.39

Conversations fell and each one cost more, which the Ads Manager view alone would have reported as a worse campaign. The typical first response time fell from almost four hours to under ten minutes, people who were not ready for a course said so at the second button rather than after a long exchange, and the cost per paying customer roughly halved. The owner now asks every qualified person whether they want a reminder before the next course date and records the answer, so follow-ups go out as approved templates only to people who said yes.

Common mistakes

  • Judging the campaign on cost per conversation. Conversations are the cheapest stage; judge on cost per qualified lead and per paying customer.
  • No reply flow. An open greeting leaves the qualifying to a long exchange that most people abandon.
  • A bot with no human exit. Every branch needs a route to a person, with the history attached.
  • Ads running when nobody is there. Schedule the ads to staffed hours, which needs a lifetime budget, or staff the hours the ads run.
  • Three apps, three slow inboxes. Start with the one customers use and the team can answer.
  • Treating a question as an opt-in. On WhatsApp, business-initiated follow-up outside the customer service window needs an approved template and a clear opt-in.
  • Recording the source later from memory. Set it when the lead is created, or the CRM cannot connect customers to the campaign.

Frequently asked questions

Are conversations from a click-to-message ad the same as leads?

No. A conversation is someone who tapped the ad and sent a message, which is a cheap and frequent action. It becomes a lead when the reply flow has established what the person wants and how to reach them, and a customer when they book or pay. Meta reports conversations started; the qualified, booked and paid stages have to be recorded by the business in its inbox or CRM, and the campaign should be judged on the cost of those later stages.

Should I use Messenger, Instagram or WhatsApp?

Use the app your customers already message you on and your team can staff well. If people already ask questions through Instagram, an Instagram destination meets them where they are. If the sale needs follow-up days later, WhatsApp's documented rules matter: free-form replies are allowed in the customer service window a person's message opens, and anything the business starts outside it needs an approved template and an opt-in. Starting with one app and doing it well beats offering all three and answering slowly.

Can I run click-to-message ads only when someone is there to reply?

Yes, through ad scheduling, which the site's budget guide notes requires a lifetime budget rather than a daily one. Scheduling the ads to staffed hours trades some reach for faster replies. If the account needs a daily budget, the alternative is to staff the inbox for the hours the ads run, or to make sure the first reply says honestly when a person will respond.

Terms used on this page

Tools to try

Where this page is used

Also related

Sources

  1. Meta Business Help Centre — Meta Business Help Centre
  2. WhatsApp Business Platform documentation — Meta for Developers

Related