Panel and Site Routing
In primary care a patient belongs to a physician, not a building. Route calls by panel, apply per-provider rules, and hold continuity when it matters.
Multi-site routing in most specialties is a geography problem. In primary care it is a continuity problem. Booking a diabetic follow-up with whoever is free at the closest office produces a visit where nobody knows the patient, and the physician who does know them finds out three weeks later.
One partner is closed to new patients, one takes newborns, one does not do procedures, one is half-time. Front desk staff learn this over months and temporary staff never do. Encoding it once means the rules are applied on the first call, not the third.
Your heaviest callers are often elderly, managing several conditions, or calling on behalf of a parent. A menu organised around your locations and departments asks them to model your org chart. Asking them what they need instead is faster for everyone.
A departure produces weeks of calls about where the doctor went, who the patient sees now, how to get records, and who signs refills in the meantime. A single approved script, delivered consistently at every hour, is what keeps a panel from dispersing.
Unlimited concurrent calls
Every site's line answered at the same moment, including the branch staffed by one person
One published fact set
Hours, walk-in rules and provider availability stated identically across all locations
Dozens of languages
The same routing rules applied in the patient's language, including through a caregiver's phone
No. It applies your assignment and continuity rules. Clinical judgment about who is the right clinician stays with your practice, and anything your rules do not cover is routed to staff rather than resolved by the system.
From your system of record where an interface exists, available through API or FHIR for supported systems and through secure workflow automation for others. Without an interface it asks the patient and flags the booking for confirmation rather than assuming.
Yes. Location-specific facts are configured per site, including hours, walk-in rules, lab and imaging availability, parking and access notes, and which providers are physically there on which days.
Either arrangement works. Practices commonly keep existing per-site numbers so patients dial what they already know, while routing all of them through the same rule set, so the patient experience is consistent regardless of which number they used.
You write the answer and the system delivers it: who is covering, whether the panel is being reassigned, how to request records, and who handles refills during the transition. It does not improvise, and it captures patients who ask to be reassigned to a named partner.
Where your scheduling system exposes those slots and your rules allow it, yes. Many practices restrict cross-site booking for follow-up care and allow it freely for acute visits, and both patterns are configurable.
Related
Accepting New Patients and Panel Capacity Calls
How patients join a panel, and the capacity rules that decide whose panel they join.
Related
Chronic Care Follow-Up Recall for Primary Care
Where continuity pays off most, and where routing to the wrong provider costs most.
Related
Same-Day Cancellation Backfill for Primary Care
Filling a released slot without quietly breaking the continuity rules you just set.
Specialty hub
AI Receptionist for Primary Care
The full primary care front-desk picture: access, recall, refills, referrals, results and coverage questions.
Related
Satellite Clinic Day and Location Routing for Retina
Your physician is at one site Tuesday and another Thursday. Route callers by physician day, location and equipment instead of whoever picked up.
See how MedReception AI handles after-hours calls, scheduling, intake, and patient communication for medical practices like yours.
