Most phone systems route calls on a simple time-of-day schedule. Open at 9, close at 5, weekends off. That works for about 340 days a year.
The other 25 are the problem. A Tuesday that is closed for a federal holiday. A half-day before Thanksgiving. An unexpected snow day. A religious holiday that shifts on the calendar every year.
On any of those days, a customer dials in and the auto-attendant tells them the office is open, because the schedule says 9 to 5 and no one updated it last night.
Holiday-Aware Routing is the thing we built so no one has to update it last night.
What It Does
A Holiday-Aware Schedule is a list of dates attached to a routing rule. On those dates, the rule follows a different path. A custom greeting. A different after-hours destination. A forward to an answering service. Voicemail. Whatever the office needs.
Every auto-attendant, hunt group, call center, and extension on the platform can point at a schedule. Point them at the same one, and the whole office respects the same holidays automatically.
One calendar. Every call path follows it.
What You Can Load Into It
Three kinds of dates, mixed freely.
Federal holidays. The ten US federal holidays. Pre-loaded. Updated every year so you never have to renumber a date.
Religious holidays. Christmas. Good Friday. Easter Monday. Yom Kippur. Rosh Hashanah. Eid al-Fitr. Eid al-Adha. Diwali. Whatever your office observes. Pick from a list, or add your own. The system tracks the moving dates year to year so a religious holiday that falls on a different Tuesday next year does not break your schedule.
Custom office days. The half-day before Thanksgiving. The annual staff retreat. An office-closed-for-training day. A weather closure you declare at 6 AM and clear by 3 PM. These are the ones that catch most schedules out. Holiday-Aware Routing treats them the same as any other date on the list.
How It Gets Configured
In the admin portal under Schedules. Create a schedule, name it something like Main Office Closures, pick dates from the pre-loaded libraries, add your own custom ones. Save.
Then attach the schedule to any routing rule. An auto-attendant's day greeting points at normal hours and a holiday greeting points at the schedule. A hunt group skips ringing on holidays and sends straight to voicemail. A weekend call center stays off on Christmas even though the rest of the week is on.
One schedule, attached to everything. Add a date once, every path that touches that schedule updates.
Multi-location offices with different holidays get different schedules. Your Dallas office closes for Good Friday. Your New York office does not. Two schedules, each attached to the right set of routing rules. No branching logic, no duplicated greetings.
1. Build the calendar
In the admin portal, open Schedules and create one. Name it something like Main Office Closures. Pick federal holidays from the pre-loaded list, add the religious holidays you observe, then add custom dates (the half-day before Thanksgiving, the annual retreat, a weather day).
2. Attach it to the routing rules
Point the auto-attendant, hunt group, call center, or extension at the new schedule. The day greeting runs normal hours. The holiday greeting runs on dates from the schedule.
3. Verify with a test call
Temporarily add tomorrow's date to the schedule, call the main number, and confirm the holiday path plays. Remove the test date when done. Thirty seconds of verification, zero surprises on the real holiday.
4. Done. For every year going forward
Federal holidays update automatically. Religious holidays with moving dates track year to year. Custom dates carry forward. Add a new closure once, every routing rule that touches the schedule updates.
Who Needs This
Medical offices are the ones who ask for it first. A small practice observes different holidays than the hospital next door. The office closes the day after Christmas every year but the schedule never changes on its own.
Patients who call on December 26th hear the wrong greeting, leave a message on a mailbox nobody is checking, and show up irritated at the next visit.
Accounting firms need it during tax season. Normal hours shift to 7 AM starts and 8 PM ends from January through April. After April 15, hours go back to regular, and the firm takes off every Friday through August. A single time-of-day schedule cannot describe that. A schedule with date-based overrides can.
Multi-location companies with regional holidays. A chain with an office in Toronto and one in Atlanta. Canadian Thanksgiving, American Thanksgiving, Victoria Day, Memorial Day. Different dates, same phone system, schedules handle it cleanly.
Any office that takes floating holidays, observes religious holidays, closes for weather, or runs a half-day before a major event. Which, once you start listing them, is most offices.
Snow days are the killer app. The office manager declares a closure at 6 AM, adds today to the schedule from a phone, and every auto-attendant, hunt group, and call center on the account flips to the closure greeting in one action. No logging into each rule, no forgetting the after-hours override on the back-office number, no waiting for the one person who knows the portal.
What It Does Not Do
Predict the future. Send you reminders. Tell you what holidays you should close for. Integrate with your employee PTO system.
It is a schedule. A very flexible schedule. It gets the right greeting on the line on the right day. It does not pretend to be anything else.
We did not frame this feature as AI-powered because it is not AI-powered. Nothing about it needs to be. It is a data structure, a UI to edit it, and a routing engine that reads it at call time. The problem it solves is coordination, not intelligence.
Why We Built It
Because we got tired of customers calling us on the Monday after Easter or the Friday after Thanksgiving, telling us the office was closed but the greeting said it was open, and asking whether we could do something about it.
For a while the answer was log into the portal and update your after-hours override. That answer works if the person who knows the portal is in the office. It does not work when the one person who manages the phone system is also on vacation, or when the closure is declared at 6 AM and nobody thinks about the phones until noon.
Holiday-Aware Routing is the answer where you never think about it again. Load the calendar once, attach it to the routes once, and the phones handle the rest. Every year, every location, every closure.
A phone system should know when the office is closed. This one does.
About Vocatech
Vocatech is a business phone service built on Cisco BroadWorks with our own platform layered on top. Callpop for desktop caller context. Reports with AI transcription and summaries. Textdock for SMS and WhatsApp from your business number inside Cisco Webex. A custom integrations workshop that connects any CRM or tool you already use.
Flat $29.95 per seat. Month to month. Founded 2008. Over a thousand businesses. 97% retention.
Start a trial at vocatech.com/contact or see the platform at vocatech.com/platform.