Workflow

From “my shoulder hurts” to an orthopedics slot: the decision path a routing rule set actually follows

Routing is a rule set you configure, not a guess. How a chief complaint becomes a department, what happens when a complaint spans two specialties, how red-flag symptoms break out of the flow, and what the caller hears when the department is full.

The caller describes the concern in their own words; the rule set maps that chief complaint to a department — ankle pain to orthopedics, skin rash to dermatology
Complaints that span two specialties are handled explicitly: offer the caller the choice, or hand the routing decision to a human scheduler
Red-flag symptoms leave the routing flow entirely and escalate to that department's clinical staff in real time
Once the department is settled, availability is checked live across that department's schedule before any time is offered
A full department is a fallback ladder, not a dead end — wait-list, urgent care, a callback when an urgent slot opens, or a partner clinic
Every call is logged and tagged with the department it routed to, so you can see where your volume actually goes

How it pays back

The mapping is yours to set

Whether back pain with numbness belongs to orthopedics or neurology is a decision about how your group is organized, not something a vendor should decide for you. Your staff configure the routing logic; the AI applies it the same way on every call.

Ambiguity follows a defined path instead of a guess

A complaint that could belong to two departments is not quietly assigned to one of them. The caller is offered the options, or a human scheduler makes the final routing call, and the reasoning is visible in the summary rather than buried in a decision nobody saw.

Red flags interrupt the flow rather than completing it

Symptoms you have defined as urgent escalate to the specialty's clinical team while the caller is on the line. They are not routed, booked and only then noticed by whoever opens the summary.

The caller you cannot book still leaves with an outcome

When the department has nothing open, the fallback ladder gives the caller a next step: wait-list, urgent care, a callback, or a partner clinic. Every call ends somewhere, which is what stops a full schedule turning into a lost patient.

Calls routed correctly

AI determines specialty and routes on first contact, no blind transfers

Structured intake returned

Chief complaint, demographics, and routing decision captured for every call

Named EMR integrations

Specialty schedules sync across athenahealth, eClinicalWorks, Epic, Elation, Cerbo, Hint, Tebra, AdvancedMD, and ModMed

Urgent calls escalated

Red-flag symptoms route to the specialty's clinical team immediately

Frequently asked questions

How does the AI work out which specialty a caller needs?

It asks about the symptom or chief complaint and applies a chief-complaint-to-specialty mapping you configure. Knee pain routes to orthopedics, a skin rash to dermatology. The mapping is a rule set, so the same complaint routes the same way on every call, and you can change where it points.

What happens when a complaint could belong to two departments?

The AI gathers enough detail — symptoms, timeline, associated complaints — to apply your rule. Where the concern genuinely spans specialties, it offers the caller the options or escalates to a human scheduler for the final routing decision. Back pain with numbness may be orthopedics or neurology depending on how you have configured it.

What counts as a red flag, and what does the AI do with one?

You and your clinicians define the red-flag list; the AI applies it. When one is triggered, the call escalates to that department's clinical staff in real time instead of continuing through booking. The AI is not assessing the caller or offering advice — it is recognizing a trigger you set and getting a clinician involved immediately.

Can the caller ask for a particular provider or location instead?

Yes. Once the specialty is settled, the AI can offer appointments across multiple providers or clinic locations, and prioritize a caller's stated preference where those slots are available. Preference is applied after routing rather than instead of it.

What does a caller hear when the department they need is fully booked?

Whatever fallback ladder you configured during setup: a wait-list place, an urgent care walk-in option, a callback when an urgent slot opens, or a referral to a partner clinic. The AI does not end the call without an option, so a full schedule produces a documented next step rather than a hang-up.