A business with one shop answers WhatsApp from one phone. A business with six branches has questions the single shop never faces: whether customers message one number or six, who at head office can change the account, and how anyone finds out that one branch takes a day to reply.
The WhatsApp Business API answers the first question through Meta’s account structure and leaves the other two mostly to the inbox connected to it. For most multi-location businesses the workable setup is one business portfolio, one central number or a small set of branch or regional numbers, and branch-level permissions and reporting built in the inbox.
- Identity lives on the number — display name, business profile and the free service-message allowance are per phone number
- Templates, billing and limits sit higher up — every branch number shares them
- Numbers are capped — two to start, 20 at most, so a large chain needs regional numbers or one central one
- Meta’s permissions cover the account, not the chats — who sees which branch’s conversations is set in the inbox
- Meta reports by phone number — anything finer needs a branch tag on every chat
How Meta structures a multi-location WhatsApp account
Everything on the API sits inside a Meta business portfolio, which holds the business’s WhatsApp accounts and the phone numbers registered to them. How those pieces are grouped is changing. Meta’s developer video on the change puts it this way:
A new account architecture for the WhatsApp Business Platform splits the existing WhatsApp Business Account (WABA) into two types: a WhatsApp Account (WAAC) for phone numbers and a Messaging Account (PMA) for templates and billing.
For a business with several locations, the split names something that was already true. Each phone number carries a customer-facing identity of its own, while the working assets sit above the numbers and are shared by every number connected to them. Three levels matter:
| Level | What lives there | What it means for branches |
|---|---|---|
| Business portfolio | Business verification; the messaging limit on template conversations | One verification covers the business; one branch’s campaign draws on the same limit as every other branch |
| WhatsApp Business Account | Message templates; billing. Meta’s new model calls this level the Messaging Account | A template approved once can be sent from any branch number on that account |
| Phone number | Display name; business profile, including an address; Official Business Account status; 1,000 free service messages a month | A branch number can show the branch’s own name and address, and has its own free allowance |
Two of those levels have consequences that are easy to miss. Since October 7, 2025, Meta has applied messaging limits, the cap on how many conversations a business can open with templates in a rolling 24 hours, at the business portfolio level, shared by all of its phone numbers. A branch that sends a promotion to its whole customer list uses capacity the other branches were counting on for booking reminders.
The free allowance runs the other way. Meta’s WhatsApp Business FAQ says that “For every business phone number, the first 1,000 service messages are free each month”, so each number has its own. Service messages are the replies sent while a customer’s 24-hour window is open, which since October 1, 2026 are otherwise billed per message.
One number or one per branch?
This is the decision that shapes the rest, and the API supports either. The constraint is in Meta’s phone number documentation:
Business portfolios are initially limited to 2 registered business phone numbers, but this limit can be increased to up to 20.
So a chain of 30 branches cannot give every branch its own number. In practice that leaves three options: one central number, a number per branch for a smaller network, or a number per region for a larger one.
| Question | One shared number | A number per branch |
|---|---|---|
| What the customer messages | The same number everywhere | The number on their branch’s sign, card or listing |
| Name and address shown | One brand name and profile | Each branch’s own display name and address |
| Getting the chat to a branch | Routing rules in the inbox | Built in: the number is the branch |
| A customer who uses two branches | One thread, one history | Two threads, history split between them |
| Free service messages | 1,000 a month in total | 1,000 a month for each number |
| Reporting by branch | Needs a branch tag on every chat | Meta’s own analytics split by number |
| Ceiling | None | 20 numbers per portfolio, after a limit increase |
A single number suits a business customers see as one brand, where a booking can land at any branch: a clinic group with central scheduling, or a franchise with one ordering line. Separate numbers suit branches that run like local shops, with their own staff, their own regulars and customers who already know which branch they want.
Either way, keep every number in the same portfolio and the same account. Templates are then approved once and shared, and nobody maintains five copies of the same appointment reminder.
Getting each chat to the right branch
On a shared number, the first job is finding out which branch a customer means. The mechanics of assigning a chat to a person are in Routing WhatsApp Chats to the Right Team Member. For a business with several locations, three signals do most of the work:
- Ask which branch: open with a short menu of branches. A reply-buttons message offers up to three choices, and a list message handles more.
- Ask for a location: the API’s location request message shows the customer a button that opens WhatsApp’s location-sharing screen. The shared location arrives in the message webhook with its latitude and longitude, which the inbox can match to the nearest branch.
- Remember the answer: store the branch against the customer’s WhatsApp ID, so their next chat goes straight there without the menu.
Permissions: what Meta controls and what it doesn’t
Meta’s permissions decide who can change the WhatsApp setup. People in the business portfolio get partial access or full control of a WhatsApp account. Partial access is divided into tasks for message templates and phone numbers, the broadest being “Manage phone numbers and message templates”. Full control is “Manage WhatsApp business accounts”.
None of those settings decides which conversations a branch manager can read. On the API, messages reach the business as webhooks delivered to whatever inbox is connected, so who sees which chats is set up there, usually as a team or queue per branch. Two rules keep it manageable:
- Branch staff need an inbox seat, not Meta access: a receptionist answering chats never needs a role in the business portfolio. Keep that list to the few people who manage numbers and templates.
- Keep templates central: every number shares the templates and every number shares the messaging limit, so one person or team at head office should own both. Otherwise one branch’s promotion can crowd out another branch’s reminders.
Branch-level reporting
Meta’s own figures are organised by phone number. Its analytics report how many messages were sent and delivered, with per-message pricing breakdowns, and can be filtered to individual business phone numbers. A business with a number per branch gets branch reporting from Meta at no extra effort.
On a shared number, Meta’s figures cover every branch as one. The split has to come from the inbox: tag each conversation with its branch when it is routed, and report on the tag. The questions worth answering branch by branch:
- How long the first reply takes, in opening hours and outside them
- How many chats are still unanswered at closing time
- How many chats end in a booking or a sale
- How often chats are passed to another branch, which shows where the routing rules are wrong
A setup order that holds up as branches are added
- One business portfolio, verified: adding phone numbers is one of the points where Meta requires business verification, so do it before the second branch goes live.
- Decide the numbers: central, per branch or per region, with the 20-number ceiling in mind for the network the business expects to have, not just the one it has today.
- Set each number’s identity: every number has its own display name and business profile, including an address, description and website, so a branch number can show the branch.
- Grant access in two layers: Meta access for the few people who manage numbers and templates, inbox seats scoped to their branch for everyone else.
- Build the routing: a branch menu or location request on a shared number, and remember each customer’s branch.
- Tag every chat with its branch from day one: a report nobody has asked for yet costs nothing to collect now and can’t be rebuilt later.
- Write templates once: where a message differs only by branch, use one template with the branch name as a variable rather than a template per branch.
Automation fits on top of this structure rather than replacing it. The broader options are covered in WhatsApp Automation for Business: API Guide & Capabilities.
Also Read: Automating WhatsApp FAQs Without Losing the Human Touch on Urgent Requests
Key Takeaways
- Each phone number carries its own display name, profile and free service-message allowance; templates, billing and messaging limits are shared above it.
- A portfolio starts with two numbers and can reach 20, which rules out a number per branch for a large chain.
- One shared number keeps each customer’s history in one place; a number per branch gives each location its own identity and its own reporting.
- Meta’s permissions govern numbers and templates. Which branch sees which chats is set in the inbox.
- On a shared number, branch reporting depends on tagging every chat with its branch.
Frequently Asked Questions
Can each branch have its own WhatsApp display name?
Yes. A display name belongs to a phone number, so each branch number can carry its own. Meta reviews it against its display name guidelines, which require a clear relationship to the business and reject a bare place name on its own. A name that pairs the brand with the branch, written the way the business names that branch on its website, is the pattern that fits those rules.
Can a branch use its existing landline number on the WhatsApp Business API?
Yes. Landlines and freephone numbers can be registered, and Meta verifies them with a phone call that reads out a six-digit code rather than a text message. A number behind an automated phone menu has to accept the international verification call and get it to a person, so the usual approach is to switch the menu off while the number is verified.
Does each branch need its own Meta business verification?
No. Business verification applies to the business as a whole. Meta’s platform overview says: “Businesses must initiate business verification when they are ready to scale marketing, utility, and authentication conversations, add additional phone numbers, or request to become an Official Business Account.” Adding a second branch number is one of those triggers, so a multi-location business should verify early rather than wait until it is blocked.
Does an Official Business Account badge cover every branch number?
No. In Meta’s help article on requesting Official Business Account status, the request is made from a specific phone number in WhatsApp Manager, so each branch number is reviewed on its own. A business with several numbers should not assume that one approved number makes the rest official.
Can one shared WhatsApp number handle messages for every branch?
For sending speed, almost always. Meta’s platform documentation says: “For each registered business phone number, Cloud API supports up to 80 messages per second (mps) by default, and up to 1,000 mps by automatic upgrade.” The constraints a growing chain meets first are elsewhere: the shared limit on template conversations, and enough people in the inbox to answer what arrives.
Final Thoughts
The first month of branch reports usually decides what to change next. A branch with slow first replies is either short of people at the busy hours or receiving chats that belong somewhere else, and the reassignment count says which. Either one is fixed in the inbox, with no change to the WhatsApp account.
Running WhatsApp across more than one location?
ClubUnbrick sets up WhatsApp Business API accounts for multi-location businesses, with the number structure, branch routing and reporting decided before the first message goes out.
What We Offer
- Account and number structure — One portfolio, the right number of numbers, and display names and profiles for each branch.
- Branch routing — Branch menus, location requests and returning-customer rules on a shared number.
- Access and permissions — Meta access for the people who manage the account, inbox seats scoped to each branch for everyone else.
- Branch-level reporting — Response times, waiting chats and bookings, broken down by location.
Start with the branches you have today; the structure is built to take the next one.
