A receptionist works correctly all week and starts offering closed-office appointments after a holiday change. The new business hours reached one configuration surface but not the scheduling rules used by the phone workflow.
Holiday readiness needs an end-to-end check across answering, availability, escalation, and customer messages.
Separate answering hours from service availability
A business may answer calls while the office is closed without offering visits during that closure. Staff availability, call coverage, and appointment availability are different schedules.
For a fictional service company, the AI may collect requests all day on a holiday while dispatch resumes later. Its greeting should not turn that request capture into a same-day attendance promise.
| Holiday configuration | Check to perform |
|---|---|
| Phone coverage | Does the intended route answer? |
| Booking calendar | Are closures and exceptions reflected? |
| Human escalation | Is the advertised contact actually staffed? |
| Confirmation messages | Do they state the correct date and hours? |
Test dates on both sides of the change
Use fictional calls for the final working day, the closure itself, reopening, and the next ordinary week. Include a caller whose local date differs from the office's date.
Check recurring schedules and temporary exceptions separately. A recurring weekly opening rule can remain correct while a one-off closure is missing.
Inspect the saved event and the reminder, not just the offered slot. A time-zone error in the message can still undermine a correctly saved appointment.
Keep business knowledge and calendar rules aligned
An approved holiday-hours document and a calendar configuration need an owner and a change checklist. The receptionist's answer should not rely on an old website paragraph when operations has approved different hours.
If your integration caches availability or business information, define how the change becomes active. Calendar change notifications can help, but your workflow still needs processing and reconciliation. Google's push-notification guide describes its provider mechanism.
Include rollback and staff review
Record the previous configuration and the effective period. If testing finds an error, restore the intended approved rule rather than improvising a new schedule during live calls.
Have a staff member inspect a small test matrix before the change goes live. Repeat the check when the temporary exception expires so the office does not remain closed in one system indefinitely.
The booking audit-trail guide provides a useful record of what changed and why.
Holiday testing questions
Can the AI answer while appointments are unavailable?
Yes, if it describes the supported request and follow-up workflow accurately.
Should the website be the only source of holiday rules?
Use the business's approved source and keep configuration changes consistent with it.
What should a pilot demonstrate?
Show closure, reopening, and escalation cases in the release checklist.