An IVR (Interactive Voice Response) is the voice menu that answers calls and guides the caller: "Press 1 for sales, 2 for support...". It is the front door of a good service operation.
How an IVR works
When a call comes in, the IVR plays a message and offers options. Based on what the caller presses (or says), the call is routed to the right queue or agent, or resolved on its own (for example, checking a balance). It works together with IP telephony and the contact center.
Benefits
- Filters and routes each call to the right area, reducing transfers.
- Serves 24/7 with information and self-service.
- Cuts wait time and improves the experience.
- Projects professionalism from the first second.
IVR or bot?
A classic IVR uses digit menus. An AI bot goes further: it understands natural language and automates whole tasks. Many systems combine both.
Designing a menu people do not hate
Almost everyone has hated an IVR at some point, and almost always for the same reasons. The practical rules that avoid it:
- Five options maximum per menu. Nobody remembers six.
- Say the reason first, the digit second: "For technical support, press 2", not "Press 2 for technical support". The caller hears what they care about and already knows what to do.
- Put the most-used option first. If 60 % call for support, support is option 1.
- Avoid more than two levels. One submenu is fine; three levels is a maze.
- Always leave a way to a human and say so out loud. An IVR with no escape hatch causes more anger than any hold time.
- Do not read a welcome paragraph. The caller wants to solve something, not hear your mission statement.
When the IVR can resolve the call on its own
A menu that only distributes calls saves very little. The real jump happens when the IVR looks up data and answers without an agent: order status, balance, appointment date, branch hours.
For that, the IVR connects to your system (via API or database), identifies the caller by number or by something they key in, and answers. Calls resolved there never enter the queue, and those are the ones that actually bring everyone else's wait time down.
Metrics that tell you whether your IVR works
- Abandon rate inside the menu: if many people hang up before choosing, the menu is long or confusing.
- Wrong selections: calls that land in one team and get transferred to another. Your labels are not understood.
- Use of the "operator" option: if almost everyone presses zero immediately, the menu is adding nothing.
- Self-service resolution: share of calls that end in the IVR without an agent. This is the metric that justifies the investment.
Common mistakes
- Recordings with different voices and audio quality between options, which sound improvised.
- Menus that never change, even though the business did.
- Ignoring schedules: offering "talk to sales" at 11 p.m. on a Sunday.
- Not announcing estimated wait time when the queue is long.
At TelHarbor the menu is built visually and connects to queues, schedules, the bot and data lookups. See IP telephony and contact center.
Frequently asked questions
Can I change the menus myself?
Yes. IVR flows are configured and edited from the platform, no coding.
Does it work in several languages?
Yes, you can offer options in Spanish and English.
How many options should my menu have?
Five at most per level, and preferably two levels in total. Beyond that people start hanging up or pressing zero.
Can the menu change by time of day?
Yes. You define one flow for business hours and another for after hours and holidays, with nothing to touch on the day itself.
Can I use a human voice instead of synthesised?
Yes. You can upload your own recordings per prompt, or use synthesised voice for the wording that changes often.
Can the IVR identify the caller?
Yes, by calling number or by asking them to key something in. With that it can greet by name, route differently or read back account information.