Business Hours, Holidays and Closures in Call
How to set opening hours, lunch breaks and public holidays, and prepare for an emergency closure, so callers always hear the right thing.
Most missed calls are not missed because nobody cared. They are missed because the phone system believed the office was open, or closed, when it was not. A holiday that was never entered, a lunch break nobody remembered or a storm closure announced by email but not on the line all produce the same result: a caller who is routed wrongly and does not call again.

This guide explains the three layers that keep a phone line honest about time, what to say in each state, and how to test them. It finishes with where each setting lives in Call. For background on the approach, see Routing Calls by Business Hours, Holidays and Closures.
Three layers of time
It helps to treat opening time as three separate layers, because they change at different speeds and are owned by different people.
The three layers
- Daily scheduleThe regular week: opening and closing times for each day, including breaks. Changes rarely.
- Holiday calendarDates when you are closed even though the weekly schedule says open. Changes a few times a year.
- Emergency closureA switch for the unexpected: power cut, storm, system problem. Used within minutes, rarely.
When the layers disagree, the rule is simple: the most specific and most urgent layer wins. An emergency closure beats a holiday entry, and a holiday entry beats the weekly schedule. Keeping that order in mind makes later troubleshooting much easier.
The daily schedule
Start with the regular week. Write down, for each day, the times at which a person can really pick up the phone. Not the times the shop is open to visitors, and not the times the manager would like staff to be available, but the times someone will actually answer.
Time zones
Always set the time zone explicitly. A line that serves callers in one place but is managed from another will otherwise open and close at the wrong hour. If you run several sites in different zones, give each queue its own hours in its own zone.
Lunch breaks and split days
A day with a gap in the middle needs two sessions. Without the gap, calls are sent to desks that are empty at midday. Two sessions per day cover the usual cases: a morning and an afternoon, or an early shift and an evening one. Days with no sessions count as closed all day.
Opening early and closing late
Staff need a few minutes to log in and a few more to finish the last call. If your public hours are nine to five, consider routing calls to people from five past nine and stopping a few minutes before five, so that the last caller is not answered by someone already putting on their coat.
Setting the weekly schedule
- List real answering timesWrite the hours someone will truly answer, day by day.
- Choose the time zonePick the zone the hours are read in.
- Enter sessionsAdd one session per day, or two when there is a break.
- Copy and adjustCopy Monday to the other weekdays, then fix the exceptions.
- Save and testPlace a call before and after closing time.
Holidays and planned closures
A holiday calendar is a list of dates on which a queue is closed whatever the weekly schedule says. Enter them once a year, for example in January, and review them each quarter. Include the days that are easy to forget: regional holidays, the days between a holiday and a weekend, staff training days, annual stocktakes and office moves.
- Enter public holidays for every place you operate, not just the head office.
- Add planned closures, such as a training day, as soon as they are agreed, not the week before.
- Use separate calendars if different queues close on different days.
- Check the calendar attached to each queue; a holiday entered but not attached does nothing.
Emergency closures
An emergency closure is different from a holiday: it is switched on with no warning. When a storm, a power failure or a system outage means nobody can answer, you want every queue to say so within seconds, without editing each one in turn. In Call, the emergency closure is switched on and lifted by the platform operator, not by your own team, so agree in advance who contacts them.
Prepare the message in advance, because nobody writes well under stress. Keep it short, honest and useful: say that you cannot take calls right now, say what the caller can do instead and, if you know, when you expect to be back. Do not promise a time you cannot keep.
Planned closure vs emergency closure
| Planned (holiday) | Emergency | |
|---|---|---|
| When it is set | Days or weeks ahead | Within minutes, on the day |
| Message | Dates and reopening day | Short apology and what to do now |
| Who sets it | Whoever owns the calendar | The platform operator, when you ask |
| Ends | Automatically after the date | When the platform operator lifts it |
Remember that an emergency closure does not end by itself. Put a line in your incident checklist that says who asks the platform operator to lift it, and when.
What callers hear while you are closed
The closed state is where many phone systems fail the caller. Think about what a person calling at eight in the evening needs. They want to know that you are closed, when you reopen, and what they can do now.
- State clearly that you are closed, and give the next opening time in plain words.
- Offer a way to leave a message, so the call is not wasted.
- For urgent matters, give a real alternative, such as an emergency service or an on-call route. Do not invent one.
- Keep it under about fifteen seconds, and avoid reading out every day of the week.
Sample wording: "Thank you for calling. We are closed at the moment and will reopen at nine tomorrow morning. Please leave your name, number and a short message after the tone and we will call you back." For voicemail follow-up, see Per-Queue Voicemail in Call: Setup and Follow-Up and, for the wider topic, After-Hours Call Handling for Small Businesses.
A test routine
Time rules are easy to get wrong and hard to notice, because they only misbehave outside the hours you are watching. A short routine catches most mistakes.
Before each holiday season
- Place a pretend call at a time just before closing and just after
- Check the lunch break: does a call at midday go where you expect
- Confirm each holiday date is attached to the right queues
- Listen to the closed message once, out loud, as a caller would
- Confirm someone knows how to reach the platform operator to switch on or lift an emergency closure
Do this after any change, not just once a year. A small edit to Monday's hours is exactly the kind of change that quietly breaks Friday.
Setting it up in Call
Call keeps time rules in more than one place, and it is worth knowing which does what.
- Queue hours: under Calls, Queues & SLA, press Configure on a queue and open the Hours tab. Choose the time zone, set opening and closing times for each day, choose what happens when closed (take a message or send to the overflow queue), write the closed greeting and pick the holiday calendar. With no hours set at all, a queue takes calls at any time.
- Line business hours: under Settings, Phone lines, each line has business hours that decide when a caller who asks for a person can be put through. You can add a second session for a lunch break, and copy Monday's hours to the other weekdays. Outside those hours, the AI agent says nobody can come to the phone and keeps helping. These hours are not read out to callers.
- Holidays and emergency: under Calls, Inbound ops, the Holidays and emergency area lets you add a closure with a date, a name and a calendar, and remove it again. An emergency closure is switched on and lifted only by the platform operator; while it is on, every queue plays the closure message. Agree in advance who contacts the operator, and keep your closure message ready.
After any change, open the routing simulator in Inbound ops, pick a queue and run it to see, step by step, where a call would go. Nothing is dialled. Only owners, administrators and managers can configure queues. For the surrounding setup of menus and queues, see Setting Up IVR and Business Hours in Call.
Frequently asked questions
What is the difference between line business hours and queue hours?
Line business hours decide when a caller who asks the AI agent for a person can be put through. Queue hours decide when a queue takes calls and what a caller gets outside them. Set both so they agree.
How far ahead should I enter holidays?
Enter the whole year at the start, and review it every quarter. Add one-off closures, such as training days, as soon as they are agreed.
Do I need to read the opening hours to callers?
Not always. Many callers only need to know when you reopen. A short message with the next opening time is usually clearer than reading out the full week.
What should an emergency closure message say?
Say that you cannot take calls now, tell the caller what to do instead, and give a reopening time only if you are sure of it. Prepare the wording before you need it.
Why did a call go to the wrong place after a holiday?
Common causes are a holiday date not attached to the right queue, a time zone mismatch, or an emergency closure that was never lifted. A pretend call through the routing simulator usually shows which.
Can different queues have different hours?
Yes. Each queue has its own hours and holiday calendar, which suits teams in different places or teams that work different shifts.