How to build a reviewer rota for patient services team

Staff the patient services rota for the morning rush and for clinical routing. Most held messages arrive when the clinic opens, so that is when reviewers are needed. Every session also needs a named duty clinician to take the messages the agent holds because they mention symptoms. Referral administration gets its own line, timed against referral deadlines.

What does the rota cover, and who owns it?

A patient services agent books and moves appointments, sends reminders, answers questions about preparation and directions, and handles referral paperwork. It holds messages that mention symptoms or medication, requests from someone other than the patient, cancellations of referrals, and anything it cannot answer from the clinic's approved information. It refuses to give clinical advice, because that is outside its role, and routes those messages to a person.

The practice manager or patient services lead owns the rota. The clinical lead agrees the duty clinician arrangements. The guide to AI agent skills by role covers what coordinators need to know, and what patient services teams should never let an AI agent do sets the outer limits the rota protects.

What are the steps?

1. Agent, depth 1: reports holds by type and hour. Bookings it could not complete, symptom mentions, third-party requests, referral holds.
2. Person (patient services lead): sets response targets. Symptom holds seen by a clinician within the session; third-party requests within the day; booking holds within hours; referral holds well inside the referral deadline.
3. Person (patient services lead): staffs the opening peak. More coordinators in the first hours of each day and after weekends and holidays.
4. Person (clinical lead): names a duty clinician for every session. With a backup. The duty clinician decides what happens to each symptom hold.
5. Agent, depth 3: books and moves routine appointments. Within the clinic's slot rules.
6. Agent, depth 2: drafts replies to held messages. With the approved information it relied on.
7. Person (coordinator): decides non-clinical holds. Send, edit, route or decline.
8. Person (referrals coordinator): manages referral holds. Named daily; checks every urgent referral against its deadline.

Why must every session have a duty clinician?

Patients write about symptoms in booking messages all the time: they want to move an appointment because they feel worse, or ask whether a new pain matters. The agent holds these. A coordinator should not decide them; their job is to get the message in front of a clinician fast. If no clinician is named for the session, the message waits in a queue nobody clinical is watching.

Naming the duty clinician on the rota solves that. The coordinator routes, the clinician decides, the record shows both. Health data is special-category data under GDPR and UK GDPR, and protected health information under HIPAA in the United States, so the routing must reach only the people who need it.

Which skills mix does each session need?

At the opening peak: enough coordinators to keep booking holds within target, one of whom is trained for third-party requests. Through the day: fewer coordinators, the duty clinician and the referrals coordinator. Coordinators new to the agent should not handle third-party requests until they have shown they can check authority properly; the AI agent competency matrix for the patient services team sets out the steps, and the approver authority matrix for the patient services team sets who may approve which disclosures.

Which controls matter, and what evidence do they leave?

• Symptom holds reach a clinician. Evidence: routing time and the clinician's name on each.
• Disclosures have a recorded basis. Evidence: how identity and authority were confirmed, on each third-party verdict.
• Answers come from approved information. Evidence: the source cited on each reply, from the clinic's policy library.
• Referrals are tracked against deadlines. Evidence: referral dates and actions in the record.
• Every session has a duty clinician. Evidence: the rota.

What should be measured?

• Symptom holds seen by a clinician within the session.
• Booking holds decided within target during the opening peak.
• Third-party disclosures with a recorded basis: the target is all of them.
• Urgent referrals delayed or cancelled without a clinician's decision: the target is none.
• Messages routed to clinicians that plainly did not need one, as a check on over-caution.

Where does it usually go wrong?

The duty clinician is fully booked. A duty clinician with a full appointment list cannot answer held messages. Protect time in their session.

Coordinators answer clinical questions to be kind. It feels helpful; it is outside their role. Coaching should cover how to reply kindly while routing.

After-holiday peaks are missed. The first morning after a long weekend brings days of messages at once. Staff for it.

Student services and HR teams face their own sensitive-message routing; compare the rotas for the student services team and the HR team.

Where the Academy fits

Patient services coordinators who review an agent's holds are the people the Academy's Operator track is written for, and module tests are set in the learner's own industry and role. A clinic can choose to put only coordinators with a current Certified Pryme Operator certificate on the third-party disclosure line, and check each certificate at source through VerifyDoc.ai.