Team and customer service

WhatsApp for several branches: a number per branch or one number with routing — who answers, who sees what, and how the bot knows the branch

The two ways to run WhatsApp across branches (a number per branch versus one number for all): an agent per number, a file per branch, the "assigned only" setting for teams, routing threads by district, and the owner's single inbox — with Meta's cost per number.

6 min read Updated 23 September 2026 ArabyBot team
The ArabyBot teamOfficial Meta partner · written from our own platform data
On this page 3
  1. The two ways side by side
  2. Setup for each way
  3. Frequently asked questions

The short answer

Both work on our platform and the difference is who answers: a number per branch means an agent per number with the branch's file (address, hours, stock) and the branch team seeing only its threads through the "assigned only" setting; one number for all means one agent that asks the customer for the branch or infers it from the district, and assigns the thread to that branch's team. The rule: if customers know their branch and call it, a number per branch; if they know the brand and not the branch, one number and routing. Either way, one inbox where the owner sees every branch.

Also asked as: «واتساب لأكتر من فرع رقم واحد ولا رقم لكل فرع» · «كيف اسوي واتساب لكل فروعي» · «رقم واتساب موحد لكل الفروع»

The two ways side by side

WhatsApp across branches — the two ways
ItemA number per branchOne number for all
Who answersAn agent per number with its branch's fileOne agent that asks for the branch or infers it
What the bot knowsOnly that branch's address, hours and stockEvery branch's file, answering by branch
Who sees the threadThe branch team — and the owner sees allThe team it was assigned to — and the owner sees all
The customer knowsTheir branch's numberThe brand only
CampaignsFrom each number to its customersFrom one number with a label per branch
SuitsBranches with their own customers and printed numbersA brand asked for by name, delivery by city
The two setups side by side: who replies, what the customer knows, where campaigns come from

Setup for each way

  1. A number per branch: connect each number and create its agent

    From WhatsApp tools: connect a number per branch (or move it in coexistence mode if it is on the app), then an agent per number with the branch's file: address, hours, services, prices and stock. A shared file for general policies is uploaded to all.

  2. One number: a file per branch and one question

    All branch files to the same agent, and in its instructions: "if the branch is not known from the message or a previous order, ask: which branch is nearest?". Then it answers from that branch's file.

  3. Teams see what is theirs

    From the inbox settings: "agents see only what is assigned to them". With one number the agent assigns the thread to the branch team once it knows the branch; with a number per branch each team is granted its number. Tags and assignment.

  4. The owner reads everything from one screen

    The unified inbox shows every number and branch together with the agent and tag filters, and the team report shows reply time per teammate — so you compare branches with each other.

The common mistake

One file for every branch saying "we open 9 to 9" while one branch closes on Friday and another does not. The bot says what the file says; give each branch its own file even with one number.

A file per branch plus a shared policy file, because the bot says what the file says

Frequently asked questions

1

Does one WhatsApp number work on more than one phone across branches?

On the official API the number does not live on a phone at all: the agent and each branch's team answer it from the unified inbox on browser and app, with no device limit. The real limit is who sees what, and that is a setting.

2

How does the bot know the customer's branch with one number?

It asks ("which branch is nearest?") or infers from the district or city in the message, then answers from that branch's file and assigns the thread to its team. A customer who ordered before is known by their previous order.

3

What does a number per branch cost?

At Meta the fees are per message, not per number, so the cost is the same, spread out — and each number gets its own 1,000 free replies a month. On the platform each number needs a connection and an agent with its file, and the plan sets how many numbers. Pricing.

4

Does a branch manager see other branches' threads?

As you choose: with "agents see only what is assigned to them" each team sees its own threads, and the owner and supervisor see all. With a number per branch you can also grant the number to its team only.

5

One branch now, more later — where do I start?

With one number and one file. When the second branch opens, add its file and tell the agent to ask about the branch, or add a second number with its own agent. Switching between the two loses no conversations.

The ArabyBot teamOfficial Meta business partner in the Middle East 239 guides Figures from our platform All guides

How we write these guides Figures come from our platform and Meta's actual invoices, dated with their sample; we describe what works today, not what we plan, and say what we do not do and when someone else is the better choice. Reviewed by the ArabyBot team on 23 September 2026.

Share this guide
And you run all of it from your phoneEverything on this page is also run from the ArabyBot mobile app — replies, orders, campaigns and AI reports. Not a web dashboard only.

Try the agent before you pay anything

The agent that will answer your customers is the one answering you now: ask it from the chat button here or on WhatsApp. Your account is free with no credit card, and the free trial on your own number or page is activated after you contact our team on customer-service WhatsApp.