For years, Omaha Steaks believed 70% of its inbound calls were sales calls. The evidence looked solid: the IVR said "press one for sales, press two for support," and 70% of callers pressed one.

Then an AI agent replaced the phone tree and started asking callers, in plain language, what they needed. The real mix turned out to be only 45 to 50% sales.

A quarter of the traffic had been misclassified for years. The company had built its entire seasonal training program on that number, so thousands of temporary agents were drilled on selling holiday packages, then spent much of December fielding claims and delivery questions they weren't trained for.

Why key presses lie

Callers don't press buttons carefully. They want a human, and they've learned the fastest route is the first option, or zero, or saying "representative" until something gives. Menu order, wording, and how long the hold message runs all shape the numbers, so what the IVR records is escape behavior.

Every downstream decision inherits that error: staffing models, training curricula, skill-group ratios, and the business case for automation all get built on data that measures which button was easiest to press.

What honest intent data changes

When the routing layer understands what the caller actually said, the numbers underneath it move. Misrouted calls carry a transfer cost and usually a repeat-yourself cost, and Omaha Steaks cut both by letting the agent classify intent from the caller's own words. Knowing the real sales-to-service split also lets you train and schedule against it, which matters most in peak season, when every misallocated trainee is money spent on the wrong skill.

Intent captured at conversational resolution shows you what a phone tree can't: which products drive calls, which policies confuse people.

What else is in there?

If twenty points of your call mix can hide inside your IVR data, what else is hiding there? Most contact centers can't say, because the phone tree is the only intent instrument they have.

Fixing it doesn't require automating a single conversation. Replacing menu buttons with an agent that asks "how can I help?" and routes on the answer is the smallest AI deployment available, and it pays for itself in data quality. Omaha Steaks found a 20-point gap in week one. Yours will be a different number in a different place, and you won't know which until you measure it.