A social-to-WhatsApp funnel is a marketing pattern where a brand uses social video (most often TikTok or Instagram Reels) to drive viewers into an inbound WhatsApp conversation. The funnel has three stages: the video earns attention, a click-to-WhatsApp link or landing page captures intent, and the chat โ opened by the user โ turns into a recurring, opt-in channel for the brand. Done right, it combines the reach of social with the response rates of chat, while staying compliant with WhatsApp's 24-hour window rule.
This article describes the architecture, the metrics that matter, and the failure modes to avoid.
Why route social viewers to WhatsApp at all
Two reasons explain why this funnel has become popular in 2026, both rooted in behaviour the brand can measure:
Response rates on chat beat forms. A user willing to start a chat is further down the intent curve than one who clicks a website link. The chat thread typically converts higher per click than a landing-page form.
WhatsApp gives recurring contact, websites don't. Once the user has opted in, the brand can recontact them later through approved templates. A pageview, by contrast, gives no recurring channel. The same first click compounds.
The funnel is at its strongest when the brand has content people want to engage with (creator video, demo, tutorial) and a follow-up worth recontacting users about (restocks, exclusive drops, a community).
The three stages
1. Attention: creator video
The funnel starts with native video on a platform that distributes algorithmically. UGC works particularly well here because authentic content survives the first two seconds of watch time, which is when the algorithm decides whether to keep distributing. For brands running performance-based UGC programs, this stage is also where most of the budget goes; we cover the model in performance-based UGC.
2. Intent: the click-to-WhatsApp bridge
The video CTA points to a click-to-WhatsApp link, either directly or via a short landing page. Two architectures are common:
Direct click-to-WhatsApp. The bio link or end-screen sends users straight into a WhatsApp chat with a pre-filled message. Highest conversion of click to chat, lowest data capture.
Landing-page bridge. The link goes to a short landing page that contextualizes the offer and then opens WhatsApp. Lower click-to-chat rate, but lets you fire pixels, collect attribution, and segment the conversation by which video it came from.
For most brands, the landing-page bridge is worth the extra step: it lets the first WhatsApp message reference the exact content the user saw, which raises in-chat engagement.
3. Conversation: the inbound chat
When the user sends the first message, two things happen at once: WhatsApp's 24-hour window opens, and the user has implicitly initiated contact with your brand โ the compliant starting point for everything that follows.
The first message back matters more than any later one. It should:
- Acknowledge what the user just saw (the video, the offer, the page).
- Ask one specific question that advances the conversation.
- Avoid template-style copy that reads like an automated reply.
If you plan to recontact the user days later, this is also the moment to capture an explicit opt-in for marketing templates โ phrased clearly, not buried.
Metrics that actually matter
The funnel produces a long chain of events. Three metrics tell you whether it works:
Cost per chat. Total spend divided by chats started. The unit-economics number to optimize: lower it by improving the video and the CTA, not by buying more views.
Chat-to-conversion rate. Fraction of chats that produce the outcome you care about โ sale, booking, demo. Improves with the quality of the first response, not the volume of follow-ups.
Recontact opt-in rate. Fraction of chats where the user agrees to receive future marketing templates. This is the funnel's compounding asset; everything downstream depends on it.
Vanity metrics like total views or total chats are useful only inside the funnel. The right benchmark is your existing paid funnel; if cost per qualified outcome on the social-to-WhatsApp path is below your baseline, the funnel is working.
How to attribute a WhatsApp chat to the campaign that started it
Cost per chat only means something if you know which campaign produced each chat. How you get that depends entirely on how the user arrived, and the two cases behave very differently.
Chats that start from a click-to-WhatsApp ad. When a user taps a Meta click-to-WhatsApp ad, the first message your webhook receives carries a referral object. On the Cloud API it includes source_type (ad or post), source_id (the ID of the ad or post), source_url, the ad headline and body, and ctwa_clid, a click ID unique to that tap. Meta's guidance is to store the ctwa_clid with the conversation and, when a sale or booking happens inside the chat, send it back through the Conversions API, so the purchase is credited to the ad in Ads Manager. This is the only path where attribution comes built in. Two caveats from Meta's documentation: the referral can occasionally arrive with only source_url, and ctwa_clid is omitted for ads shown in WhatsApp Status. Field names change, so check the current webhook reference before you build on them.
Chats that start from anything else. A link in a TikTok bio, a QR code, a wa.me link under an organic Reel: none of these produce a referral object. A wa.me link also drops UTM parameters, because WhatsApp opens a chat, not a web page. If you want to know which video sent the user, you have to carry the signal yourself:
- Pre-filled message codes. Give each video its own link with a short code in the pre-filled text, for example "Hi, I saw video R12". Your inbox reads the code from the first message. Users can delete it, so treat the share you can match as a lower bound.
- A landing-page bridge. Send traffic to a thin page that records the UTMs and writes the campaign into the pre-filled text before opening WhatsApp. This is the architecture described above, and attribution is its main justification.
- One number per channel. Rarely worth the overhead, but it separates channels cleanly when codes keep getting deleted.
Pick a window and keep it. Decide how long after the first message a sale still counts for the campaign, write it down, and use the same rule for every source. Ads Manager will apply its own attribution window to ad-originated chats; if your organic reporting uses a different one, the two numbers will not be comparable.
The honest limit: organic social-to-WhatsApp attribution is always partial. Plan for a measurable share of chats arriving with no source at all, and report them as "unattributed" rather than spreading them across campaigns.
Compliance: the 24-hour window, again
Everything in this funnel hinges on respecting WhatsApp's 24-hour window rule. The compliant pattern:
- The user initiates the chat by tapping click-to-WhatsApp. Window opens.
- The brand replies and engages freely within 24 hours.
- The brand captures explicit opt-in to send future marketing templates.
- Outside the window, the brand recontacts only via approved templates, only to opted-in users.
The mistake to avoid is planning the funnel as if free-form messaging is available forever. Design every re-engagement message as if it has to be a Meta-approved template from day one โ because, structurally, it does.
Failure modes
Three patterns explain most underperforming versions of this funnel:
The video is good, the first reply is robotic. The chat opens, the user gets a generic auto-reply, and the conversation dies. Customize the first response by source video.
No data passed to the chat. The brand doesn't know which video brought the user. The first message can't reference it. Solve this with the referral data on ad-originated chats and, for organic links, a source code in the pre-filled message or a thin landing page that records the UTMs.
No plan for re-engagement. The brand captures opt-in but never uses it. The compounding value of the channel is recontact; without it, the funnel is just a more expensive web form.