Three inputs are enough: free or busy times, a list of meeting types, and the rules for who may take each one. With those, the agent offers slots, books, reschedules and cancels at the customer's request, and sends invitations. It never reads staff calendar contents or puts customer details in invitation titles, and sensitive bookings are held.
What does booking involve, and who owns it?
Booking a meeting looks simple: find a free slot, send an invitation. In a regulated business it carries more. Some meetings may only be held by qualified staff, such as advice meetings with a licensed adviser. Some customers need longer slots, a particular format or a different contact route because they are vulnerable. And calendar invitations are seen by assistants, colleagues and sometimes other systems, so what they say matters.
The head of the customer-facing team owns which meetings the agent may book and with whom. The calendar or booking system administrator configures access. Compliance owns rules on regulated meetings. Whether a support agent should book at all is answered in can an AI support agent book appointments for customers?; this playbook covers how.
What are the steps to set it up?
- Person, team head: defines meeting types: purpose, length, format, notice period, and which staff may take each.
- Person, compliance: marks regulated and sensitive types, such as advice, complaints, hardship or bereavement, and the staff eligibility for each.
- Person, calendar administrator: grants the agent free or busy access to eligible staff calendars, and write access only to create, change and cancel the meetings it books.
- Person, team head: sets held bookings: sensitive types, meetings outside normal hours, and any booking for a customer flagged as possibly vulnerable.
- Person, compliance: approves invitation templates, with neutral titles and no account details.
- Agent, depth 2: runs a trial where it proposes bookings and staff confirm them.
- Person, team head: approves the agent's depth.
- Person, calendar administrator: tests revocation, including what happens to meetings already booked.
What is scoped per capability, and at what depth?
| Step | The agent does | Depth | Stays with a person |
|---|---|---|---|
| Read availability | Reads free or busy times only | 1 | Nothing |
| Offer slots | Proposes times to the customer | 3 | Nothing |
| Book a standard meeting | Creates it and sends the invitation | 3 | Staff eligibility rules |
| Book a sensitive meeting | Proposes the booking | 2 | Confirming it |
| Reschedule or cancel at the customer's request | Changes the meeting | 3 | Nothing |
| Cancel on behalf of staff | Drafts the cancellation | 2 | Sending it |
| Read meeting contents | Nothing | none | Never granted |
Booking for customers differs from managing a colleague's own diary; how to let an AI agent manage your calendar covers the internal case.
What should invitations and conversations say?
Titles should be neutral, such as "Meeting with your bank", never "Debt arrears review" or the customer's account number. The body should give time, format, how to join, and how to change or cancel. The agent should tell the customer they are arranging the meeting with an AI system and name the person they will meet. It must not predict the outcome of the meeting or discuss its substance, such as whether a loan will be approved.
Customers should be verified before booking meetings about their own accounts, using the firm's normal checks, so a meeting is not arranged by someone impersonating them.
What is recorded?
The booking system records each meeting created, changed or cancelled under the agent's identity. The agent's own record keeps the customer's request, the verification result, the meeting type chosen, the eligibility rule applied, the bound that decided and the approver for held bookings. Reminders the agent sends are logged too.
Which controls make it safe?
Free or busy only. The agent sees when people are available, not what their meetings are about.
Eligibility enforced. An advice meeting is never booked with someone not qualified to give advice. Evidence: the eligibility rule stored with each booking.
Neutral templates. Evidence: the template version on each invitation.
Sensitive bookings held. Evidence: held bookings with the confirming person's identity.
Revocation planned. When access is removed, existing bookings stay in staff calendars and are flagged for a person to manage, so customers are not left with meetings nobody owns.
What should you measure?
Meetings booked, rescheduled and cancelled by the agent, no-shows, meetings booked with an ineligible person (the target is none), held bookings and decision times, customer complaints about booking, and invitations that needed correcting.
Where does it usually go wrong?
Full calendar access. The agent reads everyone's meeting details to find slots, and can repeat them.
Revealing titles. Invitations name the subject, which is then visible to a customer's household or a colleague's assistant.
The wrong person is booked. The agent picks whoever is free rather than whoever is qualified or already knows the customer.
Time zones and notice are ignored. A customer abroad is offered a slot in the middle of their night, or a meeting is booked for the next morning when the meeting type needs preparation. Store the customer's time zone and respect each type's notice period.
Vulnerable customers get standard slots. A short video call is booked for a customer who asked for a longer phone call because of a disability. Read and respect stated needs, and hold where unsure.
Where Pryme fits
In Pryme, a customer's stated preferences reach the agent as declared information and staff eligibility comes from your systems of record, so the agent books against both. Sensitive bookings are held for a named person, and every verdict is filed. The wider route is in deploying an AI agent: train, shadow, certify, widen.
Questions people ask
Can the agent book meetings with prospects as well as customers?
Yes, with the same rules, though there is less to verify. Keep prospect bookings separate from regulated advice meetings, which may need checks before they happen.
Should the agent send reminders?
Reminders reduce no-shows and are routine depth 3 work. Use the customer's chosen channel and keep the content neutral.
What if the customer wants to discuss something during booking?
The agent notes the topic for the person they will meet and explains that the meeting is where it will be discussed. It should not start the conversation itself.