The chaos of many numbers
The same scene repeats in most of our meetings with multi-branch companies, whether clinics, restaurants, salons, or service companies: every branch has its own WhatsApp number, often on a personal phone held by the receptionist or the branch manager, and every number is an isolated island.
The symptoms are familiar to anyone running more than one branch:
- Nobody at head office sees anything: how many messages arrived today? How many were answered? How fast, and how well? The honest answer in most companies: we do not know
- Customers fall between branches: a customer messages the Riyadh branch about a service available in Jeddah and gets "we do not have that here" instead of a proper handover, and a customer the company could have served walks away
- Quality depends on each branch's mood: one branch replies in minutes, another at the end of the day; one answers professionally, another in a single word. One brand, ten different experiences
- The number belongs to the employee, not the company: when the receptionist resigns, the branch's conversations and relationships leave with them, and sometimes the number itself
The biggest loss is not operational but commercial: the message answered late, or never, is usually a customer who was ready to pay. In a ten-branch company that leak is multiplied by ten, and it appears in no report because nobody is measuring it in the first place.
The unified model: one entry point, smart routing
The alternative we present in those meetings is simple in concept: one entry point for all conversations, with intelligent routing behind it.
In practice, the model rests on three pillars:
- A single entry point: one main WhatsApp number, verified under the brand's name, alongside the other channels, web chat and the rest, all flowing into one platform. The customer never needs to know which number to message, and the company stops managing ten islands
- Routing by branch and intent: each conversation is classified automatically from its content and the customer's data: which branch it belongs to and what kind of request it is, a booking, an inquiry, a complaint, then routed to the right team, or handled directly by the AI agent when it falls within its authority
- One customer record across branches: a customer who visited two branches has one record with their full history, not two contradictory ones. That is what makes the experience continuous: whichever branch replies knows their story. We covered how this record generates itself from the conversations in our conversational CRM article
The point we always stress: unification does not mean suffocating centralization. Every branch still serves its customers and sees its conversations. What changes is that the company finally sees the whole picture, and the customer finally meets one brand.
What changes for management
For whoever sits in the general management or operations seat, the unified model changes three fundamental things:
- Visibility: one dashboard showing every branch: conversation volume, response speed, resolution rates, customer satisfaction, per branch and company-wide. Comparing branches turns from impressions into numbers
- Consistency: the same tone, policies, and offers in every branch, because the knowledge the agent and the teams answer from is one, updated centrally. The expired offer no longer keeps selling in the branch that missed the memo
- One report instead of ten: instead of asking every branch manager for a monthly report assembled by hand in their own style, the numbers aggregate from the same source with unified definitions, so you compare branch to branch with confidence
There is a fourth effect we hear from customers months after rollout: the numbers reveal where the problem actually is. A branch that seemed "always busy" turns out to have normal volume but slow replies, while a quiet one turns out to carry twice the volume of others at higher quality. Hiring and expansion decisions change when they rest on those numbers.
For field teams and branches
The model does not serve management at the branches' expense. It tidies the branch's own day:
- Handoffs between agent and team: the agent handles the repetitive questions and bookings around the clock and hands the team what genuinely needs a human, with the full conversation context attached. The receptionist picks up a prepared conversation instead of starting from "hello, how can I help you?"
- A calendar per branch: bookings route to the correct branch's calendar with its real hours and capacity, so no customer books a slot at a closed branch or with a staff member unavailable that day. We covered in-conversation booking in our booking management article
- Cross-branch transfers with context: a customer who needs a service at another branch moves with their conversation and record, never retelling their story from zero
Questions to ask before implementing
From dozens of projects, these are the questions we advise any multi-branch company to put to any platform it evaluates, ourselves first:
- How are routing rules built? Can you route by branch, service, and request type together, and who can adjust the rules later without a new technical project?
- How are permissions managed? Does a branch employee see only their branch's conversations, a regional supervisor their region, and management everything? Flexible permissions are a requirement, not a luxury
- How is branch data separated when needed? Some companies need accounting or operational separation between branches while keeping the unified management view
- What is the migration plan from the current numbers? How do customers messaging the old branch numbers transition, at what pace, and without losing a single open conversation
A platform that answers these questions clearly before signing saves you months of surprises after.
How tkana implements it
At tkana we built this model end to end in one platform: all your channels flow into one place, AI agents answer under your brand around the clock, and they know your branches: each branch's services, hours, and calendar, so they answer, book, and route every conversation to the right branch team when it needs a human. Management sees one dashboard with every branch's numbers, each branch sees its customers, and the customer meets one consistent brand wherever they message. And starting does not require ripping out your systems: we begin with one or two branches and expand once the numbers prove themselves.
The bottom line
Scattered numbers and isolated islands are not the fate of multi-branch companies. They are a stage you can leave behind with a clear model: one entry point, smart routing by branch and intent, one customer record, tidy permissions, and a dashboard showing your branches in real numbers. The result is a management team that sees, compares, and decides; branches that receive organized conversations with context; and customers who meet one professional brand wherever they message. The first practical step: count how many messages reached your branches last month and how many died without a reply. That number alone usually settles the discussion.