Summary
This post looks at WhatsApp Business through the lens of access, not headcount. Adding a second or third person to a shared number is the easy part. Deciding who should see everything, who should only see their own queue, and who needs full admin rights is the part most teams skip, and it is usually what causes problems later. It works through three access levels, what changes once a business runs several branches or departments instead of one team, and a real example from Severs Breeman BMW and MINI, a five branch dealer group that had to solve exactly this at department level.
TL;DR
- Most teams solve "multiple users" by adding logins and stop there, without deciding who should actually see what.
- Three access levels cover almost every setup: agent, manager, and admin.
- Severs Breeman BMW and MINI runs fifteen separate WhatsApp flows across five branches, each routed automatically to the right department.
- Getting access levels right before rollout avoids two common failure modes: managers with no real oversight, and agents who can see far more than their role needs.
An Operations Manager watching a WhatsApp number grow from one person to five rarely starts by thinking about access control. The immediate problem is coverage. Who answers when someone is out, who covers the counter during lunch, who takes over once a second branch starts asking for WhatsApp too. Getting more people connected feels like the whole job.
It is only half of it. Once several people share one number, the harder question becomes who can see what, and who is accountable for which conversation, not simply who has a login. A junior agent who can view every customer's full history across every branch has more access than the role calls for. A branch manager who cannot see how their own team is performing has less than the role needs. Both of those tend to get set by accident, on the day a team moves from one person on WhatsApp to several, rather than by anyone actually deciding.
Most guidance on running WhatsApp with multiple people stops at how to add them. It rarely covers how much of the number each person should actually control.
How much access does each person actually need?
Every WhatsApp Business setup with more than one person eventually needs an answer to this. Should this person see every conversation, only their own, or somewhere in between. Skipping that decision does not make it go away, it just hands the answer to whatever the platform defaults to, and defaults are rarely built around your org chart.
What are the three access levels that matter?
In practice, almost every WhatsApp Business team fits into one of three roles, each with a different reason to exist.
| Access level | Who it's for | What they can do |
|---|---|---|
| Agent | The person replying to customers day to day | Their assigned conversations and a shared knowledge base or quick replies; full visibility into every branch's history adds noise rather than value |
| Manager | Whoever answers for a team's output, one branch or one department | Sees workload, reassigns conversations, checks response times, without necessarily touching every other department's queue |
| Admin | The smallest group by far | Controls integrations, routing rules, and who else gets added; usually the layer where governance questions get answered directly |
What changes once you are managing locations, not just people?
Severs Breeman BMW and MINI, a family owned dealer group with five branches across the greater Rotterdam region, ran into this at a scale most single location teams never reach. Phone pressure at the workshop counter was the starting problem, not access control. A customer calling about a scheduled repair, a callback that got missed, a service advisor already on another line: the front desk phone stayed busy enough that both staff and customers lost time to it.
The fix started small, with a QR code at the counter routing customers to WhatsApp instead of a callback request. It grew into something that could not run on one shared inbox without real structure behind it: fifteen separate flows, each tied to its own phone number and department, with smart routing making sure a workshop question from one branch never landed with a sales advisor in another. That structure is what turned into 658 minutes of phone time saved in the first month alone, a number that kept climbing as more staff and departments came online.
None of that works with one shared login and a flat list of conversations. It works because every branch and department has a defined slice of the number, and everyone inside that slice has access that actually matches what they are responsible for.
Where does this usually go wrong?
The mistake we see most often is not too little access being handed out. It is too much, given by default because nobody thought it through. A new hire gets full visibility "just in case," a manager never gets reassignment rights because nobody asked for them, and six months later nobody can say with confidence who was actually responsible for a specific customer's conversation. This is a pattern that shows up any time a shared tool grows faster than the permissions sitting underneath it. The fix is deciding, before the second or third person joins, which of the three levels above they belong to, and checking that again as the team or the number of locations grows.
How do you set this up without redoing it later?
Start with a short exercise before adding anyone new. List who touches the number today, then decide, for each of them, whether they need agent, manager, or admin access, department by department if there is more than one. A shared WhatsApp inbox built for multiple users turns this into a configuration decision instead of a workaround, but someone who actually knows the team still has to make the call, rather than leaving it to whatever the platform defaults to.
For an automotive retail business specifically, this usually means separating sales from service from day one, since the two rarely need visibility into each other's conversations, and adding a branch level split the moment a second location comes online rather than after it causes a mix up.
Getting the structure right before the headcount grows
A WhatsApp Business number that works well for two people and one that works for twenty are not the same setup with extra logins bolted on. The difference is whether access was designed around roles and locations early, or added after the first mix up already happened. Teams that get the structure right once tend to stop thinking about it, which is really the point of doing it properly the first time.
Curious what agent, manager, and admin access could look like across your own branches or departments? Get in touch with Saysimple and walk through a setup built around how your team actually works.
