How to manage business hours, breaks and holidays on your phone system

Why phone system business hours matter

Managing business hours on a phone system means deciding in advance where a call goes based on the day and time. During opening hours it reaches your team, a queue or a menu; after hours the caller hears a message and the call takes a different route. Public holidays, company shutdowns and one-off closures are exceptions to that weekly rule.

It sounds like a technical detail, yet it is one of the first things callers notice. A phone ringing out at 1:15 pm because everyone is at lunch, or a cheerful “we’re open” greeting on Christmas Day, makes a business look disorganised. A clear message telling people when you reopen and what they can do in the meantime turns a dead-end call into a handled contact.

With an old on-premise system these changes often meant calling an engineer or remembering to divert the line every evening. With a cloud phone system you write the hours once in a web portal and the system applies them to every call on its own. If you are weighing the two approaches, see cloud vs on-premise phone systems.

Weekly schedule: time slots, lunch breaks and late shifts

Everything starts with the weekly schedule. For each day you set one or more time slots when you are open; a day with no slots is closed. A lunch break is not a special case, it is simply the gap between two slots, such as 9:00–13:00 and 14:30–18:00.

Before entering anything, write the real hours down for each team, because they rarely match the hours on your website. Support may start earlier, accounts may finish early on Fridays, and an on-call service may run through the evening.

Public holidays, shutdowns and bridge days

Exceptions are the days when the weekly schedule does not apply. An exception replaces the hours for that date: you can be closed all day or open with different slots, for example mornings only on Christmas Eve.

Holidays that fall on the same date every year are set once as recurring exceptions. Holidays that move, such as Easter and many bank holidays tied to a weekday, need a one-off exception for each year. A simple routine:

• Add fixed-date holidays once, set to repeat every year.
• At the start of each year, add the moving holidays for that year only.
• Add the company shutdown weeks, such as the summer break or the days between Christmas and New Year.
• Add bridge days and local holidays that apply only to your office.
• Add reduced-hours days with their own slots instead of closing completely.

What happens after hours: your routing options

Closing the phone after hours does not have to mean hanging up. The out-of-hours message comes first; then the call moves to a destination you choose. The right choice depends on why people usually call at that time.

The most common options, with their trade-offs:

How to write a good out-of-hours message

Keep the after-hours message short and specific. Callers want to know three things: that they reached the right place, when to try again and whether there is an alternative. Skip long introductions and filler; every extra second is time spent waiting for nothing.

A good message covers, in this order:

• your business name, so the caller knows they dialled correctly;
• that you are closed right now, and why if it helps (holiday, shutdown);
• your opening hours or the date you reopen, said plainly;
• what they can do now: leave their number for a callback, use another channel, or call an emergency line;
• a short goodbye.

Different hours for teams, numbers and IVR menus

In a company with several teams, one schedule is rarely enough. The tidiest approach is to create several schedules with clear names, such as “Office hours”, “Weekend support” or “On call”, and attach each one at the right point in the call flow.

Schedules can work at different levels. On a phone number they decide whether you are open at all; on an IVR menu they decide which options are available; on a call queue they decide when a team answers. That way support can take calls on Saturday while the sales queue sends callers to its own message.

In Robottino these schedules are called time conditions. Each one can be attached to numbers, IVR menus, queues, callbacks and feedback surveys, and outbound campaigns use them to dial only within those hours. The practical benefit is that when you change the hours, the change applies everywhere the condition is used, with no need to update each number.

Unexpected closures and emergencies: the manual switch

No calendar covers everything: an all-hands meeting, a network outage, a snow day, the on-call engineer starting early. For these moments you need a manual control that changes where calls go right away, without editing the schedule.

A switch like this has two positions: on, calls go one way; off, they go the other. You place it in the call flow, for example as the number’s destination or as the after-hours destination, and each call follows whatever state it is in at that moment.

In Robottino this is the On/Off switch. Each switch has a phone code: from any company phone you dial star and the code, hear the current state and press 1 to flip it. Whoever needs to close the lines in a hurry does not have to log in to the portal.

• Emergency closure: with the switch on, every call goes to a dedicated message.
• On-call cover: a switch used as the after-hours destination decides whether calls go to the on-call mobile or to the closed message.
• Training session: the switch sends calls to a callback request for an hour instead of the queue.

Setting up hours and holidays step by step

Here is a practical sequence that works with most cloud phone systems. The names follow Robottino, but the logic is the same anywhere.

1. Collect the real hours

   For each team, write down days, slots, lunch breaks and shifts. Ask the people who answer the phone, not only whoever wrote the hours on the website.

2. Create the weekly schedule

   Name it, switch on the open days and set the slots. Add a second slot on days with a lunch break.

3. Add the exceptions

   Enter fixed-date holidays as yearly exceptions, then moving holidays, bridge days, shutdowns and reduced-hours days for the current year only.

4. Write the after-hours message

   Short, with your hours or reopening date and an alternative. Listen to it before saving.

5. Choose the after-hours destination

   Hang up, an audio file, a callback request, a transfer to an on-call phone or an AI voice agent, depending on who calls at that time.

6. Attach the schedule

   Link it to the phone numbers, menus and queues it should control. Make sure your account’s time zone is correct.

7. Test it

   Place a test call inside and outside the hours and check the route. Repeat the test after every significant change.

Common mistakes to avoid

Most problems with phone system hours come from small oversights rather than technical limits. These are the ones you see most often:

• Forgetting moving holidays: Easter, bridge days and company shutdowns need adding every year.
• One schedule for every team, when support and sales keep different hours.
• An after-hours message that never says when you reopen, so callers keep trying at random.
• Leaving callbacks without a schedule, so they go out at night or at weekends.
• Never testing the route: an empty or wrong after-hours destination drops calls with no explanation.
• The wrong time zone on the account, which shifts every slot by an hour or more.

Frequently asked questions