Two branches, three outlets, one inbox: running multiple locations on WhatsApp with AI agents

The second branch is where WhatsApp gets messy. Customers message the wrong number, the branches quote different prices, and the owner reads two inboxes on two phones. The fix is a structure: one agent and number per branch with local knowledge, one inbox for the group, and a small set of things that stay central.

By Ritchie, ReplyKit · Published 5 September 2026 · 6 min read

Quick answer

Give each location its own WhatsApp number and its own AI agent, with that branch's hours, staff, prices and services as knowledge, and put all of them in one shared inbox and leads list. Keep brand tone, policies and the FAQ central and copy them into each agent. Route customers by putting each branch's number on that branch's Google profile, signage and pages. ReplyKit's Growth plan covers three numbers and five agents; Pro covers fifteen numbers.

The structure Getting customers to the right number What stays central Setting it up FAQ

The structure

One number per branch. Customers in Penang should not reach the KL desk. Each number is connected to its own agent.
One agent per branch. Local hours, local staff for booking, local prices if they differ, local parking and directions.
One inbox. Every branch's conversations in one place, filterable by number, with handovers flagged for whoever owns that branch's shift.
One leads list. Group-wide, with the branch on each lead, so head office sees the funnel and each branch sees its own.
Central knowledge copied down. Brand tone, policies, the FAQ and instructions live in one master document and are pasted into each agent, so a policy change is one edit and three pastes.

Getting customers to the right number

Put each branch's number only where that branch is: its Google Business Profile, its signage, its page on your website, its receipts. On a shared website contact page, list branches with their numbers and a map. Instruct every agent to redirect gracefully: "That branch's number is [X], or I can book you here in [this branch] if that's easier." The redirect note lives in the central document so it is identical everywhere. Our guide to placing your number covers the details.

What stays central

Tone and the agent instructions template.
Policies: deposits, cancellations, refunds, disclosure.
The FAQ, with branch-specific answers marked by branch.
The Acceptable Use boundaries: what the agent never says, in every branch.
The weekly teaching session: one person reviews all branches' unanswered questions and updates the master.

Setting it up

Pick the plan: Growth for up to three numbers and five agents, Pro for fifteen numbers and unlimited agents.
Create one agent per branch, named by branch. Paste the central instructions, then add the local block: hours, staff, address, parking.
Upload the price list per branch if prices differ, or the shared one if not.
Set services and hours per branch, and staff availability per branch.
Pair each branch's dedicated number, one at a time, and run the twenty-message test on each.
Assign inbox ownership per branch per shift.

Frequently asked questions

Can one AI agent serve two branches?

It can, but hours, staff and directions differ, so one agent per branch with its own knowledge is cleaner. Both branches still share one inbox.

How many numbers do I need?

One per branch. The Growth plan covers three numbers and five agents; Pro covers fifteen numbers.

How do customers reach the right branch?

Put each branch's number only on that branch's Google profile, signage and web page, and let each agent redirect politely.

Can head office see everything?

Yes. One inbox and one leads list across branches, filterable by number, with the branch on each lead.

How do I keep policies consistent?

Keep a master document for tone, policies, FAQ and boundaries, and paste it into each agent when it changes.

One inbox for every branch

Three numbers and five agents on Growth, fifteen numbers on Pro. 7-day free trial.

See plans

Written by Ritchie, ReplyKitPart of the small team in Malaysia that builds and runs ReplyKit. Writes about WhatsApp automation, AI customer service and small business lead response.

How we know this. ReplyKit's Growth plan (three numbers, five agents) and Pro (fifteen numbers) exist for this, and the one-agent-per-branch pattern here is how multi-outlet customers run it. Product figures in this article (limits, prices, per-reply costs) are taken from ReplyKit as it runs today and are re-checked when we update the page. Where we cite outside research, the source is linked below. We sell ReplyKit, so read our product claims with that in mind; we say where a different tool or no tool is the better choice. About ReplyKit.

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
Google Business Profile Help, Chat with customers
ReplyKit, Will WhatsApp ban my number for automation? · how Meta's messaging limits and quality rating work

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.