Keep one approved schedule
Create a schedule that records the location, local time zone, closure start, closure end and next opening time. Include partial days and appointment-only periods rather than forcing every exception into open or closed. Give the schedule an owner and an approval date. A provider calendar may help, but your business still needs to confirm whether it trades on a particular date. Do not infer your trading hours solely from a public holiday label. A business can choose a different operating pattern, and different branches may need different instructions.
Explain what callers can still do
A closed office may still accept messages, answer basic questions or take booking requests. Write a short greeting that states the closure and the available next step. For example, a hypothetical office might say: "Our office is closed today. I can take a message for the team or help with our usual service information." Do not claim staff are available when only the automated service is answering. If a reopening time is supplied, use a date and local time that the caller can understand rather than an ambiguous "tomorrow".
Apply the exception to connected workflows
Check whether the booking calendar independently blocks the closure. Changing the phone greeting does not necessarily stop appointments being offered. Review transfer rules as well: a usual destination may be on leave or unable to respond. Callback messages should reflect the revised coverage. If a separate on-call service exists, document exactly which calls it accepts and who approved that arrangement. Keep routine enquiries out of that path. The same exception should be visible to staff so they can explain why a caller received a different response.
Test the boundaries around the change
Test just before the closure starts, during the closure and at the planned reopening. Include an overnight closure that crosses midnight and, where relevant, a location in another time zone. Use a controlled test configuration or provider-supported simulation rather than changing live clock settings. Inspect the offered appointments and transfer destinations, not just the greeting. A rule that works at midday can still be wrong at the transition. Record the expected local time and actual result so a failed test can be diagnosed without guessing which clock was used.
Plan unexpected closures separately
Staff illness, a building problem or a temporary interruption may require a same-day change. Agree who can activate a temporary closed state and how they notify the team. Keep the message factual and avoid publishing internal details that callers do not need. Record an expiry or a review time so the exception does not remain active indefinitely. If you cannot update the receptionist immediately, use your existing phone fallback and tell the responsible person. An emergency change should still have an owner, a record and a check that it reached the live line.
Verify the return to normal
After reopening, place an internal test call through the public number and confirm the normal greeting, availability and transfer behaviour. Check pending messages collected during the closure and assign them before considering the change complete. Review website hours and any other business listings that were intentionally updated. Keep the previous exception in a change history rather than leaving it mixed into the current instructions. This makes next holiday preparation easier without accidentally reusing old dates or telling callers about a closure that has already ended.