Contact Center Software

IVR Explained: What It Is and How It Works for Businesses

IVR is the automated phone menu that answers calls and sends each caller to the right place. Learn how IVR works, which type your business needs and how to set up a menu callers can use.

ByFaisal Saeed

PublishNovember 13, 2026

UpdatedNovember 13, 2026

Get a quick summary from

ChatGPT Claude Gemini Perplexity

IVR (interactive voice response) is the automated menu that answers a business call, asks the caller to press a key or say what they need, and then connects them to the right person or gives them the answer. For a business, it sorts every call before anyone on the team picks up.

How well it works comes down to the menu you build: which options it offers, where each one goes, and what happens when a caller does nothing or presses the wrong key.

Key takeaways

IVR answers and routes calls, and some versions also answer simple questions without a person.
Keypad menus handle routing, while speech and AI menus need more setup and access to your other systems.
Every option needs a destination and a fallback for when nobody answers.
Plan for callers who press nothing or the wrong key.
Test every path before launch and again after any change.

What is IVR?

IVR is the automated system behind "press 1 for sales." It answers incoming calls, plays a set of choices and acts on the caller's answer.

You'll also see it called a phone tree, phone menu, auto attendant or virtual receptionist. Each of these names describes a recorded menu that sits between the caller and your team.

An IVR does two jobs. It routes callers to the right person or team, and in more advanced setups it handles self-service, such as reading out opening hours, an order status or an account balance with nobody on the line.

Phone systems call the routing-only version an auto attendant, while "IVR" also covers menus that look up information for the caller. Providers use the two terms loosely, so check which one a plan includes before you compare prices.

How IVR works

Every IVR call moves through the same five steps, whichever system runs it. The settings at each step decide whether the caller reaches someone or hangs up.

Greeting: the IVR answers and plays a short welcome with the business name.
Menu: it lists the options, such as sales, support and billing.
Input: the caller presses a key or, on speech-enabled systems, says what they want.
Action: the IVR connects the call to a team or person, plays information, or opens a submenu.
Fallback: if nobody answers, the caller does nothing, or the business is closed, the call goes to voicemail, another team, an external number or a closing message.

Each key press sends a tone, called DTMF, that the system reads as a number. On a cloud phone system, the menu runs online alongside your numbers and business hours, so there's no hardware to install and you change it from a web dashboard.

All of the steps a successful and efficient IVR Call goes through

Types of IVR and which one you need

IVR systems differ in how callers answer and how much the system can do without a person. Each step up adds setup work and needs more of your other systems connected.

A guide on types of IVR, which one you might need and how you can make a choice

Speech recognition can struggle with background noise and strong accents, so a speech menu needs a keypad option as a backup. Self-service also depends on access to the system that holds the answer; an IVR can't read out an order status unless it's connected to your order records.

If your goal is getting callers to the right team, a keypad menu does the job. Move up only when your call history shows callers asking the same lookup questions day after day.

Does your business need an IVR?

An IVR earns its place when callers want different things from different people. If one team takes every call, a menu only adds a step before the caller reaches them.

These signs say a menu will help:

Calls split across sales, support, billing or other teams.
Someone at the front desk spends part of the day transferring calls by hand.
Callers keep asking the same simple questions, such as your hours or address.
After-hours callers need a message, a voicemail or an on-call number.
Callers need to choose a language before they reach someone.

When you can skip it

A business that gets a few calls a day, all handled by the same people, doesn't need a menu. Ring the team directly and send unanswered calls to a voicemail someone returns the same day.

If calls start to overlap, the fix is a call queue, not a menu. Our guide on how call queues work explains when to add one.

Building the menu takes less time than deciding what goes in it. Work from your call history, not your org chart.

1. List why people call

Pull a few weeks of call history and group the calls by reason. The biggest groups become your menu options, and the small ones can share a "speak to someone" option.

2. Choose the options and their order

Put the most common reason first, so the biggest group of callers hears their option straight away. Two of the guides we read cap menus at two levels, so keep submenus to one layer below the main menu.

3. Give every option a destination

Each option needs somewhere to go: a team, a person, a recorded message or a submenu. Add a "speak to someone" option to every level, so callers who don't fit any choice still reach a person.

4. Write the script

Say the department before the key ("For billing, press 2"), so callers hear what they want before the number. Name teams and roles instead of staff, because a prompt that says "press 3 for Sarah" has to be re-recorded when Sarah leaves.

Here's a daytime menu for a dental clinic:

"Thanks for calling Riverside Dental. To book or change an appointment, press 1. For billing and insurance, press 2.

If you're in pain or have a dental emergency, press 3. To speak to the front desk, press 0."

5. Decide what happens when things go wrong

A menu needs an answer for three problems: a caller who presses nothing, a caller who presses a wrong key, and an option whose team doesn't pick up. Record a short prompt for the first two that repeats the choices, and send unanswered options to voicemail, another team or an external number.

Set a limit on wrong attempts as well. A caller who has pressed the wrong key three times needs a way out, not a fourth loop.

6. Build the after-hours and holiday versions

The after-hours menu keeps the same structure but changes where each option goes. Tell callers your hours, offer voicemail or an on-call number for urgent calls, and set special dates for public holidays.

7. Record and upload the audio

Record every prompt in the same voice, in a quiet room, at a steady pace. Record the no-input, wrong-key and after-hours messages in the same session, so the whole menu sounds like one business.

8. Test every path

Call your own number from an outside phone and press every option during business hours, then again after hours. Try pressing nothing, pressing a wrong key three times and choosing an option whose team won't answer.

Finish by checking that the route to a person works from every level of the menu.

These are the setup choices that leave callers stuck in a phone menu. Each one has a fix you can make in an afternoon.

Learn about common mistakes businesses make with their IVR menus, the impact they have on their business, and how to fix those mistakes

How to tell if your IVR is working

A menu that routes calls well shows it in a few numbers. Check them in the first weeks after launch and after every change to the menu.

Start with calls that end inside the menu without reaching anyone, because those are callers who gave up. Then look at how often callers press nothing or the wrong key, which points to a confusing prompt or a missing option.

Watch transfers after the call is answered. If the person who picks up passes the call on, the menu sent the caller to the wrong place and the option wording needs work.

Repeat calls matter too. A caller who leaves the menu and calls back an hour later wasn't helped, even if the menu kept the first call away from your team.

IVR in ArcSIP

ArcSIP includes a multi-level IVR in its business phone plan, set up as the call flow on any phone number next to its business hours. It's a keypad menu built to get callers to the right team or person.

Menus and submenus: each key rings a team or a user, or opens a submenu.
Fallbacks per option: if the team or agent is unavailable, doesn't answer, or it's after hours, the call goes to voicemail, forwards to a user, team or external number, or ends.
Wrong-input handling: a "no input" message plays when the caller presses nothing, an error message plays after an invalid key, and the call ends after three wrong inputs.
Hours and holidays: business hours, after-hours rules and special dates are set per number.
Audio library: upload prompts once and see which call flows use each file.
Visibility: the live dashboard shows how many calls are in the IVR, and Call Journey shows every step a call took, including fallbacks.

ArcSIP Unlimited costs $29 per user per month with a minimum of three users, and includes the IVR, reusable call flow templates and unlimited call concurrency. You can try it free for seven days without a credit card.

Your first menu doesn't need every option you can think of. It needs the reasons people call, a destination for each one and a fallback for when nobody answers.

Build it from your call history, test every path, and check the numbers after the first few weeks. Review the menu whenever your hours, staff or services change, because a menu that was right in January can send callers to the wrong place by June.

Frequently asked questions

Everything you need to know before getting started with ArcSIP.

Yes, if you give them a way around it. A direct number or an extension lets regular callers, such as key clients or suppliers, reach a person without hearing the menu. On a cloud phone system, that number can have its own call flow that rings one person or team instead of playing the menu. In ArcSIP, each number can ring an agent, ring a team, play an IVR or forward to another number.

It can be, but a payment IVR needs a payment processor that meets PCI DSS, the card industry's security standard. Card details entered on the keypad travel as tones, and the card security code must not be kept in call recordings. Some callers can't tell a genuine phone menu from a scam call, so say in your prompts what you will and won't ask for over the phone. A menu that only routes callers to teams doesn't need to collect personal details at all.

Yes, each number can have its own menu, so a sales line and a support line greet callers differently. The same applies to separate locations or brands that share one phone system. In ArcSIP, each phone number has its own call flow, business hours and special dates. Reusable call flow and business hours templates save you from building the same setup twice.

Either works if the recording is clear and the same voice runs through every prompt. A voice artist costs more up front and gives a polished sound, while recording in-house makes quick changes cheaper. Some systems turn typed text into speech, which suits prompts you update a lot, such as holiday hours. ArcSIP plays audio files you upload to its audio library, so you can replace a prompt without rebuilding the menu around it.

Yes, by putting a language choice at the very start of the call. Each choice opens a submenu recorded in that language, with options that ring staff who speak it. Record each language version on its own rather than translating the prompts word for word, so every menu sounds natural to the people using it. Keep the language choice to one short sentence per language, so callers can pick theirs before the main menu starts.

Outbound IVR places automated calls instead of answering them. It plays a recorded message, such as an appointment reminder or a payment notice, and can let the person press a key to confirm, cancel or reach someone. In the US, prerecorded calls to mobile phones need the recipient's prior consent under the Telephone Consumer Protection Act, and marketing calls need written consent. Check the rules before you send automated calls, because the penalties apply per call.

The price depends on what the IVR does. A keypad menu that routes calls is a phone system feature, so check whether a plan includes it or charges extra; ArcSIP includes multi-level IVR in its $29 per user per month plan. Speech recognition, AI voice agents and self-service lookups cost more, because they need extra software and connections to your other systems. Some vendors sell AI voice agents as a separate product or charge by the minute, so ask for the cost at your call volume.

Yes, because a cloud IVR routes calls to people rather than desk phones. The call rings wherever the person is signed in, at the office or at home. In ArcSIP, staff answer calls in a web browser without installing anything, or in the iOS and Android apps. Each menu option rings the team's members wherever they're signed in.