Skip to content

Reduce Call Center Waste with AI: Insights from 10,000 Calls

Dr. Shahinaz Soliman, M.D. Apr 23, 2026 11:51:00 AM
AI-powered call center automation for medical practices

Quick Answer: External provider calls — from other doctors' offices, pharmacies, hospitals, and insurers — represent a hidden call center burden that most large practices manage manually. CallMyDoc is currently handling 8,000+ external provider calls per month at a 1,500+ provider group on athenahealth and Five9, with that number climbing as additional intent types go live. Analysis of 10,000+ calls from the same organization shows the long-term ceiling: 85.8% of external provider calls can be handled without a live agent — 23.3% fully self-service and 62.4% through automated athenahealth case creation.

The Call Center Problem That Isn't About Patients

Every conversation about medical practice call management focuses on patients: patients calling for appointments, refills, test results, after-hours advice. And that's appropriate — patient call volume is enormous, and managing it well directly affects access, outcomes, and revenue.

But there's a second category of calls that large medical practices field every day, and it almost never appears in discussions of call center optimization: external provider calls.

Other doctors' offices calling to confirm a fax number before sending a referral. Pharmacies calling about a prescription question. Home health agencies calling to report a discharge. Imaging centers calling because an order is unclear. Insurance companies calling to confirm a prior authorization. Hospitals calling with a patient update.

In a small practice, these calls are a modest background noise. In a multi-specialty group with hundreds of providers, they become a dedicated queue — a parallel call center problem running alongside the patient-facing one, consuming agent time, creating delays for external providers trying to coordinate care, and generating a flood of manual work that flows into the EHR only because a human typed it in.

In 2026, that manual layer is no longer necessary for most of these calls — and at one of the largest ambulatory groups in Florida, it's already being eliminated, one intent type at a time.

What External Provider Calls Actually Look Like at Scale

CallMyDoc is currently deployed at a 1,500+ provider group running athenahealth and a Five9 contact center across Florida, handling external provider calls in production. As of early 2026, the system is processing 8,000+ external provider calls per month — and that number continues to grow as additional intent types are enabled and validated on live traffic.

The external provider call center at this organization receives approximately 30,000 calls per month total. To inform how the AI deployment was designed and sequenced, CallMyDoc analyzed 93,963 call transcriptions across two periods (August 2024 and December 2025–February 2026), identifying 10,114 external provider calls representing 10.8% of total inbound volume. That analysis established the intent taxonomy and automation ceiling that now guides the live rollout.

Who is calling, and how often?

Caller Type % of External Provider Calls
Vendor / Sales Rep20.7%
Insurance Representative18.1%
Pharmacy14.9%
Home Health Agency13.6%
Doctor / Provider Office10.8%
Medical Supplies Representative10.7%
Imaging Center4.4%
Physical Therapy2.2%
Hospital2.0%
Lab2.0%

The most striking finding: vendor and sales calls represent the single largest external caller category — 20.7% of volume. These are pharmaceutical reps, medical supply companies, and IT vendors. They're consuming a meaningful share of your external provider queue capacity.

The Six Things External Providers Actually Call About

Across 10,114 analyzed calls, 35 distinct intent categories were identified. The top seven account for 73% of all external provider call volume:

Intent % of Calls Est. Monthly Volume
Requesting Medical Records13.4%~273
Vendor / Sales Call12.9%~335
Confirming Authorization11.4%~273
Order Clarification9.6%~208
Request Orders9.0%~226
Message for Provider7.1%~187
Confirm Fax Number6.7%~150

Look at "Confirm Fax Number" — the seventh most common intent, 150+ calls per month, accounting for nearly 7% of external provider volume. These are calls from other offices verifying a fax number before sending a referral or records request. The entire interaction takes under 90 seconds when handled by a live agent. It requires zero clinical judgment. And yet it occupies agent time that could be spent on actual care coordination.

"Confirming Authorization" at 11.4% — 273 calls per month — follows a similar pattern. An insurance company or external provider is calling to confirm a prior authorization is in place. The information exists in athenahealth. A human looks it up and reads it back. That's the entire interaction.

At 30,000 calls per month total, even the low-percentage intents represent hundreds of agent-hours annually.

Three Tiers of Automation: Not All Calls Are the Same

The useful framework for external provider call automation isn't a binary "automated or not" — it's three tiers based on what the call actually requires.

Tier 1: Full Self-Service (23.3% of calls)

These calls can be fully resolved by AI with no human involvement. The caller asks a question, gets a verified answer, and hangs up. No case is created, no staff action is required, no callback is needed.

At the 1,500+ provider group analyzed, Tier 1 accounts for roughly 2,360 calls out of every 10,000 external provider calls — and approximately 7,000 per month at full queue volume.

What Tier 1 looks like in practice:

  • Fax and directory lookups — "What's the fax number for Dr. Martinez's cardiology office?" AI looks it up in the provider directory, reads it back, confirms accuracy, and ends the call.
  • Vendor / sales screening — The AI identifies vendor and sales callers (135+ known patterns) and routes them to a general voicemail or provides a standard response, without consuming live agent time.
  • Lab and imaging result availability checks — "Are the results in yet for the patient I referred last week?" AI checks the chart and confirms.
  • Appointment verification for care coordinators — Home health agencies confirming appointment details for a patient they're managing.

None of these interactions require a clinical decision. All require a verified answer from a data source the AI already has access to.

Tier 2: Automated Intake and Routing (62.4% of calls)

These calls can't be fully resolved by AI — they require a human to take an action. But the AI can collect all the necessary information, verify the patient, create a structured athenahealth case with the correct case type and routing, and get that work into the right provider's queue — automatically, before any staff member is involved.

The staff action still happens. But instead of starting from a phone call they need to decode and manually document, staff start from a structured, complete case with all required fields filled in, already routed to the right team.

Tier 2 accounts for 62.4% of external provider calls — the largest single category. At 30,000 calls per month, that's approximately 18,720 athenahealth cases created, routed, and queued without manual intake. At the current live deployment, a significant and growing share of these cases are already being created automatically. The time from call start to case creation: under two minutes.

What Tier 2 looks like in practice:

  • Authorization management (20.5% of external calls) — Confirming auth status, logging auth requests, tracking referral denials. The AI collects the patient ID, the auth details, and creates the correctly typed case. Staff sees a complete record to act on.
  • Document management (17.9%) — Medical records requests, discharge notifications, hospital status updates. AI identifies the patient, logs the request with the caller's information, and routes to the appropriate staff or department.
  • Order management (9.0%) — Requests for new orders from labs, imaging, home health, or other providers. AI collects the requesting party, the patient, and the specific order need, then creates the case for the ordering provider.
  • Clinical messaging (9.4%) — Messages for specific providers, callback requests, medical clearance requests. AI identifies the target provider, captures the message, and routes directly to their queue.
  • Prescription management (5.7%) — Refill requests, prescription issues, medication questions from pharmacies. AI documents the request with all required detail and routes to the prescribing provider.

Tier 3: Always Requires Human (14.2% of calls)

Some external provider calls genuinely require clinical judgment, real-time dialogue, or complex decision-making that AI cannot safely replicate. These should go to a live agent — and in a well-designed system, that's exactly where they go, instantly, with a full context summary already prepared.

Order clarification (9.6% of external volume) is the primary Tier 3 category — these are calls where an imaging center or lab has a question about an order that requires back-and-forth clinical dialogue with the ordering provider. No amount of structured intake replaces that conversation.

The key insight: the 14.2% that always requires a human gets better service too, because agents who are no longer handling fax confirmations and vendor screener calls have actual capacity for the calls that need them.

Why This Requires Deep athenahealth Integration

The automation potential described above only exists if the AI can act on what it hears — not just collect it. That's the gap where most call automation solutions fall short for external provider workflows.

Consider a simple case: a home health agency calls to report that a patient was discharged from the hospital and wants to ensure continuity of care. The AI needs to:

  1. Identify the caller as a home health representative (not a patient)
  2. Identify the specific patient being discussed
  3. Collect the relevant discharge details
  4. Create an athenahealth patient case with the correct document subclass (discharge notification)
  5. Route it to the appropriate provider based on PCP assignment or specialty
  6. Confirm to the caller that the case has been created and will be reviewed

Steps 4 and 5 require direct athenahealth API access — not just reading data, but writing structured case records with the correct categorization and routing metadata. CallMyDoc's athenahealth integration supports 12 case type categories, automatic provider cascade routing, and required field validation — the same infrastructure used for patient-facing call workflows, extended to the external provider queue.

The same integration that routes a patient's refill request to the correct prescribing provider routes an external provider's authorization inquiry to the correct auth coordinator. The logic is the same; the caller type and case type differ.

The Live Agent Integration: Five9 as the Safety Net, Not the Bottleneck

A critical design principle in external provider call automation: the live agent queue is always the fallback, and it's always available. No caller is ever stuck in an AI loop — human escalation detection fires at multiple points in every conversation, and any call can route to the live agent queue at any moment.

When the AI escalates a call, it doesn't just transfer — it packages a complete handoff summary: the caller identity, the call intent, what was collected, what failed, and why the escalation occurred. The live agent starts with full context instead of asking the caller to start over.

At the organization analyzed, this architecture means Five9 agents are engaged for genuinely complex calls that require clinical judgment, instead of spending their time confirming fax numbers and logging vendor messages.

What the Data Means for Practice Administrators and Executives

For a practice administrator managing an external provider call center, the operational picture at the live deployment is concrete: 8,000+ calls per month are already being handled without live agent involvement — and the number grows each month as additional intent types are validated and enabled. At full 85.8% containment across 30,000 calls/month, 25,740 calls per month would be handled by AI. The remaining calls — the order clarifications, complex clinical dialogues, and explicit human requests — receive faster, more focused agent attention because capacity isn't consumed by fax confirmations and vendor screening.

For a CIO evaluating an AI call platform, the technical question is integration depth. Can the system write structured records to athenahealth — not just collect transcriptions, but create correctly typed cases with the right fields, routing, and documentation? Can it work alongside an existing Five9 deployment as a smart front end, not a replacement? CallMyDoc's AI platform is built specifically for athenahealth-integrated ambulatory practices, with 51 pre-built tools covering the full range of external provider and patient-facing workflows.

For a CMO focused on care coordination quality, the case for automation isn't just efficiency — it's accuracy. A case created by a human agent transcribing a phone call is only as accurate as that transcription. A case created by an AI that collected structured data from the caller, verified the patient against the chart, and applied the correct case type and routing is complete, consistent, and immediately actionable.

A Phased Approach: Starting with the Highest-ROI Intents

Enterprise implementations of external provider call automation don't go live with all 35 intent categories simultaneously. The practical approach is sequential: enable the simplest, lowest-risk intents first, validate performance on live calls, then expand.

The recommended sequence for a Five9 + athenahealth environment:

  1. Vendor screening — Immediate ROI, zero clinical risk. Identify vendor and sales callers and route to voicemail. No patient data involved, no athenahealth write-back required.
  2. Directory lookups — Fax numbers, phone numbers, NPI lookups. Low risk, no patient authentication required. Every successful lookup is a call the live agent queue doesn't see.
  3. Non-patient case creation — Messages from vendors, insurers, and general inquiries. Structured intake and routing, but no patient ID required.
  4. Patient-related case creation — Authorization requests, medical records, refill requests, discharge notifications. Full patient identification and athenahealth write-back. The highest-volume Tier 2 workflows.
  5. Status checks — Referral status, authorization status, appointment confirmation. These require careful role-based access controls to ensure external providers only receive appropriate information.

This sequence allows each intent to be tested independently on a dedicated test number, validated by the practice, and enabled for live callers only after sign-off. If a specific intent type needs adjustment, it can be disabled without affecting any other intent. The live agent queue remains the fallback at every stage.

The Bottom Line

External provider calls are a significant, underexamined operational cost for large medical practices. For most organizations, every fax confirmation, authorization check, and vendor call is being handled by a live agent today — not because it requires human judgment, but because there was no alternative.

That alternative now exists and is running in production. At a 1,500+ provider Florida-based group on athenahealth and Five9, CallMyDoc is handling 8,000+ external provider calls per month — a number that grows each month as the rollout expands across intent types. The call analysis covering 10,000+ real calls establishes the long-term ceiling: 85.8% of the 30,000-call monthly queue can ultimately be handled without a live agent.

The 14.2% that genuinely requires human expertise gets better service as a result — because agents are no longer buried in work that an AI can handle in under two minutes.

To understand how this applies to your organization's specific external provider call mix, request a workflow analysis or see how CallMyDoc compares to traditional call center approaches.


Frequently Asked Questions

What are external provider calls in a medical practice?

External provider calls are inbound calls from other healthcare entities — specialist offices, pharmacies, home health agencies, hospitals, imaging centers, insurance companies, and labs — who need to exchange clinical or administrative information with your practice. Unlike patient calls, these calls often involve care coordination tasks such as referral management, authorization confirmations, medical records requests, and order clarification.

What percentage of external provider calls can be automated?

CallMyDoc is currently handling 8,000+ external provider calls per month at a 1,500+ provider group, with that number growing as additional intent types go live. Analysis of 10,000+ calls from the same organization shows the long-term ceiling: 85.8% can be handled without a live agent — 23.3% fully self-service and 62.4% through automated athenahealth case creation. Only 14.2% — primarily order clarifications requiring clinical dialogue — always require a live agent.

What are the most common external provider call types?

The top external provider call intents by volume are: medical records requests (13.4%), vendor and sales calls (12.9%), authorization confirmations (11.4%), order clarifications (9.6%), order requests (9.0%), provider messages (7.1%), and fax number confirmations (6.7%). Together these seven categories represent approximately 73% of all external provider call volume.

How does external provider call automation integrate with athenahealth?

Full automation requires direct athenahealth write-back capability — the AI must create structured patient cases with the correct document subclass, required fields, and routing metadata, not just collect transcriptions. CallMyDoc's athenahealth integration supports 12 case type categories, automatic provider cascade routing, patient identification and disambiguation, and real-time case creation via the athenahealth API. This is the same integration layer used for patient-facing call workflows.

What happens when the AI can't handle an external provider call?

Every call has a live agent escalation path available at any point. When the AI cannot classify intent with sufficient confidence, cannot identify the patient, or detects that the caller explicitly wants to speak with a person, the call transfers to the live agent queue with a full context summary — caller identity, call intent, what was collected, and why escalation occurred. The live agent starts with complete information rather than asking the caller to start over.

Does external provider call automation work alongside Five9?

Yes. CallMyDoc is designed as an AI front end to the existing contact center infrastructure, not a replacement for it. The AI handles the high-volume, structured calls that don't require live agents, and routes the remaining calls to Five9 with a full handoff package. The Five9 agent queue processes fewer calls but focuses on the calls that genuinely require human judgment.