Multi-Site Routing
Your physician is at one site Tuesday and another Thursday. Route callers by physician day, location and equipment instead of whoever picked up.
Retina groups typically run a hub plus satellites, with the specialist rotating between them while angiography, wide-field imaging or laser capability stays fixed at one or two sites. Routing that only knows about people, or only about buildings, will keep producing appointments that cannot be delivered where they were booked.
On the days a satellite is dark, its number rings into a machine. On the days it is open, it is answered by a technician between patients who cannot see the hub's schedule. Answering every site's number the same way, with the same rules, removes the difference between a Tuesday call and a Friday call.
A patient who arranged a ride, arranged an escort and travelled to the wrong site has lost the day, and so has your schedule. The site, the date, the physician and the arrival instruction being confirmed together on the call is a small step that prevents an outcome nothing downstream can fix.
Site coverage, physician days and visit-type availability are configured centrally and change on the next call. There is no per-office phone tree to rebuild, no laminated card at one desk that is six months out of date, and no difference in what a caller is told depending on which number they dialled.
Unlimited concurrent calls
Every site's line is answered at once, including the ones that are dark that day
24/7 coverage
A satellite closed four days a week still answers its published number
HIPAA BAA included
Location, schedule and patient data encrypted with AES-256 at rest and TLS in transit
No. Sites are configured within one rule set, and each published number is mapped to the site it belongs to while sharing the same logic. A caller who dials the satellite and needs the hub is handled in one conversation rather than being told to call another number.
From your schedule. Where provider templates are available through API or FHIR, the physician-day pattern comes from the system directly. Where they are not, you maintain the rotation as a rule and update it when the rotation changes, which is the same information your schedulers already hold.
Yes, by treating equipment availability as a constraint on the visit type at that location, in the same way physician availability is. A caller who needs a study that only runs at the hub is offered hub dates, and is told why, using your language.
The call is answered rather than sent to a machine. Routine requests are handled normally, and anything your practice treats as urgent follows the escalation path your clinical team wrote, which is usually shared across sites so a single on-call route covers the group.
As a distinct location with its own address, arrival time convention and instructions, so a patient scheduled at an ambulatory surgery centre is never given the clinic's directions. Facility date changes are captured and routed to your surgical coordinator rather than committed on the call.
Yes. Adding a site, changing which day a physician covers it, or closing a location for a week is a configuration change that takes effect on the next call. Nothing has to be re-recorded and no phone tree has to be rebuilt.
Related
Anti-VEGF Injection Recall Scheduling for Retina Clinics
Why an injection interval and a physician's site rotation have to be solved together.
Related
Filling Cancelled Eye Clinic Slots From a Real Waitlist
Refilling a satellite slot that cannot simply be moved to next week.
Operations
Multi-Office and Branch Call Coordination
The general multi-location routing pattern this builds on, across any specialty.
Pillar guide
AI Receptionist for Ophthalmology and Retina
The full eye-care front desk: injection recall, surgical coordination, urgent symptom routing, optical and access workflows.
Related
Multi-Location Scheduling for OB/GYN Practices
In multi-site OB/GYN, scans, procedures and OB visits sit at different offices.
Related
Panel and Multi-Site Call Routing for Primary Care
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.
See how MedReception AI handles after-hours calls, scheduling, intake, and patient communication for medical practices like yours.
