Key takeaways
- As a group grows, phone access becomes uneven: each location answers differently, with its own staff, hours and habits.
- A shared call center fixes consistency but often loses local knowledge: agents juggle the rules of dozens of sites and end up taking messages.
- The model that works is one entry point with location-specific rules: one number for patients, each site's providers, hours and visit types applied on every call.
- Standardize what protects the patient and the group (urgent-call protocol, data handling, definitions). Keep local what makes each site work (providers, schedules, prep, directions).
- Compare locations on the same few metrics: missed calls, time to answer, requests completed during the call, transfers, callbacks left at the end of the day.
- Roll out one site at a time, starting with a pilot, as Retinax did across its ophthalmology centers.
Monday, 8:15 a.m. At one of your locations, two front desk staff are answering phones while patients line up at the counter. Across town, a newly acquired practice still sends every call to a voicemail that fills up by noon. At headquarters, nobody can say how many calls the group missed last week, because each site counts them differently, if it counts them at all.
This is the usual state of patient calls in a multi-location medical group or an MSO. This guide is for COOs, operations directors and patient access leaders who want every location to be reachable, without building a call center that knows none of them.
Why phone access breaks as a group grows
Phone access breaks because each site staffs, books and escalates calls in its own way, and nobody measures the result the same way. The problems are predictable:
- Uneven staffing. The busiest site and the quietest one get the same number of people on the phone, or the busiest one gets fewer because the front desk is also checking patients in.
- Diverging protocols. Each site books new patients, handles cancellations and escalates urgent calls in its own way. Patients get a different answer depending on the number they dial.
- Acquisitions. Every new practice arrives with its own phone system, its own scheduling software and its own way of working.
- No shared measure. Without the same definitions across sites, a missed call at one location and a voicemail at another don't show up in the same report.
Hiring more front desk staff at every site treats the symptom. The phone volume keeps growing with each new location, and so does the gap between the sites that cope and the ones that don't.
Centralizing calls: what a shared call center gets right, and what it loses
A shared call center gives patients one number and pools staff, but it loses each site's rules, so specific requests still end as messages for the local team.
The classic answer is a central patient access center: one team that answers calls for every location.
What it gets right. Patients get one number. Staffing is pooled, so a quiet site no longer has idle phone staff while a busy one drowns. Management finally sees the whole group's call volume in one place.
What it loses. The agents don't work at any of the locations. They have to keep in mind which provider practices where, on which days, for which visit types, with which preparation, at dozens of sites. In practice, the more specific a site's rules, the more often the call ends as a message for the local team, the same limit we describe in AI receptionist vs. answering service. Queues come back at peak hours, and every new site adds rules to memorize.
Centralization solves access. It rarely solves finishing the request.
One entry point, location-specific rules
The model that works gives patients a single entry point and applies each location's rules automatically on every call.
An AI voice agent connected to each site's scheduling software can do this. Patients call one number and still reach the right provider. The agent knows which providers practice at which location and the hours of each site, books patients where it suits them, and applies a common protocol for the whole group. Groups can share rules across locations or adapt them site by site. It's how we work with multi-location groups, and with hospitals that route many departments through one number.
Take a group with three locations:
- Location A offers early morning slots and the only MRI in the group.
- Location B sees new patients only on Tuesdays and Thursdays.
- Location C joined the group last month and has two providers, both fully booked on Mondays.
A patient who calls the group's number for a first visit is offered a Tuesday at Location B, or the nearest slot elsewhere if she can't wait. A patient who needs an MRI is booked at Location A, with the preparation instructions for that site. The urgent-call protocol is the same everywhere. Your team sees every call and booking across all sites in one dashboard.

You don't have to change your phone numbers. Each site's existing number can be forwarded to the same entry point, so patients keep dialing the number they know, and a group-wide number can be added alongside it.
If you already run a patient access center, keep it. The agent can take the first line and complete routine requests, and your central team handles what needs a person: complex scheduling, sensitive calls, follow-ups.
What to standardize across sites, and what to keep local
Standardize what a patient would expect to be identical at every location, and keep local what depends on the site.
| Standardize across the group | Keep local to each site |
|---|---|
| The urgent-call protocol and its red flags (see our guide to after-hours patient calls) | Providers, their schedules and the visit types each one sees |
| How new patients are defined and booked | Opening hours, holidays and closures |
| Confirmation and reminder rules | Visit durations and preparation instructions |
| Data handling, recordings and the BAA | Address, parking and access instructions |
| Definitions of the metrics you report on | Local referral partners and imaging or lab services |
| The tone and the way the group introduces itself | The services and equipment each site offers |
If the right answer depends on the site, make sure the system knows it. A rule that lives only in one front desk coordinator's head is the first one to break when that person is out.
The metrics to compare locations
Five metrics, measured the same way at every site, are enough to compare locations and find the ones that need attention.
- Missed and abandoned calls: calls that never reached anyone, per site and per hour of the day.
- Time to answer: how long patients wait before someone, or something, picks up.
- Requests completed during the call: the share of calls that end with a booked, moved or cancelled appointment, or an answered question, with no callback.
- Transfers to staff, and why: urgent calls, complex requests, patients asking for a person. The reasons tell you where your rules need work.
- Callbacks left at the end of the day: what each site's team still has to do once the phones go quiet.
Track them weekly for every location with the same definitions. The sites that fall behind are usually the ones where local rules were never written down.
What changes for front desk teams
Front desk teams stop spending their day on the phone and get their time back for the patients in front of them and the requests that need a person.
That shift only works if the local teams are part of it. They know the rules that were never written down, the providers' habits and the patients who always call twice. Ask them to write their site's rules, review the first weeks of calls with them, and let them adjust what the agent does. At DAG Dental, "our teams keep the judgement calls," says its Chief Operating Officer.
HIPAA in a multi-entity group
In a group or an MSO, the practices are often separate covered entities, so check that the BAA covers every practice whose patients the agent talks to.
Depending on how your group is structured, the MSO may sign on behalf of its practices, or each practice may need its own agreement. Settle this with your compliance team before the first site goes live, not after the tenth. Our HIPAA checklist for AI voice agents lists the other questions to ask a vendor.
Rolling it out site by site
Start with one pilot site, write its rules, connect its software, then extend site by site with the same metrics.
- Start with a pilot site, ideally a busy one with well-documented rules.
- Write the group protocol and each site's rules with the local teams: providers, visit types, durations, preparation, red flags.
- Connect each site's scheduling software. After acquisitions, locations often run different systems. Check that each one is supported before you plan its go-live.
- Go live, then review the first weeks of calls with the site's team, and adjust the rules.
- Extend site by site, using the same metrics to compare each new location with the pilot.
On pricing, vendors bill per location, per provider, per call or per minute. Ask how the price moves when you add a site, since that's the question that matters most to a growing group.
Retinax, an ophthalmology network in France with five sites, around forty practitioners and nearly 2,500 patients a week, started with a single practice. It now has 100% of its calls handled across all of its centers. National groups run their scheduling on Vocca the same way, including DAG Dental across its 37 practices in the United States. "We tested a handful of AI tools across different offices. Vocca was the clear winner, and we rolled it out across the group," says Opal Anderson, its Chief Operating Officer.
Planning a rollout across your locations? Book a demo with the rules of two of your sites in hand: we'll show you how the same call is handled at each one.
FAQ
How can an MSO automate patient calls across all its practices?
Give patients one entry point, then connect it to each practice's scheduling software with that practice's rules: providers, hours, visit types, preparation. An AI voice agent applies those rules on every call and books, moves or cancels appointments directly, while a common protocol handles urgent calls for the whole group.
How do large physician groups reduce abandoned calls and hold times?
By answering every call instantly instead of adding people at each site. An AI voice agent picks up with no queue, handles as many calls as needed at once and completes routine requests during the call. Measuring missed calls and time to answer per site, with the same definitions, shows where the problem was.
Can one AI voice agent handle different rules for each location?
Yes. It knows which providers practice at which location, the hours of each site and the visit types each one offers, and books patients at the right place. Groups can share some rules across locations and adapt others site by site.
Do our locations have to change their phone numbers?
No. Each site's existing number can be forwarded to the same entry point, so patients keep calling the number they know. A group-wide number can be added for new patients and marketing.
How do you scale front desk operations without hiring for every new site?
Separate the phone from the front desk. When routine calls are completed during the call, the team at each site keeps its time for patients in front of it and for the requests that need a person. A new location then needs its rules written and its software connected, not a new phone team.







