Somewhere between location eight and location twenty, almost every healthcare roll-up has the same meeting. Phones ring out at lunch, new-patient calls go to voicemail after 5pm, and each office books appointments a little differently. Someone proposes a central call center. It is a reasonable idea, and for a decade it was the only one. Now there is a second option, and the two are worth comparing honestly.
Why Roll-Ups Centralize the Phones
The case for centralizing is the same whichever way you do it:
- Missed calls are missed revenue. A new patient who reaches voicemail usually calls the next practice on the search results page.
- Front-desk staff are pulled in two directions. The person checking in a patient at the counter is the same person who is supposed to answer line two.
- Every location books differently. Without a shared script, scheduling rules and new-patient handling drift from office to office.
- Leadership cannot see the funnel. When calls are handled locally, nobody at the platform knows how many came in, how many converted, or why.
The Central Call Center Model
A central call center moves inbound calls to a team of agents, either in-house or outsourced, who schedule into every location's PMS. Done well, it fixes coverage during business hours and makes scripting consistent. It also comes with costs that grow with the platform:
- Headcount scales with call volume. Every acquisition adds calls, so every acquisition adds agents.
- Agents need access to every system. A platform with five PMSs needs agents trained on five PMSs, each with its own scheduling rules.
- Turnover is high. Call center roles churn quickly, so training is never finished.
- After-hours is still expensive. Nights and weekends need either a second shift or an answering service that takes messages.
- Local knowledge gets lost. Agents a hundred miles away do not know which provider prefers which procedure, or that the parking lot is around back.
The AI Front Desk Model
An AI front desk answers every call, text and web inquiry, books directly into each location's PMS, and hands off to a person when the conversation needs one. With Samara, Operations Engine (AIT) runs scheduling, intake, reminders, recall and reviews on one playbook, and Rollup Engine (AIP) connects the platform's different EHRs and PMSs so that playbook works at every site.
Side-by-Side Comparison
| Factor | Central call center | AI front desk |
|---|---|---|
| Coverage | Staffed hours, plus answering service | 24/7, every channel |
| Peak volume | Hold queues on Monday mornings | Concurrent calls, no queue |
| Cost as you acquire | Rises with headcount | Rises with locations, not calls |
| Consistency | Depends on training and turnover | Same playbook on every call |
| New acquisition onboarding | Train agents on new PMS and local rules | Connect PMS, apply existing playbook |
| Complex or emotional calls | Strong | Hands off to a person |
| Reporting | Call logs, often manual tagging | Every interaction structured by location |
The Model That Works: AI First, People Where They Matter
This is not a choice between replacing people and keeping them. The platforms that get the most out of centralizing do it in layers:
- AI handles the volume. Booking, rescheduling, confirmations, directions, insurance questions and recall outreach, around the clock.
- A small central team handles exceptions. Billing disputes, upset patients, complex treatment questions and anything the AI routes to a person.
- Local staff get their counter back. The front desk in each office focuses on the patient standing in front of them.
A platform that already runs a call center does not need to tear it down. Putting AI in front of it shrinks the queue, covers nights and weekends, and lets the existing agents work on the calls that need judgment.
What to Ask Before You Decide
- What share of our new-patient calls go unanswered today, by location and by hour?
- How many agents will we need after the next five acquisitions?
- Can the model book directly into every PMS we run, or only some of them?
- How long does it take to bring a newly acquired location onto it?
- Will we be able to see conversion by location, source and call type?
Next Step
Run your own numbers with the ROI calculator, see how Samara works for private equity platforms, or book a demo to map your call flow across locations.
Frequently Asked Questions
Is a central call center or AI front desk better for a healthcare roll-up?
For most platforms, the best answer is both: AI handles routine scheduling and patient communication 24/7, and a small central team handles exceptions. Pure call centers get more expensive with each acquisition because headcount grows with call volume.
Can an AI front desk book into multiple PMSs?
Yes. Samara's Rollup Engine connects the different EHRs and PMSs a roll-up inherits, so the same scheduling playbook runs at every location without forcing a PMS migration.
What happens when a patient needs a person?
The AI hands the conversation to a staff member, either at the location or in a central team, with the context of the conversation so the patient does not have to repeat themselves.