Need help? Message us on WhatsAppWhatsApp us+33 7 66 86 40 02Open chat
All posts
WhatsApp Automation· WhatsAble

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

How Click-to-WhatsApp ad replies get routed to the right team, assigned to an owner, and attributed back to the ad that started the chat.

Someone taps your Click-to-WhatsApp ad in Meta and messages you. That first reply carries the ad that started it — which creative, which campaign — but a shared inbox still has three separate jobs: get the conversation to the right team, put it in front of an owner, 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: Route 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 an owner using WhatsAble's inbox UI, the same automation platforms, keyword rules, or AI-by-content routing — 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), then let the inbox Ad card show whoever replies which ad and which first line started the chat — so ads can report by creative and sales does not have to ask the customer to repeat themselves.

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. Route — 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 routing 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

Once the inbound lands in the shared inbox, it needs an owner. WhatsAble supports four assignment paths on Pro and Agency: assign manually in the inbox UI, assign via Zapier/Make/n8n/API (useful for routing by which ad or campaign sent the reply), assign by keyword, or assign by AI-based content routing. Ads-driven traffic creates bursts — a creative that performs well can produce a wave of replies in an hour. Decide your routing rule (which team owns ad-sourced leads vs. general support) before the spike, not during it.

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 routed to in step 1. Once saved, the inbox Ad card gives the assigned rep the ad preview and the customer's first line from that same event, so they open the chat already knowing which creative the customer clicked and what they first asked. 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

Route

Ads team: Runs the Click-to-WhatsApp ad in Meta Ads; WhatsAble does not create the ad.

Sales / support: —

WhatsAble: Forwards the first-inbound ad context to n8n / Zapier / Make / your webhook.

Assign

Ads team: Optionally defines routing rules for ad-sourced traffic.

Sales / support: Owns the reply once assigned; can reassign or escalate.

WhatsAble: Assigns via inbox UI, Zapier/Make/n8n/API, keyword, or AI-by-content (Pro/Agency).

Attribute

Ads team: Pulls the attribution report from the ad IDs you persisted.

Sales / support: Sees the Ad card (ad preview + customer's first line) before replying.

WhatsAble: Renders the Ad card from existing referral fields; does not persist click IDs or ad IDs for you.

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. (For the exact Developer-menu steps and field names, see the "For automators" callout above.)
  3. Set your assignment rule for ad-sourced conversations — by keyword, by AI content, via your automation platform, or leave it to manual UI assignment 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 with the Ad card.
  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 and the Ad card? 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 route CTWA leads differently from ordinary support chats? Yes — keyword rules or AI-by-content routing can separate ad-sourced conversations from general support before assignment, or you can tag and route through your automation platform (n8n, Zapier, Make) using the ad type and ad ID on the first inbound.

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 and the inbox Ad card mapping, see Click-to-WhatsApp ads and the sibling deep-dive on tracking Click-to-WhatsApp ad attribution. If your bottleneck is who owns the chat once it's assigned, read Linked Devices vs a real team inbox or see how WhatsAble ranks against five other tools in Best WhatsApp Shared Inboxes for Teams (2026). Compare Bulk Message, Pro, and Agency on pricing — assignment and the Ad card are Pro/Agency features.

Ready to automate your WhatsApp?

Connect WhatsApp to Zapier, Make, n8n, Pipedrive, or Monday.com in minutes. Start free, no credit card required.

Start Free Trial