Click-to-WhatsApp Ads → Shared Inbox: Assign and Attribute (2026)

Someone taps your Click-to-WhatsApp ad in Meta and messages you. That first reply carries the ad that started it — which creative — but a shared inbox still has jobs: get the conversation to the right team and keep the ad connected to whatever happens next. Most guides cover only the tracking half or only the inbox half. This is the hub that connects both.

Short answer: Get the first WhatsApp reply from the ad to the right team (tag it or forward it to n8n, Zapier, Make, or your webhook before that context is gone). Assign a chat by giving it a teammate's label: by hand in the inbox, automatically by keyword or from your AI agent, or from Zapier, Make or n8n with the Update a Contact action or the labels field on Send WhatsApp Message. Pro and Agency only. Attribute by saving which ad started the chat the moment it arrives (you write that to a Sheet or CRM yourself).

The real question

Ads teams need to prove which creative produced a real conversation, not just a click. Sales and support teams need that same lead to land with the right person immediately, with enough context to skip "so, what were you asking about?" Most CTWA content picks one side: attribution guides map the payload and stop, inbox guides describe assignment and never mention where ad context goes. A lead that's perfectly tracked but replied to by the wrong team still loses the sale. A lead assigned instantly with zero ad context makes the rep re-ask what the ad already answered. Both halves have to work together.

The three-step path

1. Forward — get the first reply where it can be acted on

The first inbound after a Click-to-WhatsApp tap is forwarded to whichever destination you've wired: a webhook you built, n8n, Zapier, or Make. This is the same ad context whether it's a WhatsApp ad or a WhatsApp Status ad (Status ads sometimes omit the click ID). Nothing about forwarding changes that mapping — you're deciding where that inbound goes next, before assignment happens. The full field-by-field reference lives on the Click-to-WhatsApp ads page.

2. Assign — put the conversation in front of the right person

Assign chats to teammates with labels. A teammate limited to certain labels sees only the chats that carry them. Ads-driven traffic creates bursts — a creative that performs well can produce a wave of replies in an hour.

3. Attribute — keep the ad connected to the outcome

The click ID and ad ID are usually only present on that first inbound; later messages in the same chat typically drop them. Whatsable does not persist these fields for you — you write them to a Sheet or CRM the moment they arrive, on whichever platform you forwarded to in step 1. Later, group the saved ad IDs by week to report which creative is actually producing replies — that join only exists if step 3 happened.

Who does what

Setup, start to finish

1. Run the Click-to-WhatsApp ad in Meta Ads. Whatsable does not create or manage the ad itself.
2. Wire the first inbound to n8n, Zapier, Make, or your own webhook.
3. Set your assignment rule for ad-sourced conversations — by keyword, from your AI agent, via Zapier, Make or n8n, or by hand in the inbox if volume is low. This is a Pro/Agency feature; Bulk Message has no shared inbox or assignment.
4. When someone taps the ad and messages you, the first inbound reaches your destination, and the conversation appears in the shared inbox.
5. Save which ad started the chat immediately — write the click ID and ad ID to a Sheet or CRM from your automation platform. Do not wait for a follow-up reply; later messages in the same chat usually omit them.
6. Report weekly by grouping the saved ad IDs, joining what Ads Manager saw as a click to what your CRM logged as a reply, qualified lead, or close.

FAQ

Does Whatsable create or manage the Click-to-WhatsApp ad itself? No. The ad runs in Meta Ads. Whatsable forwards the first-inbound ad context — it does not build, launch, or manage the campaign.

Which plan do I need for assignment? Pro or Agency. Bulk Message is broadcast/template-only — it has no shared inbox, no seats, and no assignment of any kind.

Who is responsible for saving the click ID and ad ID? You are. Whatsable forwards the first inbound with these fields present; it does not persist them on your behalf. Write them to a Sheet or CRM the moment they arrive.

Can I separate CTWA leads from ordinary support chats? Yes. Labels can go on automatically by keyword or from your AI agent, so chats reach the right teammate.

Does the ad context survive if the customer doesn't reply right away? Usually not for long. The referral is typically present on the first inbound only; later messages in the same chat usually omit the click ID and ad ID. Persist them immediately rather than waiting for a follow-up.

What about WhatsApp Status ads — do they work the same way? Status ads can also carry ad context, though the click ID may be omitted on those. Treat a Status referral as still worth persisting the ad ID from — it is not unrelated to this flow.

Soft next step

For the complete field-by-field referral reference, see Click-to-WhatsApp ads and the sibling deep-dive on tracking Click-to-WhatsApp ad attribution. Compare Bulk Message, Pro, and Agency on pricing.