The first time I saw a 90 percent first-call resolution rate, I thought it was great. The second time I saw it, I thought it was suspicious. The third time, at a service desk I was running, I confirmed it was a symptom. Same number on the dashboard. Three completely different organizational realities underneath. The lesson took me a few more years to internalize than I would like to admit: a headline operational metric is never an answer. It is a question disguised as one.
This essay is the version of that lesson I wish someone had handed me earlier. It is short on purpose, because the diagnostic is short. The work of acting on the diagnostic is not short. That part is the rest of your career.
The under-escalation trap
The trap is structural. The incentive system most service desks operate inside rewards ticket closure. Closing a ticket on the first call counts as a win. Escalating it counts as a partial loss, both for the analyst who handed it off and for the metric the leadership team watches. Over enough quarters, that incentive selects for analysts who solve symptoms quickly and skip the harder, longer conversation about cause. Tickets get closed. Customers get a workaround. The underlying issue stays in the environment and produces a repeat incident two weeks later, which gets a different ticket number and is closed again.
This is the version of high first-call resolution that looks identical to the healthy version from the dashboard. The dashboard sees a 90 percent close rate. The dashboard does not see the repeat-incident percentage, the problem-record creation rate, or the customer satisfaction score taken thirty days after resolution rather than five minutes after. Those are the three numbers that disambiguate the score on the front page.
Three diagnostic questions
If you want to know which version of 90 percent you have, you only need three answers. First: what is your repeat-incident rate against a six-month window? Healthy organizations sit around four percent. Under-escalating organizations sit closer to twenty. Second: how many problem records does your service desk create per month? Healthy organizations create a steady, non-trivial number, because incidents reveal patterns and patterns get logged. Under-escalating organizations create almost none, because the incentive to investigate has been quietly removed. Third: what is your customer satisfaction score thirty days after resolution? Same-day CSAT will tell you whether the customer felt heard. Thirty-day CSAT will tell you whether the resolution actually held.
A 90 percent first-call resolution rate is a number. Whether it is good news depends entirely on what the other 10 percent looks like.
Why problem management is the real test
The metric that disambiguates a healthy service desk from an under-escalating one is not on most service-desk dashboards at all. It is on the problem management dashboard, which is usually owned by a different team and reported on a different cadence. The two need to be looked at together. A high first-call resolution rate paired with a thriving problem-management function means the team is genuinely empowered and the environment is genuinely improving. A high first-call resolution rate paired with a starved problem-management function means the team is being graded on speed and the environment is silently accumulating debt.
Problem management is the conscience of a service desk. It is the function that tells the leader the truth when the leader has gotten too dependent on the headline number. If you starve it for resources, you have created a structural incentive to under-escalate, and your dashboard will keep looking great until the day a major incident exposes the cause that should have been logged six months ago.
What mature organizations do about the 10 percent
The mature organizational answer to the unresolved ten percent is not to push it to ten percent. It is to look at it. The ten percent that escalates is the most valuable signal on the service desk, because that ten percent contains the patterns the rest of the system will produce in volume next quarter. Mature organizations build a weekly rhythm around reading their escalations. They look at what categories the escalations cluster in. They feed those clusters into problem management. They publish a small number of changes per quarter directly traceable to that practice.
That rhythm is invisible from the dashboard. It is also the difference between a service desk that closes tickets and a service desk that improves an environment. The first kind shows up well in board reports. The second kind shows up well in the next decade of your operating model.
Where the answer actually lives
What is your problem-management maturity? That is the question. Because that is where the answer to the FCR question actually lives. The headline number on your service desk is a confidence trick if you cannot answer the next layer down. Three questions, one report, a quiet rebuild of the incentive system. The dashboard you publish next year will look exactly the same. The organization underneath it will be a different one.