Key takeaways
- Pick a model on purpose: each site answers its own calls, one central desk answers all of them, or local first with a shared overflow and after-hours layer.
- Keep a local number for every location; Google asks for a number that connects to the individual location rather than a central helpline[2].
- Write a one-page location sheet for each site and give each a transfer number that is not the line it forwards from.
- Keep one shared record of customers across sites, but report answer rates and bookings location by location.
- Firms with 100 to 149 employees ran about 2.6 locations each in 2022, so most growing businesses meet this problem sooner or later[1].
The second location breaks the old phone habits
With one location, the phones run on habit. Whoever is nearest picks up, everyone knows the schedule, and a caller asking for 'the guy who came last Tuesday' gets an answer. Open a second site and the habit stops working. Callers ring the wrong branch, staff at one site can't see the other's calendar, and the busiest location quietly misses the most calls while the quiet one has people free. Missed calls at small businesses covers the general causes; this guide covers the ones that only appear once there is more than one front desk.
It is a normal stage of growth. In 2022, US employer firms with fewer than 20 employees ran almost exactly one establishment each: 5,777,467 locations for 5,720,093 firms. Firms with 50 to 74 employees averaged about 1.6 locations, and firms with 100 to 149 about 2.6[1]. Some industries split earlier than others. The National Restaurant Association counts 7 in 10 restaurants as single-unit operations, which leaves 3 in 10 as part of multi-unit businesses[3], and about one in six US dentists was affiliated with a dental support organization in 2025[4].
Source: U.S. Census Bureau, 2025[1]
Show the data
| Employees at the firm | Value |
|---|---|
| Under 20 | 1.01 locations |
| 20 to 24 | 1.13 locations |
| 50 to 74 | 1.6 locations |
| 100 to 149 | 2.64 locations |
| 200 to 299 | 5.05 locations |
| 400 to 499 | 9.09 locations |
Central, local or hybrid
There are three workable structures. Each can be right. The wrong one is the structure nobody chose, where calls go wherever the phone system happened to be set up years ago.
| Model | How it works | Fits when | Watch for |
|---|---|---|---|
| Local | Each location answers its own number with its own staff | Sites are busy enough to keep someone on the phone, and callers know the local team | Gaps at lunch and after hours; no backup when one site is swamped |
| Central | One desk answers every location's calls and books for all of them | Services and prices match everywhere and schedules live in one system | Callers who want local knowledge; directions, parking and who's on today |
| Hybrid | Local staff answer first; overflow and after-hours calls go to one shared layer | Most multi-site small businesses, especially with uneven call volume | Clear rules on what the shared layer may promise for each site |
To choose, pull two weeks of call logs for every site and line them up by hour. If each site's missed calls cluster in a few predictable hours, such as opening, lunch and the last hour before closing, local answering with a shared overflow layer will fix most of it. If the sites are equally busy all day and offer the same services at the same prices, a central desk starts to make sense. If one site misses calls all day long, the problem is staffing at that site, and no routing model will hide it for long.
Most businesses with two to five sites end up hybrid. The local team keeps the calls it handles best, the regulars and the walk-in questions, and the shared layer catches what local staff can't reach. That layer can be a person at head office, an answering service or an SI Employee that each location's line forwards to when busy or closed. Virtual receptionist vs answering service compares the staffed options.
Cost shapes the choice. Example: a central desk staffed 50 hours a week needs about 217 paid hours a month. At the BLS average of $36.73 an hour in total compensation for office and administrative support workers[5], that is around $7,950 a month, before cover for breaks, sickness and vacations. A hybrid setup only asks that person, or service, to cover the gaps, which is why it is usually where small groups start.
Keep a local number for every location
Whatever model you pick, keep each location's own phone number on its listing, its signs and its page on your website. Google's guidelines for business profiles ask for a phone number that connects to the individual location, and say to use a local number instead of a central call center helpline whenever possible[2]. A single toll-free number on every listing makes the routing problem worse, because now every caller has to be asked which branch they mean.
The local number helps on the way back out too. People screen numbers they don't recognize: only 19% of US adults say they generally answer calls from unknown numbers[6]. A callback from the branch number the customer dialed has a better chance of being picked up than one from head office or a staff mobile. Where your phone system allows it, set each location's outgoing caller ID to match its incoming number.
Forwarding keeps the numbers in place. Each location's line forwards to the shared layer on a schedule, or only when busy or unanswered, so customers keep dialing the number they already have. If one central number does exist, for example on a fleet of vans, the first question on that line should be which location or which town the caller is in. A forwarded call does not tell whoever answers which sign, ad or listing the caller saw, so ask.
Routing rules, location by location
Routing is where multi-site coverage usually goes wrong, mostly because the rules live in one manager's head. Write them down per location before any call is forwarded.
List every number
Main lines, direct lines, old numbers still printed on vans and listings. Note which location each one belongs to and where it rings today.
Write a location sheet
Address, parking, hours, holiday closures, services offered there, who works there on which days, and the price information you are willing to give.
Choose transfer numbers
A manager's direct line or mobile per site, plus a backup. Not the main line that forwards out, or the call has nowhere to go.
Set the cross-location rule
What happens when a caller wants a service only another site offers, or a date only another site has free.
Forward one site first
Overflow during opening hours, all calls after closing. Add the next location once the first runs clean for a week.
Test every state
Call each location's number while open and busy, after closing and on a holiday. Check the greeting, the facts and the transfer.
Example: a caller to the fictional Riverside shop wants a wheel alignment, which only Northgate does. The written rule says to offer Northgate's next opening, give the address twice and record the booking request for Northgate to confirm. Without a rule, the same call gets three different answers depending on who picks up, and one of them is 'we don't do that here, sorry.'
- Caller
- System
- SI Employee
- Your team
01Caller
Caller dials Riverside
The Riverside counter is busy with two customers.
02System
Line forwards on no answer
Riverside's line forwards after four rings; the caller dialed the usual number.
03SI Employee
Answers as Riverside
Uses Riverside's greeting, hours, address and services.
04SI Employee
Routine request handled
Takes the booking request or message and reads the details back.
05System
Needs a person
Transfers to the Riverside manager's direct line, then the backup.
06System
Summary by email
Names the line that answered; recording and transcript in the shared record.
07Your team
Riverside follows up
Confirms the booking or calls back from Riverside's own number.
Example flow for a fictional three-shop business. Each location has its own forwarding rule, greeting, facts and transfer numbers.
With an SI Employee as the shared layer, that means one receptionist set up per location, each with its own greeting, location sheet and transfer number, and a name that says which site it covers. The summary email names the receptionist that answered, so one shared inbox can be sorted by location with an ordinary mail rule. If a transfer goes unanswered, the call comes back, the caller is told plainly that nobody could pick up, and an urgent message is saved with the call.
One record of each customer, shared between sites
Customers don't think in locations. They book at one branch, pay at another and call whichever number their phone remembers. If each site keeps its own notebook, the second call looks like a new customer and the history is lost. Four rules keep a shared record useful:
- One contact list for the whole business, with a home location noted on each customer.
- Every call logged against the contact, whichever site took it: date, reason and outcome.
- Notes written for a stranger, because the colleague at the other branch reading them has never met the customer.
- Clear ownership: the site that holds the booking owns the follow-up, even if another site took the call.
Calls answered by the shared layer should land in the same place. In an AssistCall account, every forwarded call from every location sits in one call list with its recording, transcript and summary, contacts export as CSV, and signed webhooks can pass each call to your own systems, including through Zapier, Make or n8n. How an AI receptionist works explains what happens between the forwarded ring and the emailed summary. Medical and dental groups have extra rules about what a phone summary may hold; the guide to central call centers for multi-location practices covers that version of the problem.
Report by location, not just in total
A combined answer rate hides the site that is struggling. Report each location separately, every week, on the same handful of measures, and keep the definitions identical across sites so the comparison is fair.
| Location | Calls | Answered live | Answered by overflow | Missed | New bookings |
|---|---|---|---|---|---|
| Northgate | 260 | 71% | 26% | 3% | 38 |
| Riverside | 180 | 84% | 14% | 2% | 27 |
| Airport Road | 140 | 90% | 8% | 2% | 19 |
Example: Northgate sends about a quarter of its calls to overflow, while Airport Road answers nine in ten itself. That is not a performance problem at Airport Road. It is a staffing problem at Northgate, where the busiest counter has the same two people as the quietest one. Moving one service advisor's lunch, or adding a third person on Monday and Friday mornings, will do more than any new script.
Go through the same measures monthly with each site manager and listen to two or three calls per location together. The auto repair service desk example models how a single six-bay shop would split calls between advisors and an overflow layer; a multi-site group is that model repeated, plus the routing rules above. The service standards themselves don't change by site, and customer service for small business sets them out. Every location should also open calls the same way, with its own name in the greeting (answering a business phone professionally).
Trades opening a second service area face extra steps beyond the phones, such as licensing in a new jurisdiction; opening a second location works through them for plumbers.
Frequently asked questions
Should each location have its own phone number?
Yes, on its listing, signs and website page. Google asks for a number that connects to the individual location, and customers remember their branch's number. A central number can sit alongside the local ones, not replace them.
How do I route calls to the right location from one number?
Ask first: which location, or which town. Then follow that location's rules for hours, services and transfers. Publishing each location's own number means fewer callers need routing at all.
Can a central team book appointments for every location?
Only if it can see every location's schedule and knows what each site offers. Without that, the central layer should take a booking request and let the site confirm it.
What should happen when a caller wants a service only another location offers?
Write the rule down. Either book them at the other site and repeat the address twice, or take a request for that site to call back. Never leave the caller to find the other number on their own.
How many locations before a central desk makes sense?
There is no fixed number; it depends on call volume and how alike the sites are. Many small groups run local answering plus a shared overflow and after-hours layer long before they hire a dedicated central team.
References
U.S. Census Bureau (2025). The Number of Firms and Establishments, Employment, Annual Payroll, and Receipts by State, Industry, and Enterprise Employment Size: 2022 (Statistics of U.S. Businesses) (opens in a new tab) ↑
Google (2026). Guidelines for representing your business on Google (Google Business Profile Help) (opens in a new tab) ↑
National Restaurant Association (2024). National Statistics: Restaurant Industry Facts at a Glance (opens in a new tab) ↑
American Dental Association Health Policy Institute (2025). Dental Practice Research (opens in a new tab) ↑
U.S. Bureau of Labor Statistics (2026). Employer Costs for Employee Compensation, Table 4: private industry workers by occupational and industry group, June 2026 (opens in a new tab) ↑
Pew Research Center (2020). Most Americans don't answer cellphone calls from unknown numbers (opens in a new tab) ↑