Routing requests in a multi provider practice
In a practice with several providers or locations, route each request by what the patient needs rather than which name they picked, using one written table that says who handles each request type, how fast, and who covers when they are out. Your phone tree, web forms, chat and any AI receptionist should all follow that same table.
Why requests get lost in bigger practices
A solo practice has one inbox and one front desk. Add providers, subspecialties and locations, and every request has to find its way to the right person. That is where response times quietly stretch from minutes to days.
The usual failures:
- A patient picks the wrong provider, such as a spine surgeon for a hand problem, and the request is bounced between teams
- Requests go to one provider's medical assistant, who is on vacation this week
- Each location has its own inbox, and the form sends everything to the first one
- A new provider joined months ago but is missing from the forms and phone menu
- Referrals from other offices land at the wrong location
- Every tool routes differently: forms to one inbox, chat to another, voicemail to a third
- Providers accept different insurance plans or age groups, and nobody checks before booking
Each handoff adds delay, and each delay is a chance for the patient to book elsewhere.
Build one routing table
Write down, in one place, where every kind of request goes. For each request type, list who handles it by team or role, the response target, the backup, and the channels it can arrive through.
A hypothetical orthopedic group might start like this:
- New patient, knee or hip: joint scheduling team, within 15 minutes during hours, backup the front desk lead
- New patient, hand or wrist: hand clinic scheduler, same target, backup the joint team
- New patient, back or neck: spine scheduling, same target
- Referral from another office: referral coordinator, same business day
- Existing patient scheduling: the patient's usual team
- Clinical questions: the nursing pool, under clinical protocol
- Refills, billing, records: their own teams, within a business day
The same idea fits other specialties: medical and cosmetic dermatology, pediatric and adult patients, obstetrics and gynecology. Keep the table to one page, review it quarterly, and make it the source every tool is configured from.
Does ChatGPT recommend your practice?
The Surge Score measures five things about your practice website: how often ChatGPT, Gemini and Perplexity recommend you, your PageSpeed, your structured data, your indexing and your reviews, each with its evidence and date. Free.
Route by reason, not by name
Most new patients do not know which of your providers sees their problem, so they may pick by photo or by whoever appears first. Ask what they need instead.
- Start booking and request forms with a plain question, "What can we help you with?", using the words patients use rather than clinical terms; see medical jargon instead of the words patients search
- Then show the providers and locations who treat that problem, with the soonest availability
- Keep a choice of provider for returning patients who want their usual clinician
- Apply rules before offering a provider: subspecialty, age ranges, and insurance plans that differ between providers, especially for newer providers still being credentialed
This only works if your scheduler can hold those rules. See online scheduling that writes into your EHR.
Keep the phone tree shallow
A phone menu is a routing table read aloud, and long ones lose callers.
- Put new patient appointments first or second in the menu
- Keep each level to a few options, and avoid more than two levels before a person
- Do not make new patients choose a provider by name or extension
- Ask for location first only if your locations truly differ in services or hours
- Always allow a way to reach a person
- Check where callers hang up, if your phone system reports menu activity
Call your own main line twice: once as a new patient with a specific problem, once as a returning patient who needs a refill. Count the options and time how long it takes to reach the right person. If either path takes more than a minute, simplify.
Shared queues beat personal inboxes
Requests routed to a person disappear when that person is out. Requests routed to a team queue get picked up by whoever is working.
- Route every channel to team queues, with assignment so each request has one owner
- Keep a coverage calendar so backups know when they are on
- When a provider leaves or joins, update every route the same day: forms, chat, phone menu, AI receptionist rules, booking pages and online listings
- Add a new provider to the routing table before their first clinic day, not after the first misrouted request
Listings matter too, because patients search for providers by name. How to list several providers at one location is covered in multiple providers, one location.
Test the routes
Once a quarter, send three test requests that each take a different path through your practice:
- A web form from a new patient with a specific problem, asking for your second location
- A text from an existing patient who wants to reschedule with a provider who is out this week
- A chat or call from a referring office asking where to send a referral
For each one, record who received it first, how many people touched it, and how long it took to reach the team that could act. Every extra handoff is a delay worth removing. Use obviously fake names, tell the team testing is happening, and cancel any test booking the same day.
Fold the results into your monthly numbers; see how to measure your real response time.
Checklist
- One written routing table covers every request type, owner, target and backup
- Phone, forms, text, chat and any AI receptionist follow the same table
- New patients choose by reason, then see the providers who treat it
- Insurance, age and subspecialty rules are applied before a provider is offered
- Every request routes to a team queue, not a personal inbox
- Provider changes update every route the same day
- Three test requests are run every quarter
Frequently asked
Should new patients choose their own provider?
Usually not first. Ask what they need help with, then show the providers who treat it and their soonest openings. Patients who want a specific clinician can still choose one, and returning patients should be able to book with their usual provider.
How many options should a practice phone menu have?
As few as possible. A few options per level, no more than two levels before a person, and new patient appointments near the top. Test it yourself as a new patient and as a returning patient and simplify anything that takes more than a minute.
Can an AI receptionist route calls between providers?
Yes, if you give it the same rules your staff use: which reasons go to which team, which providers take which insurance and ages, and when to transfer to a person. Configure it from your routing table and test it with the same three requests.
Book a strategy call with the team.
Twenty minutes. We'll walk through the specific opportunities in your market and what a MedPracticeGrowth engagement would look like for your practice.