Patient services teams need a competency matrix that keeps clinical judgement out of the agent's hands while it books appointments, sends reminders, chases referrals and sorts patient messages. Coordinators must recognise a clinical concern hidden in an admin message, protect health data, and know exactly which drafts they may send without a clinician.
What makes patient services different?
The work looks administrative, but the messages are not. A patient asking to move an appointment may mention new chest pain in the same sentence. An agent sorting that message as a booking change is doing exactly what it was asked, and missing the only thing that mattered. The core skill for coordinators is reading past the request to the person.
Health data adds a second layer. Under the GDPR it is special-category data, and in the US it falls under HIPAA. Either way, the coordinator who sends an agent's draft must check it shares no more than the recipient needs. A reminder that names a clinic specialty on a shared phone can disclose a diagnosis.
The matrix sets these skills by role. It sits within AI agent skills by role, and student-facing teams face a similar mix of admin and welfare, as the student services team's competency matrix shows.
How do you fill it in?
Work through each patient contact the agent touches. For each, set a target level for coordinators, the patient services lead and the clinical lead, using:
- Aware: knows what the agent does and can explain why a request is waiting.
- Skilled: sends or approves the agent's drafts and catches what they miss.
- Accountable: decides escalations, signs off changes to the agent's scripts and sources.
Then add the escalation trigger for each row: the words or situations that must reach a clinician, whatever the agent proposes.
The template
| Patient contact | Agent's role and depth | Coordinator | Patient services lead | Clinical lead | Escalation trigger | Evidence |
|---|---|---|---|---|---|---|
| Booking and rebooking | Books within clinic rules | |||||
| Reminders | Sends approved templates | |||||
| Referral chasing | Drafts letters to other providers | |||||
| Incoming messages | Sorts and drafts replies | |||||
| Clinical questions | Refuses and routes | |||||
| Record requests | Drafts response | |||||
| Complaints | Drafts acknowledgement | |||||
| All | Files every verdict |
A worked example
A hypothetical outpatient clinic group with ten coordinators, one patient services lead and a clinical lead. Its agent books at depth 3 within clinic rules and drafts everything else at depth 2.
| Contact | Agent's role | Coordinator | PS lead | Clinical lead | Escalation trigger | Evidence |
|---|---|---|---|---|---|---|
| Booking | Books, 3 | Skilled | Accountable | Aware | Patient mentions new or worse symptoms | Weekly sample |
| Reminders | Sends, 3 | Skilled | Accountable | Skilled | None; template content approved by clinical lead | Template sign-off |
| Referrals | Drafts, 2 | Skilled | Accountable | Skilled | Referral overdue past clinic limit | Chase log |
| Messages | Drafts, 2 | Skilled | Accountable | Skilled | Pain, bleeding, breathing, self-harm, medication | Scenario test |
| Clinical questions | Refuses and routes | Skilled | Skilled | Accountable | Any clinical question | Refusal sample |
| Record requests | Drafts, 2 | Aware | Accountable | Skilled | Third-party request | Procedure check |
| Complaints | Drafts, 2 | Skilled | Accountable | Skilled | Complaint about care | Lead review |
| All | Files verdicts | Aware | Accountable | Aware | None | Walkthrough |
Coordinators must be Skilled at recognising refusals. When a patient asks whether to stop a medication, the agent should refuse and route the question to a clinician. A coordinator who overrides that refusal to be helpful, by sending a soft answer, has crossed the line the agent was built to hold.
Reminder content is signed off by the clinical lead, not the services lead, because the wording can disclose a condition. Once approved, the agent sends reminders at depth 3; any change to wording goes back through the clinical lead. The approver authority matrix for the patient services team records that, and the reviewer rota for the patient services team keeps a Skilled coordinator on the message queue whenever clinics are open.
Where the Academy fits
Pryme Intelligence Academy's Foundations badge gives coordinators the shared vocabulary in about four hours. Those who send or approve drafts take the Operator track, with module tests set in healthcare and their own role. Its practicum allows no missed red line, which suits a queue where one missed symptom matters more than many quick replies. Market rules differ, as the brief on training for patient services teams in healthcare in the UAE shows.
Questions people ask
Can the agent triage patients clinically?
No. It sorts messages and routes anything clinical to a clinician. Clinical triage needs a qualified person, and an agent that attempts it is outside its scope.
Who writes the escalation triggers?
The clinical lead, with input from coordinators who see the real messages. Review them whenever a missed escalation occurs, and add the phrase that was missed.
Do clinicians need to be on the matrix?
The clinical lead does, because they approve scripts and receive escalations. Other clinicians need to know what the agent does and how escalations reach them.