Download the booking test worksheet
Define what counts as a booking
Decide whether the assistant can reserve an appointment or only take a request. If it can reserve, write down the evidence the calendar returns on success and how your team finds the entry. If a coordinator must approve, the closing script should give the response window and describe the request as pending.
Record the service duration, provider, location, time zone and buffers for the test appointment. For Google Calendar scheduling, review the settings of the actual account. Google’s appointment schedule instructions describe the booking page and scheduling settings.
Run the two-caller collision test
Set up one available slot
Offer the same Tuesday 10 a.m. slot to test callers A and B through separate sessions. Let caller A confirm first. Then let caller B accept the earlier offer.
Inspect both sides
The expected result is one confirmed calendar entry. Caller B should be offered fresh availability or a human callback. A second confirmation message with no matching appointment is a failure, even if the calendar has correctly prevented a double booking.
Repeat with a staff member taking the slot directly in the calendar after the chat starts. This catches systems that show an accurate opening once but never recheck it at confirmation.
Read back the local date and time
Give one test visitor a different time zone from the business. Ask for “Friday afternoon” and check which local date, hour and location the assistant repeats. Compare the confirmation, the business calendar and the visitor-facing message. In regions that change their clocks, use appointments on both sides of the change.
Include a service that ends just before closing and one that would run past closing when its buffer is included. The appointment length and the staff rota can make a visible gap unusable.
Try retries, rescheduling and cancellation
Interrupt the confirmation response after the calendar accepts the booking. Ask again. The assistant should recover the existing result or escalate for verification. A retry must not silently create another event.
For rescheduling, make the proposed replacement slot unavailable. Verify what happened to the original appointment before the assistant reports a change. For cancellation, test the correct customer, a different customer and a request outside the business’s change window. Check who is authorized to approve exceptions.
Record the evidence and the fallback
For each case, write down the visitor’s words, the confirmation displayed, the final calendar state and who owns a failed request. Use invented names and test contact details. Run the same cases on voice and web when both channels share a calendar, because a spoken date can be misheard even when the calendar rules work correctly.
When a case fails, change one rule and repeat that case plus its normal counterpart. A blocked change can accidentally block a valid booking. Use the launch checklist to decide who signs off and the AI receptionist service to scope an assisted booking workflow.