Using Call

Setting Up IVR and Business Hours in Call: A Step-by-Step Plan

Plan a phone menu and business hours before you click: menu design, hours and holidays, closed-hours behaviour, queues, testing and how to change it safely.

Call editorial team · Published · 6 min read

A phone menu is only as good as the rules behind it. The menu itself is a short script; the real work is deciding who answers at which time and what happens when nobody can. This guide takes the planning order that avoids rework: design, hours, queues, closed-hours behaviour, then testing.

A manager sketching a phone menu on a whiteboard in an office
Illustrative image

If you are new to the idea, read What Is IVR? first. For design principles, IVR menu design and common IVR mistakes go deeper than this walkthrough.

Plan the menu on paper

Before opening any settings, write down the five most common reasons people call you. Each reason becomes a menu choice only if it needs a different person or a different answer. Two to four choices is a good ceiling; more than that and callers stop listening.

A menu plan in five lines

  1. GreetingThe business name in one short sentence.
  2. ChoicesTwo to four options, the most common first.
  3. Way to a personOne key that always leads to someone, or to a message.
  4. No inputRepeat the choices once, then route to the way out.
  5. ClosedA short message with hours, then voicemail or a callback request.

Write the wording exactly as it will be spoken. Prompts that read well on paper often sound stiff aloud, so read them out loud to a colleague. Recording prompts or using text-to-speech covers the options.

Set business hours properly

Business hours answer one question: can a caller be put through to a person right now? Outside them, the system says nobody can come to the phone and either keeps helping or takes a message.

Holidays and emergency closures

Regular hours are not enough. Public holidays, staff events and bad weather all need a plan. In Call, closures are kept on a holiday calendar: you add a date and a name, and queues that use that calendar close on that date. An emergency closure, which makes every queue play a closure message until it is lifted, is switched on and lifted by the platform operator; agree in advance who contacts them and keep your closure message ready.

The detail of designing around dates is covered in Routing Calls by Business Hours, Holidays and Closures.

Queues and what happens when they are closed

A queue holds waiting calls and decides who is offered them. Each queue has its own hours, a timezone, a holiday calendar and a closed greeting. When a queue is closed you choose one of two behaviours: take a message, or send the call to an overflow queue. Routing settings add a required skill, how long an agent's phone rings and what callers hear before they are connected.

Two ways to handle a closed queue

Take a messageSend to an overflow queue
Suited toTeams with a fixed day and a clear next morningTeams with a second desk, site or time zone
Caller experienceHears hours, leaves detailsReaches someone, possibly a different team
RiskMessages pile up unreadOverflow team lacks the context
NeedsA daily owner for messagesAgreed handover rules and skills

Whichever you choose, say it aloud in the closed greeting. "We are closed until nine tomorrow. Leave a message after the tone and we will call you back" is better than silence or a click.

Wording and length of prompts

Callers judge a phone menu in the first ten seconds. Keep the greeting to one sentence, put the action before the key ("for opening hours, press one") and avoid internal names for teams. Callers do not know what "customer success" is, but they know what "an existing order" means.

Keep the total spoken length of the first menu short enough that a caller can hear all of it without losing track. If you cannot say the choices in about twenty seconds, you have too many or the words are too long. Pause briefly between choices, and never make a caller listen to the whole menu before they may press a key; allowing a key press during the prompt helps regular callers.

Remember the people who call often. They learn the menu quickly and want to skip ahead, so avoid changing key numbers without a good reason. When you must change them, say so in the greeting for a few weeks.

Give every branch an ending

Walk through the plan and finish each branch: choice one goes to the sales queue, choice two to support, the way out to a general queue during the day and to voicemail or a callback request at night. If a branch has no ending, a caller will find it. See Letting Callers Reach a Person Quickly for why the way out matters so much.

Test before you announce the number

Test plan for a new menu

  • Call during business hours and choose every option once
  • Call outside business hours and check the closed message
  • Set a test holiday and confirm the queue closes
  • Stay silent on the first menu and check the repeat
  • Press a key that is not in the menu
  • Ask for a person and check who rings and how long
  • Leave a voicemail and confirm it appears where you expect it
  • Check who will ask the platform operator to switch on and lift an emergency closure

Use the same list again whenever you change hours or wording; a fuller IVR testing checklist is available if you want a longer one.

Change it safely over time

Treat menu changes like small releases. Change one thing at a time, test it, and note the date. Avoid editing at the start of a busy period. After a few weeks, read the call history for how callers actually used the menu; the options nobody chooses can go, and a pattern of callers asking for a person is a sign the choices need rewording. IVR analytics explains what to look at.

One more habit pays off: keep a copy of the current menu script, the hours and the holiday dates in one shared document that the whole team can open. When a caller says the menu told them something odd, the first question is always what the menu says today. A single page that answers that saves a surprising amount of time, and it makes handover to a new colleague much easier.

Doing it in Call

In Call, business hours are set on the phone line, under Settings, Phone lines, then the line's Business hours, or at the first step of the setup wizard. Queue hours, the closed greeting, the holiday calendar and overflow are set from Calls, Queues and SLA, by pressing Configure on a queue. Holidays are under Inbound ops; the emergency closure is switched on and off only by the platform operator. Voicemail on a queue can be turned into a callback entry by the person who reads it. Only owners, administrators and managers can change these settings.

Frequently asked questions

Should I set hours on the line or on the queue?

Line hours decide when a caller who asks for a person can be put through. Queue hours decide when a queue is open and what a closed queue does. Set both and check they agree.

What happens to calls outside business hours?

The caller hears that nobody can come to the phone. Depending on your setup the line keeps helping, takes a message or sends the call to an overflow queue. Test the exact behaviour yourself.

How many menu options should I have?

Two to four is a sensible limit. If you need more, group related choices behind one option or ask whether a voice agent would suit you better.

How do I handle holidays?

Add each date to a holiday calendar and attach the calendar to the queues that should close. Do this for the whole next year at once, then check it each autumn.

Can I close everything at once in an emergency?

Yes, through the platform operator. They switch on the emergency closure, and every queue plays the closure message until they lift it. Agree in advance who contacts them, and keep your closure message ready.

Who can change these settings?

Owners, administrators and managers. Ordinary members can use the system but cannot change lines or queues.

Set up business hours and a phone menu in Call

In the demo console you can try incoming calls in a simulation.

Related guides