Root-cause analysis: fixing the ticket that keeps coming back
Resolving a ticket answers the customer in front of you. Root-cause analysis asks why the ticket exists at all — here is how to run it on recurring support volume and fix causes instead of symptoms.

The reset-password ticket came in for the fourth time that week — same customer type, same confused step, same three-message dance to fix it. Each one got resolved. The rep was polite, the customer left satisfied, the ticket closed green. And next week it came back, because nobody had touched the thing that generated it: a verification email landing in spam and a help article that never mentioned it.
That is the gap between resolving a ticket and fixing a cause. First-contact resolution answers the problem in front of you. Root-cause analysis asks why the problem exists at all — and stops it from being asked again.
Resolution is not prevention
Support teams are optimised to close tickets, and they are good at it. The industry-average first-call resolution rate sat at 69% in 2024.
Read the other side of that number: roughly three in ten contacts still generate a callback. And a surprising share of those repeats aren't the same question asked twice — they are the downstream problem the first fix quietly created.
The pattern goes deeper. When CEB (now Challenger) took apart what actually drives repeat contacts, the stated problem — the thing the customer literally called about — accounted for only about half of them. The rest came from adjacent issues nobody surfaced.
A ticket you resolve five times is a ticket you have never actually fixed.
That is the whole case for root-cause analysis in one line. If half your repeat volume comes from causes the customer never named, no amount of faster resolution will drain it. You have to go upstream.
Start from the cluster, not the ticket
RCA begins where your data already is. Pull the last quarter of tickets, group them by contact reason, and sort by frequency. You will find the familiar shape: a short list of reasons generating most of the volume. Those clusters — not individual tickets — are your units of analysis. A single angry ticket is an anecdote; two hundred tickets tagged "invoice wrong" is a cause with a return address.
Then ask why, repeatedly. The 5 Whys is the oldest tool for this, and it is almost embarrassingly simple.
"Invoice wrong" → why? The proration is off. → Why? The plan-change date is stored in the wrong time zone. → Why? … Five honest questions usually walk you from the symptom the customer felt to the line of code, policy clause, or missing help article that caused it. A fishbone diagram does the same job when a cause has several contributing branches — sort candidates into product, policy, content, process, and tooling, and the empty branches show you where you haven't looked yet.
Fix the cause, then close the loop forward
The output of RCA is not a report. It is an owner and a change: a bug filed, a policy reworded, a help article rewritten, a form field made un-skippable. Route it to the team that owns the cause and track whether the cluster shrinks — the cluster count, not this month's CSAT, is your scoreboard.
While the structural fix ships, buy margin with next-issue avoidance: forewarn the customer about the predictable next problem before they hit it. The economics are lopsided.
Fifteen seconds now against a five-minute angry call later is the best trade in support, and it costs nothing but a sentence.
None of this is exotic. It is the discipline of treating recurring tickets as evidence rather than weather. Point the analysis at the reopen rate and your top contact drivers, run it monthly, and give every confirmed cause a name and a due date. A working structure — problem statement, 5 Whys, categorised causes, owner, verification — fits on a single shared page your whole team can see. The teams that pull ahead aren't the ones who close tickets fastest. They're the ones who make sure the same ticket stops arriving.