Product May 06, 2026

What is an IVR menu and how It helps your business

“Press 1 to book a service, press 2 to speak with a manager” — you’ve probably heard something like this at least once when calling a company. That’s a voice menu.
IVR (Interactive Voice Response) is essentially an interactive automated answering system. It helps companies handle incoming call volumes more efficiently, and helps customers get answers faster.
In this article, we’ll look at how IVR works, why businesses use it, how to set up your own IVR, and which type of interactive menu is best for your needs.

Types of IVR menus and how it can be useful

Most often, IVR clarifies why a person is calling and routes the call to the right department or specialist.

What you can do with IVR

  • Route calls by branch, department, employee, or request type;
  • Stay reachable outside business hours and on holidays: answer questions and collect callback requests;
  • Serve customers without an operator: answer FAQs, provide order status, share address and contact details;
  • Send customer data to your CRM: details, call recording, opt-in/opt-out, etc.;
  • Use CRM data during the call: customer name, order number, status, and more;
  • Collect feedback — NPS and customer reviews.

IVR types

An IVR can be:

  • Single-level
    A short menu with just a few options. After the greeting, the system reads the menu options, the caller selects one, and the IVR performs an action — for example, transfers the call to a manager or provides an answer.
Example of a single-level IVR dialogue

Customer: calls

IVR: IVR: “Hello! You’ve reached ‘Starlight’. To place an order — press 1. For delivery questions — press 2. To speak to an operator — press 3.”

Customer: presses 2

IVR: “Connecting you to the delivery department. Please stay on the line.”

(If everyone is busy)

IVR: “All specialists are currently busy; your call is in the queue. To request a callback — press 1. To continue holding — press 2.”

Customer: presses 1

IVR: “Please say your phone number after the beep.”

Customer: says their number

IVR: “Thank you! We’ll call you back shortly. Have a great day!”

  • Multi-level IVR 
    A menu with branching. After the greeting, the system reads the menu options, the caller chooses one, and then the IVR presents another set of choices. This type of menu can have multiple levels.
Example of a multi-level IVR dialogue

Customer: calls the company

IVR: “Hello! You’ve reached ‘Starlight’. To place an order — press 1. For delivery questions — press 2. To speak to an operator — press 3.”

Customer: presses 2

IVR (level 2): “To check delivery status — press 1. To change or cancel an order — press 2. If the product didn’t fit — press 3. To return to the main menu — press 9.”

Customer: presses 1

IVR (level 3): “Please enter your order number.”

Customer: enters 58321

IVR: “Thank you! Your order has been handed over to the delivery service. Estimated delivery date: tomorrow, from 12:00 to 18:00. To receive a tracking link via SMS — press 1. To connect with a delivery specialist — press 2.”

Customer: hangs up

How to set up an IVR scenario

  1. In the “Inbound Calls” campaign settings, find the “IVR Settings” section and choose the “With reaction” option.
  2. Check the “Recognize words” box if you want the system to respond to spoken words as well. By default, the IVR recognizes only keypad digit presses.
  3. Now set up the first level of the scenario.

    Add a ready-made audio prompt from the platform for a standard scenario — click “Choose prompt”:

    Or create your own prompt from scratch:

    Choose how many times the system will repeat the audio prompt until the caller makes a selection, and set the pause between repeats.
  4. If your scenario expects a caller response, configure how the IVR reacts to caller actions:

Select which digits and words the IVR should react to. Then choose the action and add the IVR’s response if needed.

The platform provides 10 reaction options:

  • Record response — log the caller’s action and end the call;
  • Forward to a phone number — forward the call to a specified number. You can set a different forwarding number for each caller;
  • Forward to SIP — forward to SIP telephony. You can set a separate SIP line per caller;
  • Send SMS to the customer — you can set an individual SMS text per caller. You must mention in the audio prompt that the caller’s action will trigger an SMS;
  • Send SMS to the account owner — send an SMS with the caller’s number to a specified owner number, with a specified text;
  • Repeat the prompt on key press;
  • Add to stop list — calls won’t be made to numbers on this list (common stop list for all campaigns);
  • Webhook — notify third-party apps about events that happened;
  • Go to Level # — jump to a specific IVR level (only available if there is more than one level);
  • Send email — send an email to the specified address with call information (number, date added and processed, pressed key, call recording, etc.). You can set individual text, email, and subject for each phone number.
  1. If needed, add the next menu levels.
  2. Add call forwarding after the audio prompt ends where required — for example, if you have a “Speak to a manager” option.

    At this point, the core setup is complete and you can launch the campaign. You can also configure the campaign in more detail: maximum call duration, days of the week, and so on.

Common mistakes when setting up IVR

  • Too many options
    To prevent callers from getting confused or forgetting what they just heard, it’s best to keep it to no more than 5 options per menu level;
     
  • Long greetings and long messages
    Callers are calling to solve a problem — long introductions and company stories can be annoying. Try to keep a single IVR line within 10–15 seconds;
     
  • Unclear how to reach an operator
    Even if you think you’ve covered everything, the caller may have a question you didn’t anticipate. Always provide a way to speak to a person;
     
  • Not testing the scenario before launch
    Before launching, make a test call to ensure everything works correctly: prompts are linked to the right reactions, all caller response cases are covered, etc;
     
  • Forgetting after-hours logic
    If your scenario includes an option to reach a manager, but the business is closed on weekends, record a separate weekend prompt;
     
  • Changing contacts but forgetting to update the audio prompt
    If your services, pricing, or contact details change, update the IVR the same day so callers always get accurate information.

How to make your IVR audio better

For an IVR to work well, the scenario should be logical, brief, and friendly.
A few tips that will make it more convenient for callers:

  1. Start from the caller’s goals
    People usually call to buy, return a product, or get an answer. So write menu options from the caller’s perspective — not “Sales department,” but “Pricing / terms / talk to a manager.”
  1. Account for mistakes and silence
    What if the caller presses the wrong key or says nothing? A good IVR will offer to go back to the previous level or calmly repeat the message.
  1. Write the way you speak
    Read your script out loud. If it sounds heavy or awkward, rewrite it. Keep it short and simple: instead of “To be connected to the sales department…” say “To place an order, press 1.”

What benefits IVR brings to a business

Depending on how you configure your IVR menu, it can solve different business tasks:

  • Save employees’ time
    If customers often call with the same questions, record an FAQ. Then managers spend time only on requests that truly require their involvement.
     
  • Stay reachable
    Sometimes customers call on weekends, holidays, or after closing. With IVR, you can answer at any time or let the caller know you received the call and will call back during business hours.
     
  • Improve service quality
    When all operators are busy, some customers can get an answer without a human, while others will know how much longer they need to wait in the queue — and feel less frustration.

How IVR is used in different industries

  • Retail and e-commerce
    IVR quickly routes callers based on their purpose: purchase, order status, returns — reducing transfers and missed calls. Common questions (address, hours, delivery status) can be handled without an operator.
     
  • Banks and financial organizations
    IVR separates customers by product (cards, loans, accounts), call purpose (apply, resolve an issue), and branch, helping speed up service — especially at peak times. Dedicated flows for urgent cases (for example, card blocking) reduce pressure on the line and build trust.
     
  • Medical organizations
    IVR simplifies booking and routes inquiries (appointments, test results, certificates, doctor home visits) so reception staff don’t drown in calls. Outside business hours, you can collect requests and offer callbacks.
     
  • Delivery and logistics
    IVR handles the flood of “Where is my order?” calls, routes customers to the right flow by shipment/order number, or sends an SMS with a link. This frees operators and speeds up handling of other requests.
     
  • Hotels and tourism
    IVR clarifies the reason for calling — booking, changes, transfers, or stay-related questions — and routes the call to the right manager immediately. You can also set language selection and handle calls outside reception hours.
     
  • Technical support
    IVR sorts requests by issue type and product, reducing the load on operators while customers reach the right specialist faster.
     
  • Education
    IVR helps the administration during admission season, routes callers between departments, “catches” calls when no one is available, and answers common questions.

If you don’t have IVR yet — connect it now

With a well-designed scenario, an IVR menu removes routine tasks from your team, reduces customer wait time, and makes service predictable and convenient.
To automate inbound call handling, list a few of the most common reasons people call you and build the first IVR level around them.

 If you have any questions, contact support — we’ll help at any step of the setup!

Read next

[ Case Studies ]

 ]

How spotting shifting customer sentiment helped

Apex bank, a mid-sized regional bank, had solid client retention. But leadership felt uneasy. Competitors were rolling out flashy mobile features, and rumors suggested younger clients were considering switching. The bank’s standard quarterly surveys didn’t reveal much — customers mostly ticked “satisfied” and left no comments.

How spotting shifting customer sentiment helped

[ Case Studies ]

 ]

When five stars aren’t enough

A hotel chain was getting plenty of star ratings, but no real explanation. Email surveys returned low reply rates and online reviews only showed extremes. The team needed detailed, on-the-record insights across locations — the kind of feedback you can act on — but traditional surveys weren’t cutting it.

When five stars aren’t enough

[ Case Studies ]

 ]

Keep loosing members? Just ask why

FitZone Gym noticed a worrying trend: more and more members were canceling their subscriptions after just a few months. Exit surveys sent by email went mostly unanswered, and front desk staff rarely asked people leaving for their real reasons. The management team was left guessing — was it pricing, equipment, or maybe poor class scheduling? Without clear answers, they couldn’t stop the churn.

Keep loosing members? Just ask why

[ Case Studies ]

 ]

A clinic wanted honest feedback & stopped handing out paper forms

For years, BrightSmile Dental relied on paper surveys left at the reception desk. Most patients were in a hurry to leave, and only a handful bothered to fill them out. Even those who did were often polite rather than honest. The clinic had no real way to know what patients truly thought — or why some never booked a follow-up

A clinic wanted honest feedback & stopped handing out paper forms

[ Case Studies ]

 ]

How SproutBox validates new ideas in a day

When you sell meal kits, trends move fast. SproutBox’s marketing team had plenty of ideas—new recipes, bundle offers, a “family night” plan—but email polls took weeks and social votes were noisy. By the time answers arrived, the moment (and the budget) had moved on.

How SproutBox validates new ideas in a day

[ Case Studies ]

 ]

A robot that never says “I don’t know”

TechHouse is a consumer electronics retailer that prides itself on fast service and expert advice. With dozens of daily inquiries — from “Is this model in stock?” to “Can I return a purchase?” — the phone was their main sales and support channel.

A robot that never says “I don’t know”

[ Case Studies ]

 ]

Fixit Garage never missed a call again

Fixit Garage was busy all day — repairing cars, handling paperwork, juggling customer questions. But the real problem started after 6 PM, when the phones went silent in the shop — but not for customers. Drivers stuck on the roadside or clients trying to book a morning appointment were left with voicemail. By the time staff called back the next day, many had already gone to a competitor.

Fixit Garage never missed a call again

[ Case Studies ]

 ]

NetLink kept customers calm during a sudden outage

NetLink, a regional internet provider, had built a loyal subscriber base — until unexpected outages started to cause trouble. Every time a server crashed, hundreds of clients picked up the phone at once. Lines were jammed, support agents scrambled, and the same “What’s going on?” question was answered again and again.

NetLink kept customers calm during a sudden outage

[ Case Studies ]

 ]

How a small bistro stopped missing orders — and started growing

Most callers wanted the same things — today’s menu, delivery time, and “extra sauce, please” — but with just two operators on duty, calls piled up fast. By the time someone picked up, some customers had already moved to competitors with faster response times.

How a small bistro stopped missing orders — and started growing

[ Case Studies ]

 ]

TechNova keeps IT teams alert & systems running

TechNova, a fast-growing SaaS company, relied on Slack and email notifications from monitoring tools to inform engineers about outages. But with inboxes overflowing and phones on silent, urgent messages were often missed. Engineers found out about downtime too late — sometimes from angry customers.

TechNova keeps IT teams alert & systems running