WhatsApp for a business with branches or brands: one number or one per branch, separate inboxes and teams, and one dashboard over all of them
When one number with routing is enough and when each branch or brand needs its own workspace, and how a business account gives the owner one dashboard, one Meta login and one currency across them.
Agencies and branches4 of 4 in this topic
A business with several branches or brands can use one WhatsApp number for all of them, with chats routed to each branch's team, or give each branch its own number, inbox and team. In Linkubit the second is a workspace per branch under one business account, so the owner sees every branch on one dashboard and connects the Meta login once. Each branch can keep paying for itself or move onto one bill.
On this page
One number for everything, or one per branch?
| One workspace, one number | A workspace per branch or brand | |
|---|---|---|
| Customers see | One number for the whole business | Their branch's own number, Page and email |
| Leads go to | One inbox, routed to branch teams by rules | The branch's own inbox |
| The AI salesperson | One catalogue, one set of rules | Each branch's own catalogue, prices and rules |
| Reports | One pipeline, split by owner or territory | One pipeline per branch, compared on the account dashboard |
| Right for | Branches selling the same thing at the same price | Franchises, separate brands, or branches with their own prices and teams |
If every branch sells the same things at the same prices, one workspace with routing is simpler: Pune leads to the Pune team, Bengaluru leads to the Bengaluru team. On Scale, territories mean each team sees only its own customers. If branches have their own prices, numbers or staff who shouldn't see each other's customers, give each its own workspace.
A business account over the workspaces
When you create a second workspace, Linkubit asks whether to set up a business account. Say yes and your workspaces are grouped under it: one dashboard with a card per branch, your Meta login connected once with each number, Page and ad account given to its branch, and people given access to the branches they work in. Say no and the second workspace stays separate.
Billing: each branch, or one bill
Grouping workspaces does not move their billing. Each branch keeps paying for itself until you move it onto the account's bill; from then on the account pays for it on one invoice, with a line per plan, and its credits join the shared pool. A branch with its own subscription that moves onto the account has that subscription ended the same day with the unused time credited. The billing guide is written for agencies, and works the same way for branches.
One currency
Your first sign-up asks what your customers pay in, rupees or dollars, and every branch created afterwards uses the same. It can't be changed later, so your reports never add rupees to dollars.
What the owner sees
- A card per branch: its plan, its number and ad accounts, credits this month.
- An activity feed of branches created, assets moved and people added.
- Any branch's inbox and pipeline, by opening it. The owner gives themselves access the same way as anyone else.
Can one customer talk to two branches?
Yes, and each branch sees its own conversation with them. Workspaces do not share contacts; a customer in two branches is two records, one in each.
Can a branch manager see other branches?
Only if they are given access to them. Access is granted per person, per workspace.
Does a business account cost extra?
No. The account has no price of its own; you pay for the workspaces' plans, whichever way each one is billed.
Read next
More on Agencies and branchesLinkubit vs other toolsWhatsApp templatesCost calculatorPricing
Try it on your own number. Start free, no card, or see the pricing.