Ticket Aging & Follow-Up Discipline
Ticket 2207 is ninety-four days old. It has been looked at eleven times, which the history records faithfully, and acted on twice. For the other nine, a technician opened it, read it, and felt the particular weight of a ticket that has no obvious next step. Then they closed the tab. Everyone on the desk knows 2207. Nobody owns it, in the sense that matters. A ticket does not age because it is hard. It ages because the next step is unclear and nobody has written down whose job it is to make it clear.
This series is the ongoing hygiene that keeps a desk from needing the recovery series. It covers what ticket age actually measures, and why last-touched beats created. It covers the weekly stale-ticket sweep and the three questions to ask each stale ticket. It covers follow-up cadences by status and priority, including when to stop. Then come the tickets everyone is avoiding and the pairing fix. It covers follow-up messages that get replies, for users, vendors and managers. And it covers reading an aging report so the shape tells you what to do. Follow-up is not nagging. It is the desk keeping the promise it made when it accepted the ticket.
Articles in This Series
- What Ticket Age Actually Measures
Age since open versus time since last update versus time in the current status; the age bands; why last-touched matters more; and an age definitions card. - The Stale-Ticket Sweep: Three Questions per Ticket
The weekly sweep, the three questions for each stale ticket (still a problem, whose move, what next), the outcomes, and a sweep checklist. - Follow-Up Cadences That Keep Tickets Moving
Cadence by status and priority, the update interval, the nudge sequence for users and vendors, when to stop, and a cadence table. - The Tickets Everyone Is Avoiding
Why tickets get avoided (hard, boring, political, unknown territory), spotting them, the pairing fix, the conversation without blame, and a dreaded-ticket worksheet. - Follow-Up Messages That Get Replies
A specific question, a date, what happens next; the user nudge, the vendor nudge, the manager nudge; and three joke-free messages to copy. - Reading an Aging Report by Its Shape
Backlog by age, the healthy shape and the unhealthy one, the action per band, the manager's weekly glance, and an aging report layout.
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.