Guide
Patient Call Handling Guide
Clinics can automate scheduling and administration safely. They cannot automate triage, and the boundary between the two needs to be drawn by clinicians rather than by whoever configures the system.
The dividing line
- Administration can be automated
- Clinical judgement cannot
- Symptoms always reach a clinician
- Anything about a child goes to a person
- Distress overrides the subject of the call
Triage Is a Clinical Act
Deciding how urgently a patient needs to be seen is a clinical judgement, not a routing decision. It requires assessment by someone qualified to make it, and no configuration makes an automated system qualified.
The practical implication is that any call touching symptoms, pain, deterioration or a patient’s condition goes to a clinician. The system does not ask assessment questions and does not categorise urgency.
What it can do is recognise that a call has entered that territory and hand over immediately, with the thresholds set deliberately low so that ambiguous cases escalate.
Where the Line Falls
| Call type | Automated handling | Why |
|---|---|---|
| Booking a routine appointment | Suitable | Administrative, with clear rules |
| Rescheduling or cancelling | Suitable | No clinical judgement involved |
| Opening hours and location | Suitable | Factual information |
| Preparation instructions | Suitable, from approved content | Standard, clinician-written text |
| Fees for listed services | Suitable, published rates only | Factual, provided it is current |
| Describing symptoms | Escalate immediately | Assessment requires a clinician |
| Asking whether to come in | Escalate immediately | That is a triage decision |
| Medication questions | Escalate immediately | Clinical, and potentially high risk |
| Anything about a child’s condition | Escalate immediately | Safeguarding and clinical risk together |
| Results and reports | Escalate immediately | Requires clinical context and verification |
Designing for Patients
Pace matters more here than in most settings. Clinics serving older patients should configure slower delivery, shorter sentences and more patience with pauses, and a quick route to a person for anyone who prefers one.
Distress should override everything. A caller who sounds upset is offered a person regardless of what they were calling about, because the subject of the call is not always the reason for the distress.
Language coverage should be tested against your actual patient population rather than assumed. The patients who most need language support are often those whose speech is hardest to process reliably.
A Clinic Checklist
Before configuring anything
- Clinicians write the escalation list
- Thresholds set deliberately conservative
- Preparation text approved by clinical staff
- Fee information confirmed as current
- Out-of-hours arrangements documented
Handling patient information
- Retention period agreed and documented
- Access limited to those who need it
- Recording notice wording agreed
- Your own obligations confirmed with your advisers
- Records reviewed after any change
Questions People Ask
Can the system assess urgency?
No. Recognising that a call involves symptoms and handing over is different from assessing how urgent they are, and we only do the former.
Who decides what escalates?
Your clinicians. We implement their list exactly rather than proposing a generic one.
What about paediatric calls?
Anything concerning an individual child goes to a person immediately, with no exceptions and no configuration option.
Can it discuss test results?
No. Results require clinical context and identity verification that belong with your staff.
How is patient data handled?
Retention, access and recording notices are documented during implementation so your own privacy assessment has something concrete to review.
Have Your Clinicians Write the List
Bring the escalation situations your clinical team defines. We will build the flow around them and test every path before launch.