What Is an IVR Menu?

What it is, and where the name comes from

IVR stands for Interactive Voice Response — a voice response that reacts to the caller. It is "interactive" because the caller doesn't just hear a recording, they answer it: they press a key, and the system continues according to their choice. In Hebrew it is called a "voice menu," a "voice response" or simply "the menu."

The technical basis is tone dialing: each key on a phone produces a combination of two tones that the PBX recognizes (a method called DTMF). Once phones moved from rotary dials to keypads, it became possible to build systems that listen for keys and respond. In the past this required dedicated, expensive equipment and was the domain of banks and large companies. In a cloud PBX, an IVR menu is a standard part of the system, and even a three-person office can use it.

It is important to understand what a menu does not do: it doesn't keep the caller waiting. It directs. The waiting itself happens in the queue or the hunt group that the menu sends the caller to.

How it works — step by step

1. The call comes in to the organization's number and passes the time and caller checks (see call flow).
2. The PBX answers and plays the menu's opening message.
3. The PBX listens for keys even while the message is playing. A regular caller who knows that 2 is service doesn't need to wait for the end of the message.
4. The caller presses a key, and the PBX sends the call to the destination set for that key.
5. If they press nothing — after a few seconds the message repeats, or the call goes to a default destination.
6. If they press a key that doesn't exist — they hear "Invalid choice" and return to the menu.

The destination of each key can be almost anything in the PBX: an extension, a queue, a hunt group, a voicemail box, a recorded message, or another menu. When a key leads to another menu, you get a multi-level menu: "For sales, press 1," and then "For private customers, press 1; for businesses, press 2."

What matters here: the menu itself doesn't "know" whether anyone will answer at the destination. If key 2 leads to the extension of an employee who has gone on vacation, the menu will keep sending calls to them. That is why every destination needs its own backup plan — a voicemail box, a hunt group with several people, or a queue with a fallback destination.

How to write a good script — with examples

The script is the part that most affects the experience, and the part that is most neglected. A few examples that work:

A small business in Bnei Brak: "Hello, you've reached the bookstore. To ask about an existing order, press 1. To place a new order, press 2. For opening hours and our address, press 3. To speak with a representative, press 0." — Four options, the most common first, and a way to reach a person.

A yeshiva with a dormitory: "Hello, you've reached the yeshiva. For the yeshiva office, press 1. For the dormitory, press 2. For accounting and payments, press 3. For a student's voicemail box, press 4." — Parents don't have to guess whom to contact.

A nonprofit with a donation line: "Hello, you've reached the organization. To donate by credit card, press 1. For a donation receipt, press 2. For information about our activities, press 3. To leave a message, press 9."

Notice the structure: first the action, then the key ("For service, press 1," not "Press 1 for service"). The caller hears what they are looking for, and then knows what to press. It is a small difference that saves having to listen to the whole menu again.

Outside business hours: "Hello, you've reached the office. The office is open Sunday through Thursday, from 8:30 to 4:00. To leave a message, press 1, and we'll get back to you on the next business day. For information about our hours, press 2." — The caller knows when to call back, and has something to do right now.

Language selection: An organization that also serves English or Yiddish speakers can open with "For Hebrew, press 1; for English, press 2," and continue from each key to a menu recorded in the matching language. The language choice should be the first question, and should not come after the caller has already heard a script they didn't understand.

Types of menus

• Single menu — one level, 3–5 options. Suits most businesses.
• Multi-level menu — a key that leads to another menu. Suits an organization with several departments and sub-departments. Rule of thumb: no more than two levels.
• Menu by time — one menu during business hours and another outside them (time-based routing).
• Menu by number — each of the organization's numbers opens its own menu, for example a donation line separate from the general line.
• Number-entry menu — the caller enters a sequence of digits (an extension number, a student number), not a single key. There is a dedicated tool for this: the pattern menu.
• Information menu — a menu where every key plays a message: business hours, an address, directions, information about a class. It has no representative at all, and it works around the clock — for example, an information line for a gemach (free-loan fund).

Many organizations combine several types. A common example: during business hours, the full menu, with a key for each department and a key for a representative; outside business hours, a shortened menu that announces that the office is closed, plays the hours and offers to leave a message. The caller doesn't need to know there are two menus; they simply hear what is relevant to them at that hour.

Another useful combination: known customers get a different menu, or bypass the menu entirely and reach their contact person directly. This is done with caller-based routing, which is checked before the menu is played.

IVR menu or secretary?

This question comes up in almost every organization. The honest answer: it's not either-or. A good menu doesn't replace a person — it takes away the technical work of "who do I transfer this to," so that the person can handle the calls that really need them.

The common solution: a short menu with three or four options, and key 0 that reaches the secretary. Most callers know where they want to go and get there on their own. The secretary only gets those who didn't find what they needed — and that is usually a small part of the calls.

Common mistakes

• A long opening message — "Hello and welcome, we're glad you chose... your call is important to us..." — twenty seconds before the first option. The caller wants to get through, not to hear a speech.
• Too many options — after five options, people have already forgotten the first one.
• No way to reach a person — a caller who doesn't find themselves in the menu needs a key for a representative or the office. Without it, they press something random and end up in the wrong place.
• A key that leads to an extension nobody answers — with no voicemail box. This is the case where customers call again and again and give up.
• A "marketing" option before the main ones — "To hear our promotions, press 1" as the first option. A caller who phoned about a problem feels like they are being screened out.
• A menu that hasn't been updated — a department that closed, an employee who left, a promotion that ended. It's worth calling your own menu once a month.
• Inconsistent numbering — 0 for a representative in the main menu, and 9 for a representative in the secondary menu. Choose one convention.

Heavy-load scenarios: campaign evenings and seasonal peaks

A campaign evening at a nonprofit. On a fundraising evening, hundreds of people call within a few hours. The regular menu, with five options, slows them down. What works: a dedicated menu for the evening, very short — "To donate, press 1; for anything else, press 2" — and key 1 leads straight to a large queue of volunteers. The next day, you restore the regular menu.

Seasonal peaks at a business. A store that gets three times as many calls in the weeks before the holidays can add an option to the menu, "To check on a delivery, press 1," that plays a recorded message with the common information. Every caller who gets their answer from the message is a caller who isn't waiting in a queue.

A problem or an urgent announcement. When there is information that everyone is asking about — delivery delays, a change of event location — play it at the start of the menu, before the options. This saves dozens of identical calls.

Practical tips

• Write the script on paper and read it aloud with a clock. If the opening and the options run past 20–25 seconds, shorten it.
• Put the most common option first, even if it is "less important" in management's eyes.
• If most callers are regular customers, they will learn the keys. Don't change the order without a reason.
• Record in a quiet room, at a calm pace. Details in opening message and greeting.
• Define what happens when no key is pressed — older people, and people calling from an old phone, sometimes don't press anything at all.
• In a secondary menu, give a way back: "To return to the previous menu, press star." Someone who entered by mistake shouldn't have to hang up and dial again.

Test before you go live. After you build it, dial from a mobile phone like a customer. Go through every key and check where it leads: does the extension ring? What happens if nobody answers? What happens if no key is pressed? What happens outside business hours? Ten minutes of testing saves a week of customers getting stuck.

Pay attention to what customers ask. If a secretary gets the same question ten times a day — business hours, an address, the status of an order — that is an option missing from the menu. Add a key that plays the answer, and you save time for her and for them.

Full scenario 1: a small business — an electronics store

The short examples above show the opening. Here are three complete scripts, from the first word to the case where the caller presses nothing. You can copy them, change the names and record them. The first script: an electronics store with two salespeople, a technician and a bookkeeper.

Opening (during business hours): "Hello, you've reached the electronics store. To ask about an order or a delivery, press 1. For advice and purchases, press 2. For repairs and technical service, press 3. For accounting, press 4. For business hours and our address, press 5. To speak with a representative, press 0." — Six options is the upper limit, and here it is justified because key 5 is an information message that saves calls.

Key 1 — a message before the queue: "Please have your order number ready. We're transferring you to a representative." Then a queue of the two salespeople. Key 2: straight to the same queue, with no message. Key 3: a hunt group — the technician first, and after 20 seconds the counter as well. Key 4: the accounting extension, and if there is no answer within 25 seconds — a personal voicemail box. Key 5: "The store is open Sunday through Thursday from nine to seven in the evening, and on Fridays until one o'clock. The address is 12 Rabbi Kook Street, second floor, with parking in back. To return to the menu, press star."

Pressed nothing (after 6 seconds): the message repeats once. If they press nothing again — to the sales queue, because most people who press nothing are older customers who want a person. Wrong key: "That choice is not valid" and back to the menu, up to twice, and then to a representative.

Outside business hours: "Hello, you've reached the electronics store. The store is currently closed. Our hours are Sunday through Thursday from nine to seven, and Friday until one. To leave a message, press 1, and we'll get back to you on the next business day. For business hours and our address, press 2." — Note that the message says "closed" early, so the caller doesn't wait for a menu that isn't coming.

Full scenario 2: a yeshiva office with a dormitory

The yeshiva gets calls from three types of callers: parents, suppliers and institutions, and students calling from outside. The menu has to serve all three, without the parent hearing about suppliers and without the supplier searching for the office among voicemail boxes.

Opening: "Hello, you've reached the yeshiva. For parents, press 1. For the yeshiva office and suppliers, press 2. For accounting and payments, press 3. To leave a message for a student, press 4." — Four options, with parents first because they are most of the callers.

Key 1 — a secondary menu for parents: "For the dormitory and the mashgiach (dormitory supervisor), press 1. For registration and the secretary's office, press 2. For hours when you can reach the students, press 3. To return to the main menu, press star." Key 1 in this menu reaches the dormitory desk, which during seder time (study session) doesn't ring but plays: "It is currently seder time. Contact hours are one to two in the afternoon, and nine-thirty to ten at night. To leave a message for the mashgiach, press 1."

Key 2: the secretary's office hunt group (two extensions), and after 20 seconds the office manager's mobile extension joins. Key 3: the accounting extension, with a short message before it rings: "You can also pay by credit card on the yeshiva's website." — one sentence that reduces some of the calls. Key 4: a pattern menu: "Enter the student's number followed by the pound key," and the message goes to his personal voicemail box.

Pressed nothing: the menu repeats once, and then to the secretary's office. Night (after 10:30 PM): "You've reached the yeshiva. The office is closed. To leave a message for the office, press 1; to leave a message for a student, press 4. In an emergency, press 9." — Key 9 reaches the mobile phone of the staff member on duty, and it is the only key that rings at night.

Full scenario 3: a nonprofit's donation line

A donation line is different from the previous two: most callers want one thing, and on a campaign evening there are very many of them. So there are two scripts for the same number — regular and campaign — and you switch between them in the control panel.

Regular script: "Hello, you've reached the organization's donation line. To donate by phone, press 1. For a receipt or to ask about an existing donation, press 2. To sign up for a standing order, press 3. For information about the organization's activities, press 4. For any other matter, press 0." Key 1 leads to the donors queue; key 2 to the secretary's extension; key 3 to the same queue with the message "We're transferring you to the standing-order coordinator"; key 4 to a one-minute information message.

Campaign evening script: "Hello and welcome to the campaign. To donate, press 1. For anything else, press 2." — one sentence, two options. Key 1 to the large volunteers queue; key 2 to the extension of a single coordinator. Pressed nothing: straight to the donations queue, without repeating the message. On an evening like this, every second of menu is a donor waiting.

The queue hold message on a campaign evening: "Thank you for calling. All volunteers are currently speaking with donors. Please hold, and we will answer you shortly." And after a minute: "To leave your number and get a call back from the next volunteer who becomes free, press 1." — A callback is what keeps a donor who has waited three minutes from hanging up and forgetting.

Multi-level menus: when to use them, and how not to get lost

A secondary menu is born when one department splits. "For sales, press 1," and then "For private customers, press 1; for businesses, press 2." This is right when the two sub-departments have different people. It is not right when the same two salespeople answer both — then the second level only causes delay.

• Two levels at most. At the third level, the caller no longer remembers how they got there, and if they make a mistake, they hang up.
• A short name for each sub-menu. "Sales menu," "Parents menu." In the control panel they appear as a list, and a clear name prevents connecting a key to the wrong menu.
• Star goes back, at every level. The same key, the same meaning. Someone who learned it once always knows it.
• The same digit for a representative at every level. If 0 is a person in the main menu, 0 is a person in the secondary menu too.
• The first sentence in the secondary menu confirms the choice. "Sales department: for private customers, press 1." The caller knows they are in the right place.

A rule of thumb for the total number of options: if the combination of all keys at all levels goes over 12 destinations, some of them probably should be a pattern menu (entering an extension number) or caller-based routing (regular customers who skip everything).

Where callers drop off — reading the log

A menu is not tested in the recording but in the call log. In the log you see the path each call took, and from that you can learn, without a survey and without guessing, where people give up. Five things to look for:

1. Hanging up during the message, before any key. If more than a tenth of the calls end within 10–15 seconds with no key pressed, the message is too long, or the callers were looking for a person and didn't hear "For a representative, press 0" early enough.
2. A key that almost nobody presses. An option that gets one percent of the calls takes up space and makes the message longer. Delete it, or move it to the end.
3. Many "invalid choice" results. Callers are pressing a key that doesn't exist. They are usually trying 0 or 9 when the menu didn't offer them.
4. A key that leads to voicemail most of the time. Its destination isn't answering. The problem isn't in the menu but in the group or the extension behind it.
5. The same number calling three times in ten minutes. They reached the wrong place and tried again. If this repeats with different callers, the script is misleading.

A benchmark that helps you get oriented: in a good small-business menu, most callers press a key within 8–12 seconds, that is, before the message is over. If the average time until the key press approaches the length of the whole message, callers don't understand it the first time and wait to hear everything.

Checklist before you record

• Every option begins with the action and ends with the key ("For service, press 2").
• The most common option is first; a key for a representative exists and is mentioned.
• The opening, up to the first option: under 5 seconds.
• Every key has a tested destination, and every destination has a backup for when nobody answers.
• What happens with no key press and with a wrong key has been defined.
• There is a separate script for outside business hours, and it includes the business hours.
• The menu has no employee's name that might change — "for accounting," not "for Sarah."
• There is no promotion, date or price that will be out of date within a month.
• Recorded in a quiet room, at an even pace, with the same voice in all menus.
• Someone who didn't build the menu dialed in and went through every key.