A business with one location has a phone problem that is easy to describe: sometimes nobody picks up. A business with twelve locations has a different problem, and it is the one that quietly loses the most revenue — a caller reaches a location, just not the right one, and nobody owns what happens next.
Multi-site and franchise operations need routing, consistency, and accountability rather than simply more people answering. Here is how to set that up.
The failure mode nobody measures
In a single-site business a missed call is visibly missed. Across multiple locations it usually is not, because the call was answered — by the wrong site, by a location that took a message for another, or by whichever number the caller happened to find online.
From the caller's side this feels like being passed around. From the business's side it looks like a call that was handled. Nobody records that a customer for the Riverside branch spoke to someone at the downtown branch and then gave up.
That is the specific problem worth solving, and it is a routing problem rather than a coverage one.
One number or many?
Both work, and the choice depends on how customers find you and how the business is owned.
Local numbers per location
Each site keeps its own number, all forwarding to the same service. The operator knows which location was dialed before the call is even answered, so the greeting and routing are correct from the first word.
This suits businesses where customers search locally and where each location has its own listings and reviews. It is usually the right default for franchises, where local presence is part of the proposition.
One central number
A single number for the brand, with the operator establishing location during the call. Simpler to advertise and easier to manage centrally, but it puts the routing burden into the conversation — which means the location question has to be asked early and well.
Many operations end up running both: local numbers for local search, a central number for brand advertising, all landing in one place.
Routing rules to settle before you start
- 1How location is determined — the number dialed, the caller's address, or a question asked early.
- 2What happens when a caller is closer to one location but asks for another, which is more common than people expect.
- 3What happens when the correct location cannot take the call — does another site cover it, or is a message taken for the original?
- 4Whether locations have different hours, and how routing changes outside them.
- 5Who receives messages for each site, and who covers when that person is away.
- 6Which calls go to a regional or head-office contact rather than a location at all.
That third item is where most arrangements leak. If the right location cannot take the call and there is no defined fallback, the call becomes a message nobody owns.
Consistency is the point of doing it centrally
The strongest argument for handling multi-site calls in one place is not cost — it is that every caller gets the same experience regardless of which location they reached.
When each site answers its own phone, standards drift. One location answers within two rings and one lets it go to voicemail on Fridays. One books appointments properly and one takes a name and a number. Customers experience that as an inconsistent brand, and in a franchise the operator with the weakest phone habits shapes the brand's reputation in that market.
A single script answered the same way everywhere fixes that without requiring each location to be managed into compliance.
Where local variation is legitimate
Consistency should not mean identical. Locations genuinely differ on hours, services offered, staff names, and sometimes pricing structures. Build those as per-location variables inside one master script rather than as separate scripts, so a brand-wide change does not have to be made twelve times — and so it cannot be made in eleven places and forgotten in the twelfth.
Reporting is what makes it manageable
Centralized call handling produces something a multi-site operation rarely has otherwise: comparable data across locations.
- Call volume by location, which is a demand signal independent of what each site reports.
- Calls arriving outside each location's hours, which shows where extended coverage would pay.
- New enquiries versus existing customers, by site.
- Appointments booked, by site.
- Escalations where the first contact did not answer — the number that identifies a location with a rota problem.
For a franchisor this is particularly useful, because it shows which markets have demand a location is not converting — which is a support conversation rather than a compliance one.
Franchise-specific considerations
Where locations are independently owned, two questions need answering before anything is built. Who owns the arrangement — the franchisor centrally, or each franchisee individually? And who sees the reporting for a given location?
Both models work. A central arrangement gives consistency and negotiating leverage; individual arrangements give each owner control over their own script and escalation. What causes friction is leaving it ambiguous, particularly around who can change the script and who is accountable for an unanswered escalation.
Start with the routing
Get the location logic right first and the rest follows. Write down how location is determined, what happens when the right site is unavailable, and who owns messages for each location. Then build the master script with per-location variables, and add escalation rules per site.
See how to write a call script and how to design an on-call escalation protocol for the components.
Answering365 answers for businesses across the country from a single trained team — see our locations coverage. To discuss routing for a multi-site or franchise operation, call 888-588-9800 or get in touch.
