Franchise and multi-location bots: one brand, many numbers

Updated 2026-09-19 · 4 min read · By the Convo360 team

The multi-location problem

A franchise or chain with ten outlets faces a familiar tension: each outlet needs its own WhatsApp number, its own bookings and its own stock answers, but the brand experience, meaning tone, menu structure and offers, needs to look identical everywhere. Building ten separate bots means every price change or new offer has to be copied ten times, and drift creeps in fast: one outlet's bot still mentions last month's offer while another has already updated.

The fix is structural: separate what's local (contacts, appointments, inventory, the manager's escalation number) from what's shared (greeting script, tone, FAQ answers, offer logic), and build each only once. Everything that follows in this playbook is built on that one distinction.

This matters more as a chain grows. A three-outlet business can survive some manual copying; a thirty-outlet chain cannot, and the businesses that plan the workspace and sub-flow structure early avoid a painful rebuild later.

Workspaces per outlet

Convo360's Workspaces feature lets several bots run under one login, each with its own contacts, appointments, CRM pipeline and connected WhatsApp number. Set up one workspace per outlet so a customer messaging the Andheri store never sees Powai's booking calendar, and each store manager can be given access only to their own workspace via team roles.

This also keeps analytics clean: each outlet's conversation volume, response times and conversions are tracked separately, which matters for franchise performance reviews. A simple way to think about the split:

Sharing logic with sub-flows

The conversation logic, meaning greeting, menu, FAQ answers and booking steps, should exist once as a sub-flow, and every outlet's main flow calls it with a Call Sub-flow block, passing the outlet's own variables (address, contact number, working hours) as parameters. A typical setup looks like this: trigger 'New conversation' on the outlet's number, first block is Set Variable (outlet name, city, manager number), then Call Sub-flow pointing to 'Brand-Menu-v1', which renders the same List Menu everywhere but fills in the outlet variables where needed.

When head office needs to update the FAQ answers, add a new offer, or fix a wrong price, editing the shared sub-flow updates every outlet at once, so there's no need to open ten flows and repeat the same edit ten times. Outlet-specific details stay as variables rather than hardcoded text, so the shared sub-flow never needs to know which outlet is calling it.

Routing customers to the right outlet

There are two common patterns, and most chains eventually use a mix:

• Separate numbers: each outlet has its own WhatsApp number and its own workspace. This is the simplest option, and works well when outlets are geographically distinct and marketed locally (a poster outside each store with that store's number).
• One central number: a single WhatsApp number for the brand, with a List Menu asking the customer's city or pincode, then a Condition block routing to the right sub-flow or transferring the conversation context to that outlet's team via live-chat handoff.

Most franchises with outlets spread across different cities prefer separate numbers, since local marketing (a shop-front QR code, a local social page) naturally drives traffic to the right number. Dense multi-outlet cities, say five branches across Mumbai, often prefer one central number with pincode-based routing, since a customer rarely knows which specific branch number to message.

A rollout cadence for adding outlets

Chains adding several outlets a year benefit from a fixed rollout rhythm rather than treating each new store as a one-off project. A simple weekly cadence for a new outlet:

Following the same five-day rhythm for every new outlet means a chain can onboard a new store's bot without pulling in whoever built the first one from scratch.

Central reporting and measuring outlet performance

Franchise owners or area managers need one view, not ten dashboards. Use Analytics at the account level to see conversation volume, response time and booking conversion aggregated across all workspaces, alongside per-outlet breakdowns for spotting which locations are lagging. This is where staff roles matter too: an area manager can get read access across all outlet workspaces without owning any of them.

Three numbers are worth comparing across outlets every month: reply rate within the first hour, booking or order conversion from the FAQ menu, and how often a conversation needed human takeover instead of the bot resolving it. An outlet consistently lagging on the last metric usually needs its local variables or offers refreshed, not a whole new flow.

Step by step

1. Create a workspace per outletSet up a separate workspace and connect that outlet's WhatsApp number via embedded signup.
2. Build the shared brand sub-flow onceCreate one sub-flow with the greeting, FAQ menu and booking logic, using variables instead of hardcoded outlet details.
3. Call the sub-flow from each outlet's flowDuplicate the standard outlet flow template and point its Call Sub-flow blocks at the shared sub-flow.
4. Choose a routing patternDecide between separate numbers per outlet or one central number with pincode-based Condition routing.
5. Scope team access per workspaceAdd each outlet manager as a team member limited to their own workspace; give area managers broader read access.
6. Review central Analytics monthlyCompare reply rate, conversion and human-takeover rate across outlets to spot locations that need attention.

Example conversation

Frequently asked questions

Related reading

Available across India — see WhatsApp & AI calling automation by state and city.