Closing Tickets Properly

The ticket history ends with one word: "Fixed." Eight months later the same printer does the same thing to a different user. A different technician searches for it, finds the old ticket, and learns that it was, at some point, fixed. By whom and how are not recorded. The user of the original ticket was never told either. The status changed, no reply went out, and she found out it was closed when she tried to reply to it. Closing is the least glamorous part of a ticket's life and the only part the future reads.

This series is about the two minutes that make a close worth having. It covers what a proper close looks like, in four parts. It covers resolution notes worth reading later, structured so the stranger who finds them next year can use them. It covers getting the user's confirmation without chasing forever, and avoiding the silent close, which tells the user nothing and asks for no rating. It covers closing the ticket you cannot fix, with honest wording for each case. And it covers the monthly close review that keeps the standard up without turning into an audit. A ticket closed well is a small piece of documentation. A ticket closed badly is a future ticket.

Articles in This Series

• What a Proper Close Looks Like
  The four parts: fix confirmed, note written, user told, category right. Covers the ten-second close versus the two-minute close and what the difference costs, and a close checklist.
• Resolution Notes Worth Reading Later
  Symptom, cause, fix, verification; writing for the stranger who finds this ticket next year; good and bad notes side by side; and a resolution note skeleton.
• User Confirmation Without Chasing Forever
  The confirmation reply, the two-nudge rule, auto-close with notice, when to close without confirmation and how to say so, and the confirmation request to copy.
• Avoiding the Silent Close
  What a status-only close costs: the user who finds out by accident, the rating never asked for, the reopen that is really a complaint. Also covers closing with a reply every time, and the closing reply.
• Closing the Ticket You Cannot Fix
  Will not fix, cannot reproduce, workaround accepted, out of scope, duplicate, requester gone; saying each honestly instead of hiding behind the status; and five closing phrasings.
• The Monthly Close Review
  Sampling closed tickets, what to look for, feedback without blame, and the close review sheet.

Explore More Topics

This series is part of the QuerySolv helpdesk topic library. It covers the foundations, processes, communication, knowledge, tooling, metrics, classic ticket domains, people and strategy behind a support desk that works. The library pairs well with the software we build: QuerySolv. It is a self-hosted help desk that runs as one Windows service on your own network. It is licensed once per installation, not per agent per month.