Smart Routing for Ophthalmology Call Centers

Smart routing is worth more to an eye practice than to almost any other specialty, because an ophthalmology phone number is not one destination. It is five businesses sharing a line: the clinic, the optical shop, the surgical coordinator, billing, and records. A caller who reaches the wrong one has not been helped, and in most practices the person who answered has no way to send them onward except a transfer and an apology.

The front desk at an eye practice spends its day sorting rather than solving. Someone wants a copy of their glasses prescription, which is a records request. Someone wants to know when their contacts will be in, which is the optical shop. Someone was operated on last Thursday and has a question about their drops, which belongs to the surgical coordinator and nobody else. Each of those is a different queue with a different owner, and the routing decision is being made in the first fifteen seconds by whoever picked up.

The queue is not one queue

Practice leaders are consistent about which phone work eats the most time. An MGMA poll found eligibility and prior authorization at 45% of staff phone time, scheduling at 31%, intake at 9%, and prescription refills at 6%.

In an eye practice those categories sit behind a routing decision that has to happen first, and the categories themselves split further. Scheduling means a comprehensive exam, a post-op check, a surgical consult, or an optical appointment, and those live on different calendars owned by different people.

Smart routing is the layer that makes the rest of the automation worth having. Getting a caller to the right queue on the first attempt is what converts a four-minute call with two transfers into a ninety-second one, and it is also what stops the optical shop’s voicemail from filling up with clinical questions.

The practical test of whether routing is working is the transfer rate, and it is a number most practices have never measured because the transfers happen inside the building and leave no record.

Subspecialty routing is a mapping the practice writes

A group with retina, glaucoma, cornea, and oculoplastics has four sets of appointment types, four sets of calendars, and callers who describe their reason in plain language.

The temptation is to have the automation work out which subspecialty a caller needs. That is the wrong design and it is out of bounds. What works instead is a mapping the practice’s clinicians write once: these stated reasons route to this provider group and this appointment type, this set of phrases routes straight to a person, and anything unmatched routes to a person.

The mapping is more valuable than it sounds because it is currently undocumented. It lives in the heads of the two schedulers who have been there longest, which means it is applied differently on their days off and lost entirely when they leave. Writing it down is most of the project, and practices consistently find the exercise useful on its own.

A related reconciliation has to happen at the same time. The provider roster on the practice website and the roster in athenaOne routinely disagree, and callers ask for the people listed on the website. Working out who actually works there and takes appointments is step one, before any routing rule can be trusted.

The optical shop is a different business on the same line

Optical is where eye practices lose the most call handling time relative to the revenue involved, and it is the easiest routing win.

The calls are short, repetitive, and almost entirely status questions: are my glasses ready, did my contacts arrive, what is my prescription, do you take my vision plan for frames. None of them need the clinical front desk, and most of them do not need a person at all once the automation can read order status.

The complication is that the two businesses share a patient. A caller asking about contacts may also be overdue for the contact lens fitting that legally has to precede the order, and a caller asking for their prescription may be asking because it expired. Routing has to carry that context rather than dropping the caller into optical and forgetting the clinical side, which means the same call can end with an order status and a booked fitting.

Where the practice’s rules say a fitting is required before an order, the automation states the requirement and books it. It does not decide whether the prescription is still appropriate for the patient.

Post-op callers need one specific person

The highest-stakes routing category in an eye practice is the recent surgical patient, and it is the one most likely to be handled badly by a general queue.

A cataract patient in their first week after surgery has a defined follow-up schedule, a drop regimen, and a surgical coordinator who has been their contact throughout. Sending that caller to the general front desk produces a transfer at best. The routing rule is straightforward: if the caller has a surgery in the recent past, they go to the surgical coordinator’s queue, and that rule can be checked against the record rather than inferred from what the caller says.

What the automation does with the call once routed stays administrative. It confirms the next post-op appointment, rebooks it, takes a message with the details the coordinator needs, or connects a person. Questions about drops, vision changes, or anything the patient is experiencing go to a human immediately, using the phrase list the practice’s clinicians wrote. The automation matches the phrase and connects the call. It does not form a view about what the patient is describing.

Surgical scheduling has its own routing wrinkle worth encoding. Procedure blocks have hard cutoffs driven by room prep and turnover rather than clinic hours, so the last bookable procedure slot is well before the practice closes, and a caller offered a time that does not exist is a call that happens twice.

Say what happens when the answer is no

The routing case practices script last is the one that damages them most: the caller who wants something the practice cannot give them.

A patient asking for a specific physician who is not accepting new patients is a conversation design problem, not a flag on a record. Handled badly it sounds like a brush-off and the caller books somewhere else. Handled well the automation acknowledges the request, explains the constraint in the practice’s own words, and offers the providers who do have availability, with the wait time stated honestly.

The same applies to the caller whose plan the practice does not take, and to the one asking for an appointment inside a lead time the practice does not allow. Each of those needs wording the practice approved in advance, because the alternative is improvisation at the moment the practice is most exposed.

These scripts are worth reviewing quarterly against the call review record. The phrases callers actually use drift, and the routing map should follow them rather than the other way around.

Key Takeaways

Measure your internal transfer rate first. It is the number that tells you whether routing is broken, and almost no practice has it because transfers inside the building leave no record.
Write the reason-to-provider-group mapping down. It currently lives with your two longest-tenured schedulers and is applied differently on their days off.
Reconcile the provider roster on your website against athenaOne before trusting any routing rule. Callers ask for the people the website lists.
Route optical status calls away from the clinical front desk, but carry the clinical context with them so an expired prescription still ends in a booked fitting.
Route recent surgical patients to the surgical coordinator by record, not by what the caller says. That check is reliable; inference is not.
Encode the procedure block cutoff. Offering a procedure time that room turnover makes impossible generates a second call and a rebooking.
Script the no. A patient told a provider is not accepting new patients needs the practice’s own wording and a real alternative, or they book elsewhere.

Routing is unglamorous and it is where the time goes. An eye practice running five service lines through one phone number is making a sorting decision on every call, hundreds of times a day, using knowledge that was never written down. Writing it down and handing it to an AI team working inside athenaOne does not change any of the practice’s rules. It just means the caller reaches the right desk the first time, and the people at those desks spend their day on the calls that actually needed them.

Sources