IVR and phone menus

IVR Analytics: Metrics to Track and How to Improve Your Menu

Which IVR numbers matter, how to find the point where callers give up, and a simple routine for testing one change at a time and checking that it worked.

Call editorial team · Published · 7 min read

When you design a phone menu, it feels clear. You know what every option means and where it leads. A first-time caller does not. They are listening for a word that matches their problem and guessing at the rest. The gap between those two experiences is invisible from the inside, and it is the reason IVR analytics matters.

A team lead reviewing call statistics on a laptop beside a desk phone
Illustrative image

This guide covers the measures worth tracking, how to find the exact point where callers give up, how to learn from what callers say once they reach a person, and a routine for improving one thing at a time. If you are still choosing how to structure the menu itself, read IVR Menu Design first, or What Is IVR? for the basics.

Why you need data to improve a menu

Callers who get lost rarely complain. They hang up. The people who do give feedback are the ones who struggled through and reached an agent, so you hear from the survivors and never from the people who gave up. Numbers are the only way to hear the silent group.

Call reasons also drift. A new service, a season, a change to your website: each one shifts why people phone. A menu that matched last spring may be sending a third of this month's callers to an option that is no longer the main event. Reviewing data on a schedule catches that drift early.

Finally, data lets you prove that a change helped. Without a before and after, every edit is an opinion.

The measures worth tracking

You do not need every possible metric. Begin with a short list and make sure you count the same way each month.

MeasureWhat it tells youHow to read it
Option selectionHow often each menu choice is pickedA choice nobody picks may be unclear or unnecessary. A choice everyone picks may deserve to move higher in the list.
Drop-off by stepWhere callers hang up inside the menuA spike right after the greeting suggests it is too long. A spike after one option suggests that option leads somewhere unhelpful.
Requests for a personHow many callers press the key for an agentHigh numbers at one point show a menu branch that is missing an option.
Invalid or empty inputWrong keys, silence, speech not understoodRepeated errors mean wording or timing is the problem, not the caller.
Repeat callersSame number calling again soon afterOften a sign the first call did not solve the problem or ended in the wrong place.
Time to reach an agentHow long callers spend in menu and queueLong menus add time before the queue even begins.

Decide how you count before you start

Pick a reporting period, such as weekly or monthly. Decide whether business hours and after-hours calls are reported separately, because after-hours callers hear different messages. Decide how you treat a caller who dials twice in a few minutes. Whatever you choose, write it at the top of your tracking sheet and keep it fixed. If you change the counting rule halfway, a movement in the numbers may only reflect the new rule.

If you only watch three things

The first three numbers to watch

  • Which options are chosenShows whether the menu matches why people call today.
  • Where callers hang upShows which step loses people.
  • How many ask for a personShows what the menu does not cover.

Finding where callers give up

Draw your menu as a simple flow, from greeting to destination, then write the number of callers who reached each step beside it. The shape of the numbers usually points at the problem within a minute.

Reading a menu flow with counts

  1. GreetingCount callers who hang up before any option is read.
  2. First menuCount the callers who press nothing, press a wrong key or ask for a person.
  3. Second levelCompare how many who picked an option go on to a second menu or a queue.
  4. DestinationCheck how many callers hang up while waiting, and how many reach someone.

Separate finished callers from lost callers

Not every hang-up is a failure. A caller who hears your opening hours or a recorded address and hangs up has what they needed. That is a good outcome. A caller who hangs up halfway through the options, or after twenty seconds in a queue, probably did not. If your system records how long a call lasted and where it ended, compare the two groups separately, and do not set a target that treats every early hang-up as a loss.

Look at callers who call again

A caller who rings back within minutes is telling you something. They may have hung up, been transferred to the wrong place, or got an answer that did not solve the problem. Listing the numbers that call more than once in a short window is a quick way to find the branches that produce confusion.

Learning from what callers say

Counts tell you where. Conversations tell you why. Once a caller reaches an agent, the first sentence they say is usually the reason the menu failed them: "I pressed the sales option but I am already a customer."

A routine for improving one thing at a time

It is tempting to rewrite the whole menu after reading the data. Resist that. If you change five things and the numbers move, you cannot tell which change worked, and if they get worse you cannot tell which to undo.

Five steps for each improvement

  1. Write the problem in one sentenceFor example: many callers hang up after the second option.
  2. Guess the causeWording unclear, too many options, a long message, wrong destination.
  3. Change one thingReword one option or shorten one message, nothing else.
  4. Test and record the dateCall the line yourself and write down when the change went live.
  5. Compare after a fixed periodUse the same measure and period as before, then keep or undo the change.

Common symptoms and likely fixes

Likely causeTry first
Many hang up after the greetingGreeting too long, main choices come lateShorten the greeting and put the main choices earlier
One option is rarely chosenWording does not match how callers thinkReword it in the caller's language, or merge it with a neighbour
Many ask for a person at one branchThe branch is missing an optionAdd the missing option, or send that branch to a person directly
Callers press wrong keys oftenOrder or pacing is confusingReorder options, repeat the key after the label, slow the speech
Callers hang up while waitingNo alternative to waitingOffer a callback or voicemail

The last row has its own guide: Using Callbacks and Voicemail in Your IVR.

Pitfalls when reading the numbers

A monthly rhythm

Choose one person to own the review. Once a month, take thirty minutes to look at the same short list of measures, compare them with the previous month, and decide on at most one or two changes. Also review after any event that shifts call reasons, such as a new service, a price page update or a holiday period. Routing Calls by Business Hours, Holidays and Closures is worth rereading before each seasonal change.

Monthly review checklist

  • Option selection counts, split by business hours and after hours
  • Drop-off at each step compared with last month
  • Number of callers who asked for a person, and the topics they raised
  • Repeat callers within a short window
  • Changes made last month and whether they helped
  • The single change for next month, with its start date

Looking at your calls in Call

Call gives you a few places to start. The voice analytics page shows, for a chosen period and phone line, how many calls the AI agent picked up, how many caller turns it answered, and how often callers were put through to a person or left a message. It also counts moments such as callers talking over the agent. Call history lets you open a call, read its summary and transcript, and see the outcome. For queues, the Queues and SLA page shows figures such as the longest wait and abandoned calls, and the callbacks list shows what is waiting. Some measures, such as call length and caller ratings, are not shown on the voice analytics page, so check which numbers each screen offers before you plan your review around them.

For a wider view of measuring a call line, see Call Analytics Dashboard and Call Center KPIs.

Frequently asked questions

What should I look at first in IVR analytics?

Start with which options callers choose, where they hang up and how many ask for a person. Those three show whether the menu fits why people call.

Is a high abandonment rate always bad?

No. A caller who hears your hours or address and hangs up may have what they came for. Separate callers who finished from callers who gave up midway.

Is it worth analysing a small call volume?

Yes, but read the individual calls rather than relying on percentages. A few calls a day still reveal repeated confusion.

What if my system does not report drop-off?

Make your own test calls, ask agents to note the first thing callers say, and review call logs for callers who ring twice in a short time.

Should I change several things at once?

It is better not to. One change at a time lets you see what helped and undo it if it did not.

How long should I wait before judging a change?

Long enough to cover a normal cycle of your business, usually at least a couple of weeks, and compare the same days and hours as before.

Can I delete an option nobody chooses?

Check first. It may be badly worded, or it may serve a rare but important need. Reword or merge before removing.

See how your callers move through your phone lines in Call

In the demo console you can try incoming calls in a simulation.

Related guides