They read the record of what the agent did, find which bound decided it, and check two things a general reviewer might miss: whether anything clinical slipped into an administrative decision, and whether the patient was treated the same as others in the same position. Then they approve, edit or decline, and write a reason the practice manager could follow.
What decisions does a patient services team review?
Agents in patient services make many small decisions, most of them allowed at depth 3 within the provider's own limits:
- offering and booking appointment slots;
- filling cancellations from a waiting list;
- sending reminders and preparation instructions;
- answering administrative questions such as parking, opening hours or how to request records;
- routing messages to the right team.
Some decisions are held for a person: anything mentioning symptoms, contact detail changes, cancellations of procedures, or requests from third parties. Held decisions get reviewed one by one. Allowed decisions get reviewed by sample, because nobody saw them before they happened.
What are the steps?
- Read the record. Open the verdict, the agent's draft or completed action, the sources it used and the brief version. Read the patient's own message, not just the agent's summary.
- Find the deciding bound. The minimum chain checks role scope, certificate, sources, the provider's own limits and platform guardrails. Knowing which decided tells you whether the outcome came from a rule or from missing evidence.
- Check for clinical content. Did the patient's message contain anything a clinician should have seen? Did the agent's reply say anything that reads as clinical advice? Either is a finding, even if the patient came to no harm.
- Check fairness. For waiting-list and slot decisions, compare with similar patients. Was this patient offered the same options?
- Decide and record. Approve, edit or decline, with a reason.
Where do the lines sit?
| The agent may | A person decides |
|---|---|
| Offer slots from the published schedule | Any change based on clinical urgency |
| Fill cancellations by the list's agreed order | Exceptions to the list order |
| Send approved reminder and preparation messages | Any message that interprets results or symptoms |
| Route messages to teams | Whether a third party may act for a patient |
| Draft replies to administrative questions | Complaints and requests to waive charges |
The full list of red lines for this role is in what patient services teams should never let an agent do.
A worked example
Take a community physiotherapy service whose agent fills cancelled slots from a waiting list at depth 3. In the weekly sample, a coordinator notices that patients who prefer phone contact are offered cancellation slots much less often than those who use the online portal. The record shows why: the agent offers a slot by message and moves to the next patient if there is no reply within two hours. Patients who check messages less often are skipped.
No single decision broke a rule. The pattern is unfair. The coordinator records the finding, and the process owner changes the provider's limits so the agent calls phone-preference patients through the scheduled callback list before skipping them, and so a skip is recorded with its reason. The next month's sample shows a more even spread.
How do teams keep reviews honest?
- Rotate samplers, so nobody only reviews their own team.
- Read the patient's words in every sampled item. Agent summaries can drop the phrase that mattered.
- Track edits by template. Repeated edits to the same message type belong in the agent's brief.
- Escalate clinical misses the same day, to the clinical lead as well as the process owner.
Training the whole team on these steps is covered in how to train the patient services team to review agent decisions. Student services teams apply the same method with different red lines; see how student services teams review an agent's decisions. For the full role map, see AI agent skills by role.
Where the Academy fits
Patient services coordinators who review agents daily are the audience for Pryme Intelligence Academy's Operator track: how a governed agent decides, human review, reading the workspace and when something goes wrong. Module tests are set in the learner's industry and role, so coordinators answer healthcare cases. Teams of up to 25 can start with the free readiness assessment, which shows scores by concept and where the gaps are.
Questions people ask
Should a coordinator review allowed decisions if nothing went wrong?
Yes. Problems in allowed decisions are found only by sampling them; nobody complains about a slot they were never offered.
What counts as clinical content in a review?
Anything describing symptoms, medication, results or a change in condition, and anything in the agent's reply that could be read as advice. When in doubt, treat it as clinical.
Who acts on a fairness finding?
The process owner, with the patient services lead. The coordinator records it; changing the provider's limits is their decision.