Practical guide

Prepare holiday cover without leaving the office permanently closed

Last materially reviewed 2026-09-28

Quick answerGive each temporary schedule a date boundary, an owner and a return-to-normal check.
What to know

Confirm which calendar applies

CloudTalk’s business-hours guidance distinguishes company and number-level holiday handling. A number’s registered country may affect the holiday calendar it uses. Do not infer the intended office closure from a number prefix alone; confirm the actual business requirement and the configured rule.

What to know

Write the temporary caller promise

State whether callers reach a covering colleague, a message service or a closure announcement. Avoid promising a reply time that nobody has agreed to deliver. Make the responsible person aware of the temporary route before the holiday starts.

What to know

Plan the removal too

Record when the exception ends and who verifies normal service resumes. Keep the usual configuration available for reference without overwriting unrelated rules. A temporary improvement becomes a defect when it remains active after its purpose ends.

What to know

A fictional return check

An office closes for a local holiday while a second location stays open. The administrator applies the intended exception only to the relevant line and assigns a next-day check. The second location’s normal callers are not redirected merely because both numbers share one account.

What to know

Give every exception an expiry condition

For each exceptional date, record the affected number, time zone, greeting, answering destination, owner and return condition. Distinguish a one-day closure from a recurring holiday rule so next year's service does not inherit an accidental assumption. Check whether ordinary opening hours or a separate time split takes precedence in the actual account. If the office remains partly staffed, describe which callers should reach them and which should hear the closure message. Prepare the return to normal service before the holiday starts. A covering colleague should not have to invent that decision afterward. Keep the announcement accurate: a greeting that promises callbacks requires someone to own them. This small exception record is easier to review than a collection of unlabelled temporary routing changes.

Continue when useful

Next: Change register

Record the purpose and acceptance of a route change so the next administrator can maintain it.

Open Change register →

Sources used for this page

These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.

  1. CloudTalk business hours — Merchant documentation · help.cloudtalk.io · Merchant-controlled · checked 2026-09-28
  2. CloudTalk day/time rule priority — Merchant documentation · help.cloudtalk.io · Merchant-controlled · checked 2026-09-28