Composite, drawn from patterns across engagements, not one specific client.
Support ticket volume was climbing for a business I worked with, and the instinct was the obvious one: hire more support staff to keep up. Before signing off on that hire, one question got asked first: what are the tickets actually about.
What looking closer found
Nearly forty percent of tickets, across a six-month window, were some version of the same question: how do I do X. Not bugs, not complaints, confusion about a specific step in the product that a support agent could answer in thirty seconds, every time, the same thirty seconds, over and over.
That's not a support capacity problem. That's a product clarity problem being handled, at great cost, one ticket at a time, by human beings, forever.
Why the obvious fix would have made it worse
Hiring more support staff would have absorbed the volume without touching the cause. The same confusing step would keep generating the same tickets, just with a bigger, more expensive team quietly managing the symptom indefinitely, at a growing cost that scales with the business instead of shrinking.
What actually fixed it
A single onboarding tooltip, placed at the exact step generating the confusion, plus one clarified label on a button that had never been obviously named. Two small product changes. Ticket volume for that category dropped by roughly two-thirds within a month, no new hire required.
The lesson, generalized
Rising support volume is often read as a staffing problem by default, since "we're understaffed" is the intuitive read of "we can't keep up." Sometimes that's true. Often the real story is a small number of product friction points generating a disproportionate share of the noise, and staffing up just makes the underlying problem more costly and still hidden, not solved.