WhatsApp across branches: how head office sees what the network tells clients

Plenty of numbers. Nobody in charge of them. And every branch has its own idea of what “quick” means.

A client messaged one salon in the chain: “Any slots on Saturday?” No reply until evening. On Monday she wrote to another branch of the same chain, and was told there had been a Saturday slot, but “we have our own number, we can’t see your chat with them.” To the client, it is one company. To the company, it is two phones in two different drawers.

Head office will never hear this story. It will only see that the branch made less this month and ask the manager why. The manager will say “footfall was slow.”

This is what a network looks like when every branch runs its own WhatsApp. Below: what gets lost, and which decisions the person running the network should make.

How it usually happens

A network grows faster than its rules. First there was one location and one number. Then a second opened and got a phone. Then a third, a fourth, a franchise across town. Each time the call was quick: “let the front desk have its own WhatsApp, clients prefer it.”

A year later, the picture looks like this:

• Every location has its own number. Some on an old phone at reception, some on the admin’s personal number.
• Head office sees nothing. How many clients wrote, who got a reply, what was promised — only the person holding the phone knows.
• Reporting is by word of mouth. “It’s all fine, we answer everyone.” Impossible to check.
• Each branch has its own voice. One is polite and thorough, another sticks to “yes,” “no,” “come in.”
• Clients write to the wrong place. The nearest branch, the one they visited last time, or three at once, just in case.

Convenient for everyone except the client and the owner.

What gets lost

Speed

In a branch, the WhatsApp phone sits next to the till. The admin greets guests, takes payments, answers calls. The message waits until their hands are free. Reply speed at that location depends on how busy the shift is, not on any rule. Head office finds out when clients start leaving.

Promises

“We’ll call you when the stylist is free.” “We’ll hold the car until Friday.” “We’ll send the tour quote tomorrow.” These promises are made in a branch chat and live in one person’s memory. The admin changes, goes on leave or simply forgets — and the promise is gone. The client will not remember the employee’s lapse. They will remember the brand.

The client base

The most expensive loss. If the branch number is the admin’s personal number, the whole branch history leaves with them. Regulars, booking history, agreements. The new admin starts with an empty phone. Sometimes the old one starts at the salon next door, together with the clients.

One voice

A network spends years building its brand: signage, interiors, service standards. Then in chat, every branch sounds like whoever happens to run it. A client who got a detailed answer from one location yesterday gets a curt “no” from another today. Same company, technically. The client does not see it that way.

The client at the “wrong” branch

Clients do not know how you split territories. They write to whichever number they saved. Without a handover rule, the answer is “that’s not us,” and the request quietly disappears. Your internal logistics became the client’s problem. They will solve it themselves — with a competitor.

Signs in your network

You have the problem if at least two of these sound familiar:

• Head office cannot list every working WhatsApp number across its locations.
• Some numbers are registered to employees rather than the company.
• You learn about unanswered messages from reviews, not from reports.
• A branch slipped after its admin left, and nobody can explain why.
• Clients complain that different branches tell them different things.
• Branches argue over whose client it is instead of replying.
• “Checking chats” means a manager drove over and asked for the phone.

Questions to ask yourself

1. How many work numbers does the network have, and who are they registered to? Not on paper, in reality — including the “temporary” number someone set up three years ago.
2. How many enquiries reached the branches last week, and how many went unanswered? If you cannot say, you do not have a picture.
3. What stays with the company if the admin of your strongest location leaves tomorrow?
4. Who replies to a client who wrote to the wrong branch? Is that decided, or decided again every time?
5. What should head office see, and what is the branch’s business? If you do not draw that line, it gets drawn for you: either nobody sees anything, or everybody suspects surveillance.

Decisions for the person running the network

Numbers belong to the company

Every work number is registered to the company. The SIM and the access stay with the company, not in the admin’s bag. Personal numbers are taken out of client work. Plan the move to work numbers before the next resignation, not after it.

One reply standard for the whole network

Decide once, for every location:

• First-reply time. Not “when we can,” but a clear norm for working hours and a separate one for after hours.
• What we say at night and at weekends. The client should know when to expect an answer, not guess.
• Tone and ready answers. For common questions — price, booking, availability, address — the network uses the same wording.
• Every promise has a date. If a branch promised something, it has a deadline and an owner.

Put all of this in a client chat policy, not in the head of one area manager.

Who picks it up

Decide in advance:

• who replies when a client wrote to the wrong branch, and how they are handed over to the right one — with their history, not with “just call them yourself”;
• who picks up messages if a location misses the reply time;
• what happens to a branch’s chats when its admin changes or the location closes.

What head office sees, and what stays with the branch

Head office does not need to read every “good morning.” It needs to see what affects revenue and reputation: how many enquiries came in, how many went unanswered, how fast people replied, and which conversations need attention — a complaint, a conflict, a broken promise. The rest is the branch’s job.

A sound split sounds like this: the branch owns the conversation; head office owns the rules and makes sure no client is left without an answer.

Privacy and the limits of control

Chat oversight in a network easily turns into paranoia. On both sides. Head office suspects branches of hiding things. Branches suspect head office of looking for someone to blame. Everybody spends energy on suspicion while clients wait.

Oversight without spying rests on a few rules:

• Only work conversations are monitored, on work numbers. Staff personal chats do not live on the work phone and are not checked.
• The rules are announced up front. Staff know what head office sees and why.
• Franchisees are a separate conversation. With partners, the limits go into the contract: which client and chat data flows to head office, and which stays with the partner.
• Personal data laws vary from place to place. What can be stored and who can see it is checked before launch, not after a complaint.

Oversight everyone knows about builds discipline. Oversight people stumble on drives out your best staff.

Where to start

Not with choosing a tool. Start with a table: every location, every work number, who it is registered to, who holds the phone. Then one reply standard and one rule for handing a client between branches. Then decide what head office sees every day and what only when a dispute needs sorting out.

A tool can help keep those rules in place later. It cannot invent them for you. The rest is for the introduction.

Checklist: the network and its chats

• Head office knows every work number at every location
• All numbers are registered to the company, access stays with the company
• One first-reply time applies across the network
• Common questions have shared wording
• It is decided who replies to a client who wrote to the wrong branch
• It is decided who picks up messages when a location misses the reply time
• When an admin changes, the branch’s chats stay with the company
• Head office sees unanswered enquiries without calling the branch
• Staff and partners know what head office sees and why

If you answered “no” three times or more, your network is not one company. It is several, sharing a sign.

---

Many branches. One client. And it is not the client’s job to know where your territory ends.