Jan 1, 2026

·

6 min read

Do customers think in menus, or in sentences?

James Bolger

Do customers think in menus, or in sentences?

How Voice AI is changing the role of IVR in customer service

Interactive Voice Response systems have been a core part of customer service operations for decades. They were introduced to solve a practical problem: how to handle growing inbound call volumes in a predictable and cost-effective way.

“Press 1 for sales.
Press 2 for support.
Press 3 to hear these options again.”

For large organisations in particular, IVR has delivered reliability, control, and scale. Many high-volume, mission-critical businesses still rely on it today, and for good reason. It is resilient, easy to govern, and well understood.

What has changed is not the need to manage calls efficiently, but how customers expect to communicate when they reach out.

Customers communicate in intent, not menu structures

When customers contact a business, they are trying to achieve a specific outcome. They are not thinking about call trees or routing logic.

Typical reasons for calling include:

  • Checking an order or delivery status

  • Changing or cancelling a booking

  • Querying a bill or unexpected charge

  • Reporting a fault or service issue

IVR requires customers to translate these intentions into predefined options. When the structure does not match the customer’s mental model, calls are misrouted, transferred unnecessarily, or abandoned altogether.

Voice AI removes this translation step. Customers explain what they need in natural language, and the system identifies intent directly from their speech. This changes how the interaction begins and reduces friction immediately.

Routing versus resolution

Traditional IVR is designed to route calls. Its primary purpose is to decide where the interaction should go next. Voice AI is designed to handle the interaction itself.

A modern Voice AI agent can:

  • Interpret spoken intent

  • Ask clarifying questions when information is incomplete

  • Authenticate callers

  • Retrieve live data from CRMs, order systems, and knowledge bases

  • Complete common service tasks end to end

Instead of passing a customer to an agent to check an order status, Voice AI can retrieve the information and deal with follow-up questions in the same conversation. Escalation happens only when judgement, discretion, or empathy is required.

Headcount is the symptom, not the root cause

In most service teams, headcount feels like the bottleneck. Queues build, agents are stretched, and the instinctive response is to hire more people.

That reaction is understandable, but it often treats the symptom rather than the cause.

In many organisations, agents spend a significant amount of time on work that does not require human judgement. Authentication, basic lookups, simple changes, and repeat questions reach agents because the interface in front of them fails to resolve or prepare the interaction.

Menu-driven IVR contributes to this by pushing volume through rather than dealing with it. Skilled staff end up absorbing avoidable work.

Voice AI changes where effort is applied. Routine requests are handled earlier, context is collected before escalation, and agents spend more time on cases that genuinely need people.

For small teams, this reduces pressure to hire. At enterprise scale, it lowers handling time and repeat contact without removing control.

IVR still matters, but its role is changing

IVR is not disappearing, particularly in large organisations. It continues to play an important role as:

  • A resilience layer

  • A compliance and governance mechanism

  • A predictable fallback when automation confidence is low

What is changing is where IVR sits in the customer journey.

Increasingly, Voice AI is placed in front of or alongside IVR to capture intent, resolve straightforward requests, and prepare interactions before they reach agents or legacy systems. IVR becomes a safety layer rather than the primary interface.

This reflects operational reality rather than ideology.

Why the economics are different for SMEs

SMEs face a different set of constraints.

They typically:

  • Handle lower call volumes

  • Have limited resources to design and maintain call trees

  • Rely on small teams to manage customer enquiries

  • Prioritise speed of deployment and cost efficiency

For many SMEs, Voice AI is simpler to deploy and maintain than IVR. It reduces manual call handling, avoids complex menu design, and delivers acceptable resolution without enterprise-scale infrastructure.

In these environments, Voice AI often replaces IVR entirely rather than supplementing it.

Voice AI and human agents work better together

Voice AI performs best when handling predictable, high-volume interactions such as:

  • Order and account enquiries

  • Simple service changes

  • Appointment scheduling

  • Out-of-hours support

  • Initial triage

This allows human agents to focus on complex cases, sensitive conversations, and situations that require judgement. The result is not fewer people doing more work, but people spending their time on the work that actually benefits from human involvement.

Organisations that deploy Voice AI in this way often see more consistent service quality and better agent retention.

Designing voice journeys around reality

Where traditional IVR asks customers to adapt to systems, Voice AI allows systems to adapt to customers.

For enterprises, this often means reshaping the front of the call journey while keeping proven infrastructure in place. For SMEs, it often means skipping menu-driven call handling altogether. 

The real decision is not whether IVR still works. It is whether it should remain the primary way customers are expected to explain what they need.

Because customers do not think in menus. They think in sentences.