Every support team I’ve worked with tracks the same number: ticket volume, down and to the right. A quieter quarter reads as a win.
It isn’t always one, and the chart alone can’t tell you which.
For years, that number meant roughly one thing: fewer problems, or better self-service. A human who couldn’t solve something alone had exactly one move left — open a ticket. That complaint was the only real signal the business had that something didn’t work, the moment it didn’t work.
An agent doesn’t have that move, and it was never going to develop one. When it hits a wall, it doesn’t call support. It tries another path, another source, another provider entirely, and nobody downstream ever hears about it. There’s no ticket for a door that quietly closed.
So the same metric — tickets down — now has two unrelated causes behind it, pointing in opposite directions. One is quality improving: fewer things are breaking. The other is customers leaving without a trace, routed around the failure instead of reporting it. Pull up both months side by side and the two charts are indistinguishable.
Nobody built this metric to be fooled. It was built on a fair assumption: a user who hits a wall tells you about it. That same assumption held for every kind of user the business has ever served, until a new one arrived that doesn’t hold it at all, and nobody updated the metric to notice the difference.
This isn’t a volume problem. Most agentic traffic today is search and comparison, not transactions — the urgency here has nothing to do with how many agents are buying. It’s a signal problem: the one number support teams report upward just lost the ability to tell these two stories apart.
A ticket count going down proves nothing about quality until someone can say who stopped calling, and why.