Quick answer: A good IVR menu offers a few clear options, puts the most common request first, and gets the caller to a person or an answer quickly. Keep each prompt short, name the option before the key, offer a language choice only if you need one, and always decide what happens when the caller presses nothing. Map the whole call tree on paper before you record a word.
An IVR, or interactive voice response system, answers incoming calls with an automated greeting and a keypad menu. Done well, it sends callers to the right person without anyone picking up the phone. Done badly, it is the reason people shout "agent" at a recording. This guide is about doing it well. If you are mainly after outbound calling, our guide to bulk voice call service in India is the better starting point.
IVR and outbound voice calls are different tools
An outbound campaign calls many people with one message and, at most, one keypad question. We cover that in our guide to press-1 voice campaigns. An IVR works the other way round: people call you, and the menu decides where they go. The skills overlap, but the design problem is different, because an IVR caller chose to call and wants something specific.
Start from why people call
Before you draw a menu, list the real reasons people phone your business, in order of how often they happen. Ask the people who answer the phone today. The top few reasons become your menu options. Rare reasons can wait for a person to handle them.
For a clinic, that list might be booking, report collection, and billing. For a school, admissions, fees and transport. These are only examples; use your own call history.
Menu design rules that hold up
Keep the number of options small
Three to five options on one level is a common working rule. A caller cannot hold nine choices in mind while listening. If you need more, split them across a second level instead of reading them all at once.
Say what the option is, then the key
"For admissions, press 1." The caller hears the topic, decides if it is theirs, and then learns the key. The reverse order makes people replay the menu.
Put the commonest request first
Most callers will press the first option that fits. Order by frequency, not by how your organisation chart looks.
Offer a language choice only if you need one
If your callers speak more than one language, a first prompt such as "for Hindi, press 1, for English, press 2" is useful. If almost all callers speak one language, skip it and save them a step.
Give a way out
Let callers reach a person, or repeat the menu, without having to guess a key. Decide ahead of time what the key for a person is and use the same one at every level.
Plan for silence and wrong keys
Some callers press nothing, and some press a key you did not offer. Choose what happens in each case: repeat the menu once, then route to a person or to voicemail. A menu that loops forever is the worst outcome.
A sample call tree
This is an invented example for a small clinic. Adapt it to your own business.
- Greeting: "Welcome to Sunrise Dental Clinic."
- Press 1: Book or change an appointment, which goes to the front desk.
- Press 2: Reports and billing, which goes to the accounts desk.
- Press 3: Clinic address and timings, which plays a recorded message.
- Press 0: Speak to someone.
- No key pressed: Repeat once, then route to the front desk.
- Outside office hours: Play the timings and take a missed-call callback request.
Routing and office hours
An IVR is also a routing tool. Calls can go to different team members' phones depending on the option chosen, and a different path can apply outside office hours. Think about this at the design stage, because it affects what you record. A menu that says "our team is available" at midnight loses trust.
Test the menu on real callers
- Call it yourself and write down every point where you hesitated.
- Ask someone who has never used it to complete a task without help.
- Play the audio over a phone, not on good speakers.
- Listen to a sample of recorded calls after launch and look for callers who press 0 immediately. That is a sign the menu is not working.
The same listening discipline applies to the recordings themselves, which our guide to writing a bulk voice call script covers.
Where the Nexcomm service fits
Nexcomm's cloud IVR service gives a business a virtual number, either a 10-digit mobile number or a toll-free 1800 number. You design the call tree, add team members' numbers so calls route to the right person, set office-hours routing, and review call recordings and logs from a dashboard. Multi-level menus are supported, and calls can be passed to a CRM through webhooks.
Frequently asked questions
How many options should an IVR menu have?
Three to five on a level is a common working rule. More than that and callers lose track. Use a second level for the rest.
Should the menu be in more than one language?
Only if your callers need it. A language choice as the first step is useful for mixed audiences and a wasted step for single-language ones.
What is the difference between an IVR and a bulk voice call?
An IVR handles calls that people make to you. A bulk voice call is an automated outbound call that you make to many people. Both can use keypad input.
Do I need special hardware?
A cloud IVR runs on the provider's servers, so you do not need exchange hardware or on-site wiring.
How do I know whether the menu is working?
Look at the call reports for drop-offs and for callers who press 0 straight away. Our guide to voice call reports and metrics explains what to read in them.
Sources checked
- Nexcomm's IVR Solutions service page, for virtual numbers, multi-level menus, office-hours routing, recordings and CRM webhooks (checked 2 November 2026).
- The three-to-five option figure is a common working rule, not a standard or a published benchmark. The call tree is an invented example.
More in Voice and IVR guides.
Written by Rohit Jadhav. Last reviewed 2 November 2026.
