Holiday routing overrides
How to set holiday call routing without changing normal hours
By ByTomorrow · Published
A temporary holiday change can outlive the holiday if someone edits the normal weekly schedule and forgets to restore it. The greeting, transfer destination and appointment availability can also disagree.
Use a dated exception record while preserving the ordinary schedule. This worksheet is an editorial operating procedure; the implementer must confirm which controls exist in your phone and calendar tools.
Where mistakes enter
Check these failure points
Several schedules are treated as one
Answering hours, staff transfer coverage and bookable appointments may live in different systems. Changing one does not prove that the others changed.
The exception has no end condition
“Closed for the holiday” is incomplete configuration. The effective time, time zone, expiry and restoration owner all matter.
Practical working sheet
Use this procedure with your own records
Override worksheet
Record exception name; affected phone route; local time zone; start timestamp; end timestamp; normal schedule reference; approved greeting; permitted transfer destination; fallback; authorizing owner; restoration owner. Specify whether the end timestamp is the first instant normal behavior resumes.
A fictional closure
Example: one office closes for a fictional training day. Calls still receive the approved message, live staff transfer is unavailable and ordinary inquiries go to the owned review queue. The next staffed period is stated only if approved. This example makes no claim about any real holiday or company schedule.
Check calendars separately
HighLevel documents date-specific calendar availability separately from weekly hours. If that system is used, verify the intended date exception without assuming it changes phone routing. Review existing appointments independently; a closure announcement does not itself cancel them.
Boundary test card
Test immediately before the exception, at its start, during it, at its end and in the following ordinary period. Record expected greeting, route and bookable availability for each time. Use supported test controls or an authorized test schedule, not a false production date.
Restoration and expiry check
The owner should verify that normal routing and wording resume at the agreed time. If the provider lacks automatic expiry, assign an explicit restoration task and an independent check. Keep the previous working settings available for rollback.
Apply and verify
Test the complete behavior
Capture the normal configuration
Record enough detail to compare and restore it without guessing.
Approve the dated exception
Resolve time zone, coverage and caller wording before implementation.
Apply only the intended scope
Have the authorized implementer update the affected controls and document which systems were changed.
Check the caller and booking experience
A correct greeting does not prove a correct transfer or appointment schedule.
Close the exception after verification
Record the observed restoration and any unresolved callbacks from the closed period.
Questions
Straight answers.
Prefer a date-specific exception where the system supports it. HighLevel documents separate calendar exceptions; the appropriate phone control must be verified for your setup.
Do not assume so. Check existing appointments and handle any necessary changes through their own authorized process.
The after-hours guide chooses caller branches. This worksheet manages a temporary configuration across start, expiry and restoration boundaries.
Sources and further reading
- HighLevel date-specific calendar availability
HighLevel separates date-specific calendar exceptions from weekly hours. This documentation concerns calendar availability, not automatic synchronization with a phone agent.
Checked .
- Retell transfer-call options
Retell distinguishes cold, warm and agentic warm human transfers and documents destination and timeout settings.
Checked .
Choose one behavior to verify
Bring the relevant route, script or worksheet to a scoping conversation. Agree on the expected result and the evidence before changing the working system.
Discuss your workflow