Prepare a dated holiday phone message

The decision this workflow supports

Holiday hours often change independently of the regular weekly schedule. A temporary message becomes a problem when it remains active after the holiday or when the website and phone give different answers about the same date.

Put the review process in place

Create one dated change record covering the holiday, affected service and approved wording. Assign both an activation check and a removal check. Keep a copy of the normal schedule so the reviewer can restore it without reconstructing the previous answer.

Worked example for your team

Suppose the owner approves a shorter lunch service for one named holiday but leaves the following day unchanged. Make two fictional calls that differ only in their date. The holiday call should receive the shorter schedule, while the next-day call receives the normal one. Then inspect the website footer and phone answer after the exception expires. If either still carries the holiday wording, the change is unfinished. Keep the removal task assigned to a person rather than assuming that a date written in a document will remove the message automatically.

Sample wording to approve

“For the date you mentioned, the restaurant has a special published schedule. I can share that schedule, or pass an unanswered question to the team for confirmation.” This wording is a draft for the restaurant owner to approve before use.

Fields for the staff handoff

Staff need holiday date, affected service, approved opening and closing information, change owner, and removal date. Mark uncertain details explicitly and keep the requested action separate from anything restaurant staff have already confirmed.

Acceptance tests before use

A call about the holiday uses the exception. A call about the following week uses normal hours. The temporary message disappears after the manager’s chosen expiry. Record the observed result, assign any mismatch, and repeat the affected scenario after correction.

Related guides