Define booking rules first
Specify working hours, duration, buffer time, holidays and who can take each appointment type. Store availability in the system your team already trusts. Confirm time zone and service requirements before presenting slots.
Define the scheduling rules and source of availability
Use the booking system or authoritative calendar as the source of truth. Document appointment duration, preparation buffers, working hours, time zones and who is qualified to take each appointment. A conversational tool can ask useful follow-up questions, but the scheduling service should enforce the rules. Give customers a manual path when the request falls outside known options.
- Collect the detailsClarify service, duration and time zone
- Reserve the slotCheck live availability and confirm the booking
- Send a receiptInclude the appointment reference and change options
Confirm availability when the customer commits
Treat a proposed slot as tentative until the calendar confirms it. Send confirmation and make changes easy. Route requests involving special requirements or uncertain availability to a person.
Confirm details before committing an appointment
Show the time, time zone, service and any cancellation policy before creating the booking. Recheck availability at the time of confirmation so two people cannot claim the same slot. Use a unique request identifier or booking platform guarantees to protect against retries. After the system confirms the appointment, return a reference and explain how to cancel or reschedule.
Test awkward situations
Simulate two people choosing the same slot, a cancellation, a time-zone change and an unavailable calendar. Track successful bookings, reschedules, duplicate events and requests that needed human help. Give staff a manual booking path.
Test conflicts, fallbacks and operational handoff
Try daylight saving changes, delayed replies, off-hours bookings, policy exceptions and two simultaneous requests. Verify what happens when the calendar cannot be reached or an email fails. Make sure customers do not receive a confirmation for an appointment that was never saved. Only collect the information needed for scheduling and route sensitive cases to an appropriate system.
Booking an assessment across time zones
A consultancy offers appointments to clients in multiple regions. The assistant translates a customer’s requested time, shows both the client and office time zones, and checks availability again after the customer confirms. If the slot disappears, it offers alternatives. Successful appointments receive an ID and cancellation instructions.
Include customer-facing policies in the workflow without asking the model to invent them. Appointment lengths, cancellation rules and staff assignments should come from the approved booking configuration. Keep confirmations and reminders consistent with that source. Run through a cancellation after a reminder has already been scheduled and verify the old reminder is removed. Check who can see appointment details and what the system logs when someone changes or cancels a booking.
| Step | Owner | Protection |
|---|---|---|
| Interpret the request | Assistant or form | Ask a clarifying question when needed |
| Validate and reserve the slot | Scheduling service | Recheck availability and handle retries safely |
| Send confirmation | Booking system or approved messaging | Use a confirmed record and clear next steps |
Common questions
What if the user asks to reschedule?
Retrieve the booking through the approved route, verify the user as appropriate, and confirm the replacement before cancelling the original according to policy.
Can a bot book without a calendar integration?
It can collect an enquiry for staff to schedule. Only present an appointment as booked when an authoritative system confirms it.
Which booking details should a confirmation contain?
Include the service, time zone, location or joining instructions, appointment reference and an approved way to change or cancel. Avoid unnecessary personal details.
What to check next
- AvailabilityUse the trusted scheduling system
- ConfirmationRecheck when the user commits
- ExceptionsRoute special requests to staff




