Pull up a chair. You have just joined a support process and someone says, “Go and look at the IVR.” You nod, but what are you supposed to be looking at? Let me explain what an IVR really is, and you will see why people who run contact centres argue about it so much.

IVR stands for Interactive Voice Response. It is the recorded voice that answers before any human does: “For account balance, press 1. For card blocking, press 2.” Newer ones let you speak instead of pressing keys. Underneath, it does three jobs. It collects some information (an account number, a mobile number), it sorts the caller into a queue, and sometimes it finishes the whole task without an agent at all.

Sorting is the main job

Think of a hospital reception. The receptionist does not treat anyone. She sends the person with a fractured wrist to orthopaedics and the person with a fever to general medicine. An IVR is that receptionist. Its first duty is to send the call to the group of agents trained for it. A caller with a loan query who lands with the credit-card team will either be transferred (a cost, and an irritation) or given a wrong answer (a worse cost).

This is why skill-based routing and the IVR are planned together. If you have three queues, a menu with twelve options is pointless. If you have twelve specialist queues, a menu with three options will push the sorting work onto agents.

Self-service: containment

The second job is self-service. Balance enquiry, order status, bill due date, a PIN reset after authentication: if the IVR can complete these, no agent is needed. The share of calls that end inside the IVR is called the containment rate.

Take an illustrative regional electricity-bill helpline in Guwahati. It receives 60,000 calls a month into the IVR, and 15,000 of them finish there, say a caller checks the last payment and hangs up. Containment is 15,000 / 60,000 = 25%, and 45,000 calls go on to agents. Now suppose a redesign lifts containment to 35%. That is 21,000 contained and 39,000 reaching agents, so 6,000 fewer agent calls every month. Multiply by average handle time and you get workload hours saved, and you can feed that to the staffing calculation.

But here is the catch, and it is a big one. A high containment number does not mean customers were helped. A caller who gets lost in the menu, gives up and hangs up is also “contained” in a lazy report. Look at what happens next: did the same number call back within a few hours? Did the call end before the caller reached any real option? Containment without that check flatters bad design.

Menu design: small decisions, large effects

Some practical points that experienced designers tend to agree on, though you will find exceptions:

  • Keep each level short. People hold a handful of spoken options in memory, and by the fifth they have forgotten the first.
  • Put the most frequent reason first. Your call-reason data (disposition codes) tells you what that is; do not guess.
  • Name options in the customer’s words. “Billing and payments” works. “Account servicing” means nothing to a caller.
  • Never trap people. A way to reach an agent should exist, ideally within two levels.
  • Limit the depth. Each extra level costs the caller time, and the drop-off adds up.

Language selection is a particular Indian question. Offering Hindi, English and one or two regional languages at the very start is common, and the order matters: a wrong guess forces the caller to listen through a language they cannot follow before reaching the choice they need. Many teams decide the order from caller data, or detect the language from the registered number’s region and pre-select it.

Authentication inside the IVR

If the IVR asks for a customer ID or a registered mobile number and an OTP, the agent receives a call that is already identified, and can skip the first minute of questions. This saves handle time, and it is also safer, since card numbers can be keyed in by the caller rather than spoken to a person. Whether that is permitted depends on the client’s security rules, so find out before you promise anything.

Where an IVR goes wrong

Speech-recognition menus misunderstand accents, noisy surroundings and code-mixed speech, which is how many Indians actually talk. A caller who says “mera bill” and is told “Sorry, I didn’t get that” three times is furious before the agent says hello, and that anger shows up in CSAT and handle time, not in the IVR report. Always read agent feedback about “customers already upset when they arrive” as a signal about the IVR.

Another failure is stale content. A promotion ends, but the option still plays. A branch closes, but its number is still announced. Someone must own the IVR script and review it on a schedule, with changes tested before going live, because a typo in call flow can send every caller to the wrong queue within minutes.

So when someone says “look at the IVR”, look at four things: how callers are sorted, what it finishes by itself, how many leave before reaching a person, and what mood they carry into the first sentence the agent speaks. The menu is a conversation with the customer, held by a machine on your behalf.

Figures and names in the examples are illustrative.

Leave a Reply

Trending