A retail client came to us with a problem that wasn't obvious until we looked closely: their ads were working, but their branches had no idea who was getting the leads. This is how we fixed it by combining 12Commerce and 12Bot.
The Problem: Ads Were Working, Attribution Wasn't
The client runs an e-commerce store with multiple physical branches, each with its own branch manager. Their marketing was solid — running paid ads on Google, Facebook, and Instagram, generating a steady stream of leads.
The breakdown happened after the click. Before the fix, different branches were running ads with different WhatsApp numbers attached — each branch's ad pointed to its own number. There was no central point tracking any of it: no system told anyone which branch was getting how many leads, whether a customer's message was ever picked up, or whether that lead turned into an order. Branch managers had no visibility beyond their own number. Management had no way to see which branch was converting and which wasn't.
This is a common failure point for multi-branch or multi-location businesses using WhatsApp as a sales channel: WhatsApp handles conversations well, but it has no native concept of "branches" or "routing." One number, one inbox, no structure — it works for a single-location business and breaks immediately once you add more than one branch.
Show Image
Why a Generic WhatsApp Setup Couldn't Solve This
A standard WhatsApp Business setup — even with basic automation — assumes one team is answering from one inbox. It doesn't ask a customer which branch they want, doesn't know which manager to notify, and gives ownership no way to measure branch-level performance. Bolting a generic chatbot onto this doesn't fix the structural issue: the problem wasn't response speed, it was that leads had no destination.
The Solution: 12Commerce + 12Bot Working Together
We built a two-part system:
On 12Commerce, we added multi-branch ordering: a customer selects their branch before placing an order, instead of ordering into a single undifferentiated queue.
On 12Bot, we consolidated everything into one central WhatsApp number that replaced the separate per-branch numbers — every ad, every branch, points to this single number now. Instead of leaving the message sitting in a generic inbox, the system routes it based on the branch the customer selected. When a customer picks Branch A, the Branch A manager gets notified directly with the customer's number and intent to order, so they can follow up immediately.
The customer experience stays simple — one number to message, no confusion. The structure only exists on the back end.
Show Image
The Admin Layer: Visibility That Didn't Exist Before
The part that actually solved the client's real problem was the admin dashboard. As admin, they can now see:
- How many messages/leads came in per branch
- How many customers were contacted by each branch manager
- How many orders each branch delivered
- The conversion rate per branch — leads in vs. orders closed
This turned WhatsApp from a black box into a channel they could actually manage. Before this, "how many leads did Branch A get this week" was a question nobody could answer. Now it's a dashboard view.
The Result
The system now runs across 13 branches, with each branch receiving roughly 2,000–2,500 messages routed to it directly — approximately 26,000–32,500 messages a month flowing through a structure that previously had none. Every one of those messages now lands with a named branch manager instead of sitting in a single undifferentiated inbox.
What this unlocked wasn't just routing — it was measurement. The admin can now see exactly how many messages each branch received, which didn't exist before. Conversion tracking (how many of those messages became completed orders) isn't automated yet; it's built through manual follow-up and reporting on top of the message data. That's the honest next step for this system: closing the loop from "message received" to "order confirmed" without relying on manual reporting.
Why This Matters Beyond This One Client
Any business running paid ads with more than one location or team handling WhatsApp has this exact problem, whether they've noticed it yet or not. Ad spend without lead routing is money generating conversations that go nowhere. This is a pattern we now build for directly, rather than treating each multi-branch client as a one-off.
