Holiday closure call plan
Choose the real closed window, monitoring boundary, response point, and approved alternate path first. Then adapt one of six original scripts without promising a holiday callback nobody can make.
Content updated September 6, 2026 · Original scripts reviewed August 31, 2026
Direct answer
A business holiday voicemail greeting should identify the business, state the exact closure or reduced-hours window, explain whether the inbox is monitored, set the first realistic response point, and offer one approved urgent route only when it is staffed. Add a brief seasonal closing after the operational details, not instead of them.
The COVER closure card
COVER is our pre-writing card for a temporary closure. Complete it with the person who owns the schedule and inbox, then write the shortest greeting that preserves those decisions.
Use exact dates, local time, and time zone when callers may cross regions.
Name an alternate only when it is approved, staffed, and ready for the stated requests.
Say whether messages are checked during the closure or held until the team returns.
Promise the first review or callback window the business can actually meet.
Give the exact reopening date and time, then schedule when the normal greeting returns.
Choose by operating state
| Operating state | Greeting must include | Avoid |
|---|---|---|
| Fully closed; inbox not monitored | Closure window, reopening point, delayed message review | “We’ll get back to you shortly” or an unstaffed urgent contact |
| Fully closed; limited inbox review | How often messages are reviewed and which requests qualify | A callback promise for every message during the closure |
| Reduced holiday hours | Exact open window, response window, and normal-hours return | Calling the business closed when a limited team is answering |
| On-call service available | Approved scope, staffed contact path, and routine-message option | Using “emergency” without defining an appropriate service boundary |
| Solo owner away | Personal availability boundary and the first realistic review time | Writing as “our team” or implying continuous coverage |
Six original scripts
Replace every bracketed field and read the result aloud. If the business cannot keep the monitoring or response statement, move to a different operating state before recording.
Script 01
Original“Thank you for calling [Business Name]. We are closed from [start date and time] through [end date] and will reopen on [date] at [time]. This inbox is not monitored during the closure. Please leave your name, number, and a brief reason for calling, and we will begin returning messages when we reopen.”
Decision note: Use when nobody is reviewing the inbox. The promise begins after reopening, not during the break.
Script 02
Original“You have reached [Business Name]. We are closed for [holiday] and reopen on [date] at [time]. We will review this inbox once each business day for [approved request type]. For other requests, leave your name, number, and a short message, and we will respond after we reopen.”
Decision note: Name the review cadence and scope instead of suggesting a fully staffed line.
Script 03
Original“Thank you for calling [Business Name]. Our holiday hours are [days and times] through [date]. If you leave your name, number, and [one useful detail], we will review your message during those hours. Our regular schedule resumes on [date].”
Decision note: Use when the business remains open on a smaller schedule and the inbox is actively checked.
Script 04
Original“You have reached [Business Name]. Our office is closed until [date and time]. For [specific approved urgent service] during this period, call [staffed number or approved route]. For routine requests, leave your name, number, and a short message, and we will respond after we reopen.”
Decision note: Publish the alternate path only after its owner confirms the dates, scope, and staffing.
Script 05
Original“Hi, this is [Name] at [Business Name]. I am away from [start date] through [end date] and will begin reviewing messages on [date]. Please leave your name, number, and [one useful project detail]. I will return calls in the order received when I am back.”
Decision note: Keep the voice honest and singular; do not invent a team or immediate backup.
Script 06
Original“Thank you for calling [Business Name]. We are closed on [date] and will reopen on [date] at [time]. Please leave your name, number, and a brief message. We will review messages when normal service resumes. Thank you for calling.”
Decision note: Use when a neutral, broadly accessible closing fits better than holiday-specific language.
Christmas and New Year planning
Do not leave a Christmas recording running through New Year if the office opens between them. Use separate prompts for separate closure windows; a shared festive introduction cannot explain two different monitoring schedules.
The following is an original fictional office scenario, not a public holiday calendar. Its owner chooses to close December 24–27, 2026 and January 1–3, 2027, with normal operation between those windows. Your actual business dates, time zone, and staffing must replace these facts.
Thanks for calling Cedar Lane Cleaning. Our office is closed December 24 through 27. This mailbox is not monitored during the closure. Leave your name, number, and service ZIP code. We reopen December 28 at 9 AM Pacific and begin reviewing messages at 10 AM. Thank you, and happy holidays.
Thanks for calling Cedar Lane Cleaning. Our office is closed January 1 through 3. Leave your name, number, and service ZIP code. We reopen January 4 at 9 AM Pacific and begin reviewing messages at 10 AM. This mailbox is not monitored while we are closed. Thank you.
If a voice artist records both prompts, ask whether two files, later date changes, and a reusable regular greeting are included. Use the recording quote request to make the scope clear. There is no need to hire someone if a clear self-recorded version meets the need.
When the greeting and the service disagree
Say that the business is unavailable for after-hours service, then describe when messages are reviewed. Do not add an urgent menu option merely because a template includes one. Receiving a message, reading it and dispatching someone are three different commitments. Your greeting should make only the commitments your business can keep.
“You have reached Cedar Lane Cleaning. We are closed for the holiday and reopen Tuesday at 9 AM Pacific. We do not provide after-hours service, and this mailbox is not monitored while we are closed. For a routine cleaning request, leave your name, callback number and service ZIP code. We begin reviewing messages Tuesday at 10 AM Pacific.”
Original fictional example, not a tested business recording. Replace the day with your actual reopening date before recording. This is availability wording for routine business requests, not emergency-response advice.
Suppose that greeting plays correctly, but an old “press 1” route still forwards callers to the owner’s personal mailbox. The audio is accurate; the route is not. Re-recording the same message will not remove the obsolete option. Trace the active closed-hours branch and have the authorized administrator remove or replace the route, then call the public number again. Do not change unrelated open-hours routing.
Leave a non-sensitive test message with a unique label. Record the call time and time zone, words heard, destination, and whether the assigned owner could retrieve that label. If the caller reaches a different mailbox, keep the issue open. If the message arrives but nobody can review it until later, change the stated review window or arrange real coverage before making the promise. An unanswered test is an unresolved result, not evidence that the system works.
In JustCall’s documented workflow, time rules, voicemail notification recipients and publishing are separate configuration steps. That is a product-specific example of why saving an audio file alone is insufficient; other providers use different controls. See the JustCall after-hours setup documentation (checked September 6, 2026). The comparison above is our editorial checklist, not a claim that we tested JustCall.
Use the live-line setup scorecard to record the test, then follow the inbox workflow when the team returns. If callers cannot record anything, start with message-recording troubleshooting instead of rewriting the greeting.
A worked closure rehearsal
Fictional example: a studio closes September 7, 2026, reopens September 8 at 9 AM Pacific, and starts reviewing messages at 10 AM. No one monitors the inbox while it is closed. These are sample business decisions, not a holiday schedule you should copy.
“Thanks for calling Juniper Studio. We are closed September 7 and reopen September 8 at 9 AM Pacific. This mailbox is not monitored during the closure. Leave your name, callback number, and session type. We begin reviewing messages September 8 at 10 AM Pacific and will call to discuss availability.”
Avoid “back tomorrow” in a recording that may play for several days. Replace every sample date and time together; do not update the reopening date while leaving the old review date. If a closure extends, revise the greeting, phone schedule, and restoration reminder as one change.
Use the live-line scorecard to record the resultA holiday greeting is unfinished until someone owns its removal. Record the normal greeting name, restoration date and time, responsible person, and outside-test number beside the seasonal asset.
Restoration card
Normal asset · active route · restore time · owner · outside tester · proof message
Risk check
Replace it with the first review or callback window the owner approved.
Publish an alternate only when its owner confirms coverage and scope.
Use an exact reopening date and time instead of “after the holidays.”
Do not expose a private number, name, or inbox as a seasonal shortcut.
Implementation evidence
RingCentral’s published holiday script guide notes that a voicemail greeting applies around the clock by default unless its schedule is edited. Zoom Phone documents separate business-hours and closed-hours greeting settings. Check the actual schedule and route rather than assuming the uploaded seasonal file controls both.
Sources checked August 31, 2026. Interfaces, schedules, and account permissions can change.
Generate brief, balanced, and detailed drafts from the real closure and response promise.
Open the generatorCheck dates, pace, level, clipping, and silence privately before the seasonal greeting reaches the public line.
Open the recorderTrace the active holiday state, route, prompt, and inbox when an old seasonal message survives the return date.
Open troubleshootingFrequently asked questions
State the business name, the exact closure or reduced-hours window, whether messages are monitored, the next realistic response time, and one approved urgent alternative only when it is genuinely staffed. End with one simple action for the caller.
It is optional. Use a warm closing when it matches the business voice and audience, or use neutral closure language when clarity, accessibility, or a broad customer base matters more. Operational details should come before seasonal wording.
Attach it to the actual holiday or closed-hours schedule before the closure begins, then place an outside test call. If the system has no scheduled profile, set a calendar owner and a restoration time so the seasonal greeting does not remain active.
Only when the number is approved for callers, staffed during the stated period, and appropriate for the service. Do not imply emergency coverage that the business cannot deliver, and never substitute a business greeting for public emergency instructions.
Call the public number and note the exact words and time. Then inspect the holiday schedule, closed-hours profile, auto attendant, queue, forwarding path, selected prompt, and final mailbox. Change one active layer and repeat the same outside call.