Key takeaways
- Centralizing phones pools staff across sites, which handles peaks better and frees each site's desk for patients in the building.
- The main risks are lost local knowledge, wrong-site bookings and clinical calls stuck in a scheduling queue.
- Before go-live, every site needs the same booking rules, a shared script library, a site directory and a direct route to each site's nurses.
- Roll out one site and one call type at a time, and report metrics by site so problems are not hidden in group averages.
Why more practices face this decision
Fewer physicians work in small independent offices than a decade ago. The share of US physicians working in private practices fell from 60.1% in 2012 to 42.2% in 2024[1], and the share in hospital-owned practices rose to 34.5%[2]. In 2024, 6.5% of physicians described their practice as private equity-owned[3]. Dentistry is moving the same way: about one in six US dentists (17%) were affiliated with a dental support organization in 2025[4].
Source: American Medical Association, 2024[1]
Show the data
| Item | Value |
|---|---|
| 2012 | 60.1% |
| 2024 | 42.2% |
When separate offices join a larger group, each usually keeps its own phone setup at first: its own number, its own receptionists and its own habits. Sooner or later someone asks whether one central team could answer for all of them. The answer can be yes, but only if the groundwork is in place.
What a central team usually handles
- Scheduling, rescheduling and cancellations for every site.
- New-patient intake calls and insurance questions before the first visit.
- Recall and reminder follow-up, and filling cancellations across sites.
- Overflow from site desks when local lines are busy, and lunch cover.
- Referral intake from outside offices.
Clinical calls are the main exception. Most groups route symptom calls, refills needing a clinical decision and results questions to each site's nurses, or to a central nurse team working from shared protocols, rather than to schedulers.
Benefits, risks and how to manage them
| Benefit | Matching risk | How to manage it |
|---|---|---|
| Pooled staff handle peaks better than several small desks | Callers lose the familiar voice of their local office | Greet with the site name; keep some local staff on site lines |
| Site desks focus on patients in the building | Desks and the central team blame each other for errors | Shared message standards and a daily huddle |
| One way of booking across all sites | Booking rules differ by provider and site | One rules library, kept current by a named owner |
| Open slots at one site offered to callers from another | Patients booked at the wrong location | Read back site address and provider at every booking |
| Better data on call reasons and outcomes | Problems hidden in group-wide averages | Report every metric by site |
| Easier training and quality checks | Local knowledge lost (parking, entrances, quirks) | A site directory with the details callers ask about |
What must be shared before go-live
One booking rules library
For each provider: visit types, lengths, new-patient limits, age limits, procedures they do not perform, and which sites they work at on which days.
One script library
Greetings that name the site, the emergency instruction, hold and transfer lines, new-patient questions and the escalation list for red-flag symptoms.
A site directory
Address, entrance, parking, accessibility, hours, holiday closures, fax number, insurance plans accepted, and the direct line to each site's nurse.
Shared systems access
Every central scheduler needs to see every site's schedule in one place and book directly, not by calling the site.
Clinical escalation routes
A direct, tested way to reach each site's nurse or the central nurse team, with a fallback if nobody answers.
Message standards
Who owns each message type at each site, how messages are sent, and the response time.
If schedulers have to phone a site to check whether a provider takes a visit type, the central team will be slower than the local desk it replaced. Fix the rules library first.
Systems: the hidden obstacle
Groups formed by acquisition often run more than one practice management or EHR system. Fragmentation is common in smaller practices: in 2024, only 32% of solo-practice physicians used an EHR from one of the five market-leading developers, compared with 90% of physicians in practices with more than 50 physicians[5]. A central team that has to log into three systems to find an open slot will not deliver the promised speed.
If systems cannot be unified before centralizing, start with the sites that already share a system, and keep the others local until they migrate.
Sizing the central team
Pooling is the main efficiency gain. Several small desks each have to cover their own peak; a combined team covers the combined peak, which is usually smaller than the sum of the individual peaks because sites do not all spike at the same minute.
| Site | Example calls in busiest hour | Example staff needed if separate |
|---|---|---|
| Site A | 30 | 3 |
| Site B | 22 | 2 to 3 |
| Site C | 15 | 2 |
| Combined, busiest hour for the group | 58 | 5 to 6 in one pool |
Example (fictional): separately, the three sites need seven or eight people on phones at their peaks. Pooled, the group's busiest hour needs five to six, because Site C peaks later than the others. The difference can staff a nurse line or cover breaks.
Language access across sites
Different sites often serve different communities. Central teams can staff bilingual schedulers more efficiently than each site can alone, but the obligation does not change: under Section 1557 rules, when interpretation is required, a covered entity must offer a qualified interpreter[6]. Record each patient's preferred language in the shared system and route callers who choose a language option to the right people.
In-house team or outsourced center
Some groups hire an outside patient access vendor rather than building a team. That can be quicker, but the vendor will handle protected health information, so HIPAA requires satisfactory assurance in a business associate agreement that it will safeguard that information[7]. Ask the same questions you would ask an answering service: who trains the agents, how scripts and booking rules are kept current, how clinical calls are escalated, and what reports you receive by site.
Bringing site staff along
The biggest obstacle to centralizing is often not technology but the people at each site. Long-serving receptionists know patients by voice and worry that a central team will get things wrong, or that their own jobs will go. Address both early and honestly.
- Explain what changes for site staff: fewer calls, more time for patients at the counter, and fewer interruptions during check-in.
- Say plainly whether roles will change and how. Uncertainty drives people to leave before any decision is made.
- Invite experienced site receptionists to help write the booking rules and site directory. Some may want to join the central team.
- Give each site a named contact in the central team for problems, rather than a general inbox.
- Share the by-site metrics with site staff every week during the rollout.
Keeping the local voice
Patients choose a local office and expect to reach it. Keep each site's phone number, greet callers with the site's name, and let central staff see the site directory on screen so they can answer local questions about parking or entrances. Where it fits, assign central schedulers to a regular set of sites so they learn the providers and the quirks. Done this way, many patients will not notice the change except that the phone is answered faster.
A phased rollout
- Pick a pilot site with a willing manager and a shared scheduling system.
- Start with overflow only: the central team answers calls the site cannot reach in a set time.
- Move scheduling for that site to the central team once overflow runs smoothly.
- Add sites one at a time, each with a site walk-through for the central staff.
- Bring in recall and referral intake after scheduling is stable.
- Review clinical routing after each site joins.
Metrics to report by site
- Answer speed and abandoned calls in each site's busiest hours.
- Bookings made at the wrong site or with the wrong provider or visit type.
- Same-day completion of callbacks and messages.
- Site staff and patient feedback, collected the same way at each site.
Related guides: plan the groups and fallbacks with call routing, compare a dedicated phone team with the front desk, and decide how nights and weekends are covered in answering service vs in-house after-hours coverage. For outsourced options, start with how medical answering services work.
Example: a three-site dental group
Example (fictional): a dental group with three offices on one practice management system moved hygiene scheduling and recall to a four-person central team, while each office kept a front-desk person for check-in, treatment-plan conversations and dental emergencies. The first month brought several wrong-office bookings, so the team added a closing read-back of the office address and dentist's name. Hygiene cancellations at one office began to be filled from the waiting lists of the other two, and each office's desk had more time for patients in the chair.
Frequently asked questions
What is a centralized scheduling call center?
A single team that answers scheduling and related calls for every location in a group, usually with access to every site's schedule, while site desks focus on patients in the building.
Should clinical calls go to the central team?
Usually not to schedulers. Route symptom and clinical calls to each site's nurses or to a central nurse team working from shared, provider-approved protocols.
How do you avoid booking patients at the wrong location?
Greet with the site name, keep a clear site directory, and read back the address, provider and time at the end of every booking.
Is outsourcing a central call center HIPAA compliant?
It can be, if the vendor signs a business associate agreement giving satisfactory assurance it will safeguard protected health information, and your policies and checks cover how it handles calls.
References
American Medical Association (2024). Physician Practice Benchmark Survey (opens in a new tab) โ
American Medical Association (2024). Physician Practice Characteristics in 2024: Private Practices Account for Less Than Half of Physicians in Most Specialties (Policy Research Perspectives) (opens in a new tab) โ
American Medical Association (2024). Physician Practice Characteristics in 2024: Private Practices Account for Less Than Half of Physicians in Most Specialties (Policy Research Perspectives) (opens in a new tab) โ
American Dental Association Health Policy Institute (2025). Dental Practice Research (FAQs) (opens in a new tab) โ
Office of the National Coordinator for Health IT (ASTP/ONC), HHS (2024). Office-based Physician Electronic Health Record Adoption, 2008-2024 (ONC Data Brief) (opens in a new tab) โ
Legal Information Institute, Cornell Law School (Electronic Code of Federal Regulations text) (current). 45 CFR ยง 92.201 - Meaningful access for individuals with limited English proficiency (opens in a new tab) โ
Legal Information Institute, Cornell Law School (Electronic Code of Federal Regulations text) (current). 45 CFR ยง 164.502 - Uses and disclosures of protected health information: General rules (opens in a new tab) โ