Routing by Intent, Not by Menu Tree, at a Multi-Site FQHC

Routing by intent matters more at a health center than almost anywhere else, because a health center puts more behind one phone number than almost anyone else. Medical, dental, behavioral health, and the staff who help patients work out what they will owe all sit at the end of the same call, and the patient is expected to sort themselves into the right one before anyone picks up.

The menu tree is the standard answer and it fits this setting worst. It asks a caller to translate their own situation into the health center’s internal structure, in English, on the first try, before they have spoken to anyone. Patients who guess wrong land in a queue that cannot help them and get moved, or they hang up and try again later, which shows up in your numbers as a busy day rather than as a failure. Meanwhile the staff absorbing those misrouted calls are usually the ones with the least slack.

Phone access is a named priority, not a background complaint

Practice leaders are explicit that the phone is where access breaks, and they rank it alongside the metrics that get board attention.

When MGMA asked practice leaders where they were focusing patient access efforts for 2026, no-shows led at 27%, followed by online scheduling at 24%, phone access at 22%, and wait times at 21%. Those four made up roughly two-thirds of all responses.

Read that against a health center’s day and the ranking is really one problem viewed from four angles. A patient who cannot get through does not become an online scheduler. They become a no-show on a visit they could not confirm, or a walk-in absorbing a slot that was held for someone else.

The reason to start with routing rather than with adding phone lines is that misrouted calls consume the same staff twice. Once to answer, once to hand off, and the patient still has not been helped.

A health center is several practices wearing one phone number, and the differences between them are structural rather than cosmetic.

Dental runs its own providers, its own appointment lengths, and its own template. Behavioral health has its own intake rules and its own idea of what can wait. Medical carries the walk-in load. A caller saying “I need an appointment” has told you almost nothing, and the missing detail decides which schedule is even eligible to be searched.

athenaOne holds this structure in the department and provider records, which is the difference between routing that stays current and routing that has to be re-recorded. Departments describe where the work lands and providers describe who is actually available inside each one. When a health center opens a site, adds a dental operatory, or moves behavioral health intake to a different team, that change is made in the system of record, and routing that reads the system of record follows it.

The alternative is the arrangement most health centers are living with, where the phone tree encodes an org chart from two reorganizations ago and everybody has learned which wrong option gets a human fastest.

Eligibility questions are their own destination

This is the routing category health centers have that most practices do not, and leaving it unrouted pushes it into the wrong queue by default.

A large share of health center calls are not clinical requests at all. They are people asking what a visit will cost, whether their coverage is active, what happens if they are between plans, or what they need to bring to establish a sliding fee determination. Those calls belong to eligibility and enabling services staff, not to a scheduler, and they take longer than a booking.

When there is no intent category for them, they land with whoever answers. A scheduler ends up half-answering a coverage question, the patient gets an incomplete answer, and the call happens again next week. Naming the category and routing it to the people who own it fixes both ends.

The automation’s role here is to recognize the request and place it, plus collect what the receiving staff will need so the callback is productive. It does not determine anyone’s eligibility, quote a sliding fee, or tell a patient what they will owe. Those are determinations the health center makes under its own program rules, and the handoff exists precisely because they are.

The details that make an automated call sound automated

One change that sounds trivial is the best example of why this work is specific rather than generic.

Standard confirmation language includes a line asking patients to give 48 hours notice to cancel. For a same-day booking that line is nonsense, and patients hear it as proof they are talking to a machine that is not paying attention. The fix is to make the confirmation language conditional on the booking itself, so a same-day appointment gets a same-day confirmation.

That is the whole category in one example. Routing gets the call to the right place, and then a dozen small conditionals decide whether the interaction reads as competent. Which of them apply is knowable only by watching real calls at a real health center, which is why the first weeks of any deployment should be spent reading transcripts rather than tuning a model.

The handoff rule that goes with it: when a caller says something the rules do not cover, the call goes to a person rather than to a plausible guess. A wrong answer delivered confidently is worse for a health center than a transfer, because the patient acts on it.

Start with the two service lines that carry the volume

Health centers that try to map every service line before going live tend not to go live.

The sequencing that works is to pick the two lines carrying most of the call volume, usually medical and one other, and get intent routing correct for those across every site. Add the rest once the first two are stable and the transcripts are boring. That order also produces the artifact worth having on its own, which is a written map of intent to department that currently exists only in the heads of the people who have worked there longest.

Capacity is the reason to sequence rather than to wait. Health centers cannot hire their way to full phone coverage, and the labor pool that staffs a call center is the same one competing with every other employer in the area. Routing correctly is how you get more out of the coverage you already have, before anything gets automated end to end.

The measure to watch is not calls handled. It is the share of calls that reach the right destination the first time, because that is the number that decides whether staff spend their day on their own work or on somebody else’s misrouted call.

Key Takeaways

Treat intent routing as a service-line problem. Dental, behavioral health, and medical do not share a schedule, so “I need an appointment” is not yet a routable request.
Read routing from athenaOne departments and providers rather than a recorded menu. Structural changes then propagate from the system of record instead of needing a re-record.
Give eligibility and sliding-fee questions their own destination. Unrouted, they land on schedulers who can only half-answer them, and the call repeats.
Keep determinations with your staff. Automation collects the details and places the call; it does not decide coverage, cost, or fee category.
Make confirmation language conditional on the booking. A 48-hour cancellation notice on a same-day appointment is the kind of detail patients read as inattention.
Route to a person whenever the request falls outside the rules. In this setting a confident wrong answer costs more than a transfer.
Go live on the two highest-volume service lines across all sites, then expand. Mapping everything first is how these projects stall.

A health center’s phone problem is rarely a shortage of phone lines. It is that one number hides several practices, and the patient is being asked to do the sorting. Routing by intent moves that job to something that can read the health center’s own department and provider structure inside athenaOne, at any hour, in the caller’s own words. Staff then spend their time on the calls that were meant for them.

Sources

Phone access is a named priority, not a background complaint

Service lines are the routing problem, and they do not share a schedule

Eligibility questions are their own destination

The details that make an automated call sound automated

Start with the two service lines that carry the volume

Key Takeaways

Related reading

Ready to See It in Action?