One WhatsApp number for several branches: how to organize it
How to handle one WhatsApp number across head office and branches: one user per person, a menu that distributes chats and transfers that keep context.
In a nutshell
When the business WhatsApp lives on a phone at one branch, the queue at the counter and the messages compete for the same person. With the number connected to a platform, each location signs in with its own users, new conversations go to whoever has the fewest open chats, and what one branch can't answer is passed to another, without the customer changing numbers.
Why a branch's WhatsApp gets overloaded
When the business number is on a phone, it gets answered by whoever has that phone nearby. At a branch that is usually the same person serving the counter: when there is a queue, the messages wait.
Meanwhile, head office or the back office may have people with time to reply. The problem is not headcount: the WhatsApp messages simply don't reach them.
- The number depends on one phone and whoever is holding it.
- The customer doesn't know why nobody answers.
- Nobody sees how many conversations are waiting.
One number, one user per person
The first change is connecting the number to a platform that uses the WhatsApp Business API. The number stops living on a phone: each person signs in with their own user, from a computer or a phone, and everyone sees the same inbox.
You don't need a number per location. With one number the customer always writes to the same place, and inside you decide who answers. If each location already has its own number and you want to keep them, check how many lines your plan includes.
- One user per person, with a role.
- The history stays with the business, not on a phone.
- Someone who moves to another location still sees the same conversations.
Organize your team's customer service in one inbox.
Assign each conversation to an owner and keep track of everything the team still has pending.
Distribute by workload, not by who saw the message
An entry menu asks the customer which area they want to talk to. Each option can hand off to one person or to a department of several. If the sales department includes people from every location, the conversation goes to just one of them: whoever has the fewest open conversations at that moment.
That way the distribution adjusts itself. When the branch is swamped, new conversations go to head office, and the other way round. The customer gets a greeting from the person who will help them.
- Build departments by topic (sales, admin), not by location.
- Add people from every location to each department.
- Close finished conversations: open ones are what counts as workload.
Hand a conversation to another location without losing context
Sometimes a conversation was already taken by someone who then can't get to it. Instead of letting it wait, transfer it to a colleague. Whoever receives it sees the whole conversation.
Before transferring, leave an internal note: what the customer asked, what is missing and what was promised. The note is for the team; the customer doesn't receive it.
- Transfer as soon as you know you won't make it, not at the end of the day.
- A short note saves the customer from repeating everything.
- Whoever receives the conversation also gets a notification.
Look at every location with the same numbers
With the whole team in one inbox, reports show every location together: how long the first reply takes and, person by person, how many messages they sent and how long they took to answer.
Use those numbers to adjust who is in each department and at what times, not to compare one location with another: a branch with a counter will always have less time for WhatsApp.
- First reply time is the number the customer feels most.
- Conversations per person show where work piles up.
- Review it once a week, with the team.
How to do it in Volga
In Settings → WhatsApp you connect the business number, and in Settings → Team you invite each person with their name, email and role. In the Inbox, every conversation shows who has it; “Unassigned” gathers the ones nobody took and “My chats” shows each person's own.
In Settings → Auto-reply you build the entry menu. An option can “Hand off to a department (several people)”: you tick whoever handles it, from any location, and Volga hands each chat to just one person, whoever has the fewest unclosed chats at that moment. To hand over a conversation that was already taken, leave an internal note and use “Transfer conversation”: a record of who passed it to whom is kept, and the receiver sees the “A chat was assigned to you” notification. In Reports, the “By agent” table shows the whole team together.
- One number for every location; each person with their own user.
- A menu department distributes chats across several people by their unclosed chats.
- Internal note and “Transfer conversation” to hand a chat to another location.
Frequently asked questions
Questions about this guide
Do I need one WhatsApp number per branch?
No. With a single number connected to the platform, every location works from the same inbox and the entry menu distributes the conversations. If you prefer one number per location, it depends on how many lines your plan includes.
Does the customer find out that another location is answering?
They don't need to: they write to the same number and someone from the business replies. If the menu option has an introduction message, they get a greeting from the person who will help them.
What happens to a conversation that someone took and can't answer?
It is transferred to another team member, with an internal note. Whoever receives it sees the whole conversation and gets a notification.