What is IVR? How phone menus work and when to use one

IVR stands for interactive voice response. It is the automated part of a phone call that plays a greeting, offers a menu and sends the caller where they asked to go. Most people know it as “press 1 for sales, press 2 for support”. Twilio’s glossary also calls it a phone tree.

An IVR system is worth having when one phone number has to reach more than one team. It is not worth having when one person answers every call. This guide covers how an IVR works, when it helps, when it hurts, how to design a three-option menu, and a script you can copy.

How does an IVR system work?

A call arrives, the system plays a recorded or read-out greeting, the caller presses a key, and the system sends the call to the destination linked to that key. Older systems and many current ones read the keypad tones (DTMF). Some also accept spoken answers, which needs speech recognition on top.

1. The call arrives on your business number.
2. The greeting plays. It is either a voice recording or text read out by a synthetic voice.
3. The caller presses a key. Each key is tied to a destination: a team, a person or a recorded message.
4. The call is sent there. If the team is busy, the caller waits in a queue. If nobody presses anything, a default destination takes the call.

The menu only decides where the call goes. What happens next depends on your call queue. If you want to see how calls are shared between agents once they are in a queue, read call queues and ACD explained.

What is an IVR menu tree?

A menu tree is the map of options a caller can choose from. A one-level tree has a single set of keys. A multi-level tree sends the caller to a second menu after the first key press, and sometimes a third.

Start with one level. Add a second only when a real group of callers cannot be served by it, and test it with someone outside the company first.

When should you use an IVR?

Use an IVR when callers need different people and a receptionist would otherwise spend the day transferring calls. Skip it when one team handles everything, because the menu then adds a step with no benefit.

• You have two or more teams on one number. Sales, support and accounts are the usual split.
• You have branches or departments. A clinic with a booking desk and a lab, or a school with admissions and a bursar.
• You get a fixed set of repeat questions. An opening-hours message or a pickup address can be played without an agent.
• Calls arrive when nobody can answer. A menu with a clear message beats endless ringing.

When does an IVR hurt callers?

An IVR hurts when the menu is longer than the caller’s patience, when none of the options fits the question, or when it is a wall between the customer and a person. Twilio’s glossary notes that poorly designed menus frustrate callers, which is why some systems add speech recognition.

• More than five options. Callers forget the first ones by the time the list ends.
• Options named in your internal words. Callers say “my order”, not “fulfilment”.
• No way to reach a person. Always give a key, or a default, that ends at a human.
• A long greeting before the options. The caller has called to be helped, not to hear the company history.
• A menu that is out of date. A key that sends calls to a team that no longer exists is worse than no menu.

How do you design a three-option menu?

List the three reasons people call most, put the biggest one on key 1, name each key by what the caller wants and keep the whole greeting to about twenty seconds. Three keys are enough for many small teams.

1. Pull the last month’s calls. Count the reasons people called. Pick the top three.
2. Order by volume. The most common reason goes on key 1, so the largest group hears its option first.
3. Name each key by the caller’s goal. “To book a delivery, press 1” beats “For logistics, press 1”.
4. Use one sentence pattern. “To do this, press 1” for every option, so callers learn it in the first two.
5. Pick a default. Decide where the call goes if nobody presses a key. It should be a team that can handle anything, not a dead end.
6. Test it with someone outside the company.

Sample IVR script

Here is a greeting for a small shop with orders, support and accounts. It runs about twenty seconds when read at a normal pace.

The script leaves out the slogan, the opening-hours speech and any fourth option. If callers need your hours, give them a key of their own or put them in your WhatsApp profile.

How does the SautiDesk phone menu work?

SautiDesk’s phone menu is one level with keys 1 to 9. Each key sends the caller to a queue. You write the greeting as text that is read out, or upload a recording as an MP3 or WAV file up to 60 seconds, and you choose a queue for callers who press nothing. You can switch the menu on or off. When it is off, calls ring the queue you have chosen instead.

Because each key points to a queue, a menu with three keys needs three destinations. SautiDesk Basic includes 1 queue and SautiDesk Pro has as many as you need, so a menu that splits callers across several teams needs Pro.

What happens after the caller presses a key?

The call goes to the queue behind that key and rings the agents in it. The ring order is set per queue. SautiDesk offers five: longest idle, take turns, fairest by talk time, ring everyone, and the same order every time. An agent on a break is not rung.

If nobody answers, the call is not lost. Each missed call becomes a ticket with an owner, so the caller still gets a call back. Every call, WhatsApp chat, SMS and email from one customer lands on the same ticket on the help desk, so the agent who rings back sees the history. The call centre software page shows the whole call flow.

IVR or an AI voice agent: which one do you need?

A key-press menu is predictable and cheap to maintain. A voice agent can handle open questions, but it needs careful testing and a human fallback. For a first phone menu, a plain key-press menu is the safer start. Our guide to AI in the call centre covers what AI does well today and how to adopt it carefully.

A checklist before you switch the menu on

• Each key leads to a queue with at least one agent who is signed in during opening hours.
• The greeting names every key, and the keys match the settings.
• You have chosen where callers go if they press nothing.
• You called the number from an outside phone and pressed every key.
• Someone owns the menu and reviews it once a quarter.