The repeat-issue review
A client's printer drops off the network again. The engineer restarts the spooler, the user prints, the ticket closes inside the SLA and every dashboard looks great. It's the third ticket for the same fault this month, logged by three users and closed by three engineers, none of whom saw the other two.
Repeat tickets cost margin and goodwill at the same time. Each is quick, so nobody flags it, but the client sees a problem that never goes away and starts wondering what they pay for. One root cause is quietly eating hours every month.
Gather first: last month's closed tickets with resolution notes.
The prompt:
Find the issues that keep coming back across our clients' tickets, and help me fix the root causes instead of closing the same ticket every month.
What experienced service desk managers know:
Repeat tickets close inside SLA, so every dashboard looks fine while one root cause eats hours every month.
The client sees a problem that never goes away and starts wondering what they pay for.
The pattern hides because each ticket is logged by a different user and closed by a different engineer.
Last month's closed tickets with client, device or user, category and resolution notes: [paste]
Our average cost per engineer hour: [figure]
Do this:
Find every issue that appeared three or more times for the same client, device or user, grouped by likely root cause.
For the top five, suggest a permanent fix, the hours it would save each month and the cost of those hours.
Draft a short note to each affected client explaining what we found and what we are doing about it.
Where the resolution notes are too vague to group a ticket, list it separately instead of guessing the cause.