WhatsApp for franchises and multi-branch businesses: one number or many, shared knowledge with local differences, routing customers to the right branch, and keeping head office in the loop
A chain's WhatsApp problem is scale and consistency at once: every branch answers the same brand questions differently, head office cannot see any of it, and customers message the wrong branch. The setup that works separates what is shared from what is local, and gives every branch its own inbox under one roof.
Quick answer
Give each branch its own WhatsApp number and its own agent, each carrying the shared brand knowledge (services, policies, tone) plus a short local note (address, hours, prices if they differ, staff, parking, local promotions), with bookings into that branch's calendar and branch staff on that branch's inbox. Keep one central number for general enquiries that asks the customer's location and sends them the right branch's number. Head office sees every inbox and exports leads across branches. ReplyKit's Growth plan covers three branches and Pro fifteen, under one account.
One number or one per branch
| Model | Good for | Trade-offs |
|---|---|---|
| One central number, one agent | Brands where every branch is identical and bookings are central | Customers must say which branch; local quirks get lost; one number's daily limits cover everyone |
| One number per branch, one agent each | Most chains: local hours, prices, staff, parking | More numbers to manage; each branch needs its own knowledge note; limits scale with branches |
| Central number plus branch numbers | Chains that advertise nationally but serve locally | Central agent routes by location; branch agents handle the rest |
The per-branch model wins for anything with local hours, prices or calendars. Each number is also independently capped at 200 replies a day, so volume scales with branches rather than piling onto one line; the limits are explained in the daily limits guide.
Shared knowledge, local notes
- Shared. Brand description, services and standard prices, policies, tone and persona, the FAQ. Write once, paste into every agent, update everywhere when it changes.
- Local note per branch. Address and directions, hours and holidays, local price differences, staff names, parking, this month's local promotion, which services this branch does not offer.
- Instructions. Shared, with one line naming the branch and telling the agent to prefer the local note where it conflicts.
- Bookings. Each branch's services and hours in its own calendar, so the agent books into the right place.
- The knowledge structure is in what to put in the knowledge base, and the two-location version in running two locations on one setup.
Routing customers
- Print each branch's number on that branch's signage, Google Business Profile and local ads, so most customers reach the right one directly.
- The central number's agent asks "which branch is closest to you" and replies with that branch's number and a click-to-chat link.
- Branch agents, when asked about another branch, give its number rather than answering for it.
- Google Business Profile chat buttons per location are set up as in adding WhatsApp to Google Business Profile.
Staff access and head office
Branch staff work their own inbox, take over chats and hand back. Head office sees all inboxes, the leads across branches, and the unanswered-questions list per agent, which is the fastest way to spot a branch whose local note is out of date. Monthly, export leads by branch and compare response and booking rates; the metrics are in metrics that matter. For franchisees who own their own accounts, the franchisor supplies the shared knowledge as a document and each franchisee runs their own ReplyKit; the agency model in marketing agencies shows how a central team can set them up.
One honest note before the setup. ReplyKit connects to your number by QR pairing, the same linked-device mechanism as WhatsApp Web. It is live in minutes and needs no Meta approval, but Meta does not sanction automation this way, so a number can be restricted. We enforce limits of 30 replies an hour and 200 a day per number with a warm-up ramp for new numbers, reply to inbound messages only, and recommend a dedicated number rather than your main line. The full picture is in our ban guide.
Frequently asked questions
Should a chain use one WhatsApp number or one per branch?
One per branch for anything with local hours, prices or calendars, plus an optional central number that routes by location.
How do I keep brand answers consistent across branches?
Write the shared knowledge once and paste it into every agent; each branch adds a short local note.
Can head office see every branch's conversations?
Yes. All inboxes, leads and unanswered-questions lists are visible under one account on the Growth and Pro plans.
How many branches can one account run?
Three numbers on Growth, fifteen on Pro, each with its own agent and calendar.
What about franchisees who own their own accounts?
The franchisor supplies the shared knowledge as a document and each franchisee runs their own account; a central team can set them up.
Every branch answered, every branch visible
Shared knowledge, local notes, one inbox per branch, head office oversight. 7-day free trial, no card.
Sources and further reading
- Harvard Business Review, The Short Life of Online Sales Leads (Oldroyd, McElheran, Elkington, 2011) · firms that responded within an hour were about seven times more likely to qualify the lead
- WhatsApp Business Messaging Policy · opt-in, opt-out and prohibited-use rules every business must follow
ReplyKit is an independent product and is not affiliated with or endorsed by Meta or WhatsApp. This article is general guidance for running a small business, not legal, financial or regulatory advice.