How to keep patient services teams ready for an AI agent’s 90-day recertification

Patient services teams need each cycle's changes by department, by channel and by caller type. Every 90 days the patient enquiries agent is recertified on the provider's own conversations, and which departments it books for, how it checks identity and when it hands to a person can all change. Brief coordinators by department, practise carer and escalation calls, and sample the first fortnight.

What changes for patient services coordinators?

A patient enquiries agent in a hospital or large provider usually answers non-clinical questions at depth 3: appointment times, directions, how to prepare, transport and parking. It reschedules appointments within each department's rules at depth 3. It drafts acknowledgements to complaints and feedback at depth 2. Any message that sounds clinical, such as worsening symptoms or medication worries, is escalated to a named person. It refuses to share details of a patient's care with anyone whose identity and authority it cannot confirm.

Recertification re-runs the agent's cases on recent conversations. Three kinds of change reach coordinators. A department may be added or removed from the agent's booking scope. Identity checks may tighten, so more callers reach a person. And escalation phrases may widen after the replay finds a missed case.

Take, for example, a hospital where the outpatient orthopaedics department changes its rules so that post-surgery follow-ups can only be moved by the department itself. After recertification the agent refuses to reschedule those appointments and hands each request to a coordinator, naming the bound that decided. Coordinators who used to see none of these calls now take several a day and need the department's contact and rules before the first one arrives.

Carers are the hard case. A carer who says they act for a patient is making a declared claim. Unless the provider's records show that authority, the agent refuses to share details and hands to a coordinator, who must decide what can be said.

Who owns readiness?

The patient services manager owns coordinator readiness and the rota. Each department's operations lead owns its booking rules. The builder owns recertification. A clinical safety lead should approve any change to escalation, and the information governance lead any change to identity checks.

Steps for each cycle

1. Agent, depth 1: report the cycle by department: enquiries answered, rescheduled, escalated and refused, with the deciding bound for each.
2. Person (clinical safety lead): review escalations, especially any that reached a person late.
3. Person (department leads): confirm booking rules that changed in the cycle.
4. Person (builder): recertify on recent conversations and updated rules.
5. Person (manager and builder): write the change note by department and channel.
6. Person (clinical safety and information governance leads): approve escalation and identity changes.
7. Agent, depth 2: draft practice conversations, including a carer call and a clinical-sounding message, checked by the manager.
8. Person (manager): brief coordinators by department, then sample the first fortnight.

What should coordinators practise?

Carer conversations. Work through a carer who is upset, insistent and probably genuine, but whose authority is not recorded. Coordinators should know what they can say, what they cannot, and how to record the conversation.

Escalation handover. When the agent escalates, the patient has already explained once. Coordinators should read the agent's summary first and confirm, not restart.

Department changes. If a department left the agent's booking scope, its patients now call coordinators. Give each coordinator the reason and the new rules.

Language and access. If a patient needs an interpreter or an accessible format, the agent should hand over. Coordinators practise picking those cases up quickly.

Health data is special-category data under GDPR, and in the US HIPAA applies, so identity rules are not a service preference. Pryme Intelligence Academy's Operator track, with tests set in the learner's own industry and role, gives coordinators who clear held work a checkable certificate.

Controls and the evidence they leave

• Escalation review each cycle. Evidence: the clinical safety lead's review and sign-off.
• Identity rule approval. Evidence: the information governance lead's signed approval.
• Department briefings. Evidence: attendance by department.
• Fortnight sample. Evidence: conversations reviewed and corrections.
• Practicum for new coordinators. Evidence: the practicum log template for patient services teams.

What to measure

Time from escalation to a person's response. Calls handed over for identity reasons, by department. Repeat contacts within a week on the same appointment. And complaints that mention the agent. A spike in identity handovers after a cycle usually reflects tighter checks working, but it needs staffing.

Where does readiness slip?

Departments change their rules without telling patient services, so the agent books by old rules or holds bookings for reasons coordinators cannot explain.

Coordinators share information with carers to be kind. The rule exists to protect the patient; coordinators need a practised alternative to saying no.

Escalations go to a named person who is on leave. Name a second person on every rota.

Whether coordinators need a certificate to clear held work is the provider's choice; see do patient services teams need a certificate to approve AI agent actions, and on responsibility, are patient services teams accountable for an AI agent's mistakes. Student services teams run a similar cycle; compare keeping student services teams ready and the guide to AI literacy and certification for people who work with agents.