How to Replace a Phone Tree in Healthcare: A Health System Guide

What You Need to Know

• Replace a phone tree in healthcare one call reason at a time: route it to AI agents, keep it with staff or retire the menu. Every path should end with someone who can finish the task.
• Audit every branch and count your calls before you change anything. Your lines may miss calls: a July 2026 VA review found that 45% of call attempts to specialty care lines at sampled facilities weren't tracked¹.
• Keep a human exit and accessible routes on every path, then switch over in phases. Compare results only after a stabilization window.

What does it take to replace a phone tree in a health system?

To replace a phone tree in healthcare, audit your current menu, give each call reason a path to AI agents or staff, then switch over in phases and measure the result. You can keep your interactive voice response (IVR) system (see our guide to healthcare IVR) and send some branches to AI agents, or retire the menu and let callers say what they need.

Either way, every path has to end with someone who can finish the task. Your own before-and-after numbers will be the main evidence that the change worked.

How do you audit your current phone tree and map call reasons?

Test-call every number and branch, then count why and when patients call.

Step 1: Audit every number and branch

Menus can send callers to staff who can't finish the task. VA's inspector general found that most sampled facilities' specialty care menus didn't route veterans directly to staff who could resolve their needs¹.

Call each number patients can find: main line, clinic and service-line numbers, after-hours lines, and numbers in directories and on your website. Press every option and submenu, noting dead ends, voicemail-only branches and branches where staff can't finish the caller's task.

Published numbers can fail callers. When VA's inspector general test-called specialty care clinic numbers listed in VA directories and websites, 36% of them led to misrouted or disconnected calls¹.

Check that each path is counted, because some VA clinics used shared lines and individual extensions that can't record call data¹.

Turn the inspector general's recommendations to VA into an audit checklist¹:

• Update and verify every published clinic number on a set schedule.
• Check at least once a year that each branch sends callers directly to the right clinic and supports first-call resolution.
• Set up lines so they collect call performance data.
• Name who monitors call data and how often.

As you test, log each path in a worksheet like this one, with a row for every branch:

Step 2: Map call reasons and volumes

Pull keypress counts for each option and call volume by day of week and hour. England's general practice guidance uses both to learn when people call and why².

On any line that can't report, tally a week of calls by reason to complete a list of call reasons ranked by volume for Step 3.

Should you keep your IVR and route to AI agents, or retire the menu?

Decide for each call reason. Keep your IVR and route some branches to AI agents, retire the menu or keep a branch with staff.

Step 3: Choose a path for each call reason

Keeping your IVR changes less at once. The menu still sorts every caller, but it sends only the branches you pick to AI voice agents. At one VA facility, a secondary prompt let callers who chose scheduling pick their specialty clinic, which the inspector general said "minimized transfers"¹.

Pilot a retired menu on one entry number first, because every call reason on that number moves to a new path at once. Without the menu, routing rules for spoken requests sort the calls, with the rules set during implementation. After go-live, keep running the Step 5 test calls on a schedule to catch misroutes.

Send each call reason where someone can finish it. Clinical questions need clinical staff, while scheduling that breaks the usual rules needs a scheduler who can make exceptions. In a VA study, none of the regional nurse triage centers could schedule patients directly, "limiting their ability to achieve first-call resolution"⁴.

Keep any remaining menu short and plain, even one that hands scheduling to AI patient scheduling. England's general practice guidance suggests a welcome message of 60 seconds or less, with options worded the way patients talk².

What has to stay in place, and what should you test before go-live?

Every path keeps three things: a way to reach staff, a Spanish route and access for TTY and relay callers. Test every path end to end before go-live.

Step 4: Keep escalation paths and access routes

Every branch, old or new, needs an exit to staff who can resolve the request. Write down where each escalation goes during and after hours: staff queues, the provider on call or an answering service.

Write voicemail rules that say who checks each box and how fast callers hear back. Three lower-complaint VA facilities expected staff to check and return voicemail within 24 hours¹.

Spanish speakers need equal service on every path, exits included. In a secret-shopper study of California safety-net behavioral health clinics, Spanish speakers had a harder time reaching live schedulers than English speakers⁵. The study didn't test phone menus⁵. A new phone path can close that gap or repeat it.

Check the new path and its vendor against these rules before launch:

• TTY and relay. ADA rules apply to a covered provider's automated phone system, including an IVR or voicemail³. The system must give effective real-time communication to TTY users and to callers using every FCC-approved form of relay, including internet-based relay³. Covered providers must also answer relay calls the same way they answer other calls³.
• Language and disability access. Section 1557 rules apply if your system receives federal financial assistance⁶. They require reasonable steps to give each caller with limited English proficiency meaningful access⁶. They also require communication with callers with disabilities to be as effective as with others⁶. The same ADA phone rules apply⁶.
• Interpreters. Section 1557 duties may include offering a qualified interpreter⁶. The rules build spoken language help around qualified interpreters and bilingual staff⁶. They bar requiring callers to bring or pay for their own interpreter, or relying on a minor child to interpret except as a temporary measure in an emergency⁶.
• Family members and other adults. Section 1557 rules bar relying on an adult who isn't a qualified interpreter, such as a family member, with two exceptions⁶. One is a temporary measure in an emergency while a qualified interpreter is found⁶. The other applies when a caller asks for that adult in private, with a qualified interpreter present⁶. The adult must agree⁶. The request must be documented and appropriate to the situation⁶.
• Written procedures. Section 1557 rules also require written procedures for language access and effective communication, plus accessible technology⁶. Update those procedures for the new phone path before go-live.
• Business associate agreement. HHS guidance treats a cloud vendor as your business associate if it creates, receives, maintains or transmits electronic protected health information for you⁷. Even a vendor that can't view the data counts, because HHS limits its conduit exception to transmission-only services⁷. Treat a vendor that processes live calls or keeps recordings or transcripts as handling patient information. Sign a BAA before it touches any patient information, including in testing⁷,⁸.
• Risk analysis. Because the HIPAA Security Rule requires a security risk analysis, add the new phone path to yours⁸.
• Phone numbers. If you also change carriers, the FCC says customers who switch providers in the same area can keep their number⁹. It also says not to cancel old service first⁹. Confirm toll-free and business lines with your carrier.
• California AI disclosure. California's generative AI law covers health facilities, clinics and physician practices in the state¹⁰. For AI-generated calls about a patient's clinical information, it requires a spoken disclaimer at the start and end, plus instructions for reaching a person¹⁰. The law excludes administrative matters such as scheduling and billing¹⁰.

Confirm with counsel whether and how each rule applies to you. Ask which ADA title covers your system. Ask how Section 1557 treats a Spanish-language AI path and where to hand off callers who need an interpreter. Ask about consent rules for recorded calls in your states. Then ask which call reasons California's law may reach and whether your other states have AI disclosure rules.

Step 5: Test before go-live

Test every path end to end, the way patients will use it².

Run relay and TTY tests with your compliance team and counsel, covering your whole phone path, including any part a vendor runs.

How do you phase the cutover and measure the result?

Start with one or two call reasons or one entry number while the old path still runs. Compare results after a stabilization window.

Step 6: Phase the cutover

Start small and widen only once the first phase holds steady. Pick call reasons that are common and low risk, such as confirmations or rescheduling, because problems show up quickly and stay away from clinical calls. Meanwhile, keep the old path running for anything not yet moved. England's general practice guidance expects practices to adjust a new path after launch².

Tell patients and referring offices before the change. Maine's Medicaid agency told providers in advance that a virtual assistant would replace its phone menus¹².

Step 7: Measure before and after

Set a baseline for the four measures England's guidance names². Add transfers, repeat calls and voicemail volume if Step 1 showed your lines can count them. Your own numbers matter because we found no peer-reviewed study of a health system replacing its phone tree with AI agents.

Compare results only after a stabilization window. Key informants at three VA primary care sites said patient dissatisfaction seemed highest right after their switch to a call center model⁴. Set the window's length before go-live, then compare like periods with the same weeks, lines and call reasons, leaving go-live week out.

Count callers as well as calls where you can, because one patient who tries three times shows up as three missed calls².

Healthcare call center metrics explains how to define each measure, while our guides to first call resolution, call abandonment rate and average handle time go deeper.

How do Commure AI Call Center Agents work with your phone tree?

Commure AI Call Center Agents support both paths in a phone tree replacement. They can operate within your existing IVR or manage call flows end to end once the menu is retired. Either way, calls route through your existing telephony with no number change.

The call reasons from your audit become the workflows configured during scoping. The agents ingest your SOPs, scripts, scheduling rules and EHR configuration in Epic, MEDITECH, athenahealth, eClinicalWorks, ModMed or AdvancedMD. Structured scoping sessions capture the remaining details.

The agents finish routine requests on the call, 24/7/365, in English or Spanish: FAQs, scheduling, rescheduling, cancellations, confirmations and intake. Commure reports typical results of a 30%+ reduction in inbound calls handled by your team.

The escalation routes you define become routing rules: calls that need a person reach staff by warm transfer, routed by configured intent rules. Complex or non-standard requests go to staff, an answering service or a follow-up workflow. The agents log each message as a structured task.

Deployment typically takes about four weeks, covering workflow scoping, configuration, testing, UAT and a controlled production rollout. Your phased menu cutover runs on its own timeline.

After go-live, every call is recorded, transcribed and scored. A real-time dashboard, reviewed weekly, tracks resolution rate, scheduling success and abandonment for your before-and-after comparison.

To see your call reasons first, request a complimentary call center health analysis. It breaks down a week of your calls by type, length and outcome, using transcripts and call data you share under a signed BAA.

How should a health system plan its phone tree replacement?

Plan a phone tree replacement in the same order as the steps, starting with an inventory and ending by naming an owner.

1. List every entry number and branch. Include directory and website listings.
2. Pull call data. Take 90 days of keypress counts and volume by day and hour, plus a one-week manual tally on lines that can't report. If you don't have a call-reason breakdown yet, request a complimentary call center health analysis.
3. Mark each call reason. Label it "keep with staff," "route from IVR to AI agents" or "retire menu."
4. Write escalation and voicemail rules. Cover both during and after hours.
5. Book test calls. Cover each language you serve, interpreter handoffs, TTY and each relay type. Bring in compliance and counsel on ADA, Section 1557, BAA, HIPAA risk analysis, recording consent and state AI disclosure questions.
6. Pick the first phase. Choose one or two call reasons or one entry number. Tell patients and referring offices before go-live, for example through your patient engagement software.
7. Set the baseline and stabilization window. Fix baseline weeks, metrics and how long the new path runs before you compare.
8. Name an owner. Decide who reviews menus and call data, and how often.