Skip to main content
All resources

Guide · 4 min read

Clinical triage best practices for multi-site groups

How to standardise phone triage across several eye care locations while keeping local flexibility, clinical ownership and a complete audit trail.

Why phone triage is different across sites

A single practice can rely on one experienced receptionist who knows that "flashes and a curtain" means the on-call doctor now. A group of five or fifteen locations cannot. Staff turn over, protocols drift, and the same symptom gets a same-day slot at one site and a call back next week at another. Triage on the phone is the highest-risk moment in the patient journey, and the one with the least consistency.

Principle one: clinical ownership

Pathways belong to clinicians, not to the front desk and not to a software vendor. The medical director, or a clinical governance group for larger organisations, defines which symptoms are red flags, what happens for each, and who is on call. The technology applies the pathway. It does not invent it.

Principle two: one standard, local exceptions

Write one pathway for the group and allow explicit, documented exceptions per site: a location without a retina specialist escalates differently from one with an on-site surgical centre. The rule is that exceptions are written down and approved, never improvised.

Principle three: escalate on uncertainty

A good triage system does not try to be clever. When a symptom is ambiguous, or the caller is distressed, or the situation is outside scope, the call goes to a person with everything already collected. Safety over automation, always.

The red-flag set most groups start with

  • Sudden vision loss or a sudden drop in vision
  • Flashes of light with new floaters, or a shadow or curtain in the field of vision
  • Eye trauma or a foreign body
  • Chemical exposure
  • Severe pain, especially with nausea or a red eye
  • Post-operative complications after cataract, LASIK or injections

Each item maps to an action: same-day slot, immediate on-call escalation, or direction to emergency care, with the wording agreed by the clinical lead.

Principle four: audit everything

Every routing decision should be traceable: what the patient said, which pathway applied, which version of the pathway was in force, and what happened next. Review the queue of escalated and flagged calls weekly. Update pathways in versions, not in place.

Principle five: tell patients what they are talking to

Callers should know when they are speaking with an AI assistant, and moving to a person should be one sentence away. Transparency is part of safety, not a separate compliance box.

See how many more calls you could answer

We'll model recovered appointments and staff hours on your own call volume.

Talk to a founder. No obligations.