Every support queue has two enemies, and they are not the same. The first is the backlog — a raw pile of open tickets you can drain in a focused sprint. The second is quieter and more corrosive: aging. Aging is not about how many tickets are open; it is about how long the ones that are open have been sitting there without anyone doing anything. A queue of 300 tickets that were all touched today is healthy. A queue of 40 tickets where a dozen have not been looked at in eleven days is rotting, even though the number is smaller. Aging is the metric that catches the tickets falling silently through the cracks, and it is the one most teams never look at until a customer escalates a thread nobody has touched in two weeks.

Aging measures neglect, not volume

The reason a raw open-ticket count hides aging is that averages lie by design. A team can post excellent first response times and a healthy median time to resolution while a small tail of tickets quietly ages past a month — because the fast, easy tickets flood the average and drown out the few that are stuck. The customers on those aging tickets are exactly the ones most likely to churn or escalate, because their experience is the opposite of the tidy number on your dashboard. To see them you have to stop looking at the middle of the distribution and start looking at the oldest end of it, which is what an aging report is for.

The aging-bucket report

The core tool is a report that buckets every open ticket by how long it has been since it was last actioned — not since it was created, since it was last genuinely worked. A typical set of buckets:

  • 0–1 days — fresh, nothing to worry about.
  • 2–3 days — normal for anything waiting on a real investigation.
  • 4–7 days — the warning zone. Something here should have moved by now.
  • 8+ days — the danger zone. Any ticket this old needs an owner to explain why, today.

The point is not the exact thresholds — pick ones that fit your SLA policies — but the shape: a queue in good health has almost everything in the first two buckets and a near-empty tail. When the 8+ bucket starts to fill, you have found your neglected tickets before the customer finds you.

The no-ticket-untouched rule

The operational habit that keeps the tail empty is simple to state and hard to keep: no open ticket goes more than N days without a human touching it, where a touch means a real update — a reply, a status change, a note to the customer explaining the delay — not just opening it and closing the tab. Silence is what makes a ticket rot, and a short holding reply ("still working this, here is where we are") resets both the customer's patience and the aging clock. Making this a daily sweep — one person owns walking the oldest bucket each morning — turns aging from a quarterly surprise into a routine that never lets a ticket reach two weeks unseen.

Real staleness vs. legitimately parked

The trap in any aging report is false positives. A ticket in "waiting on customer" for six days is not neglected — the customer has not replied. Counting it as stale punishes your team for someone else's silence, the same distortion that wrecks SLA clocks when they do not pause. So aging has to respect waiting states: a ticket parked on the customer or snoozed to a future date should be measured against its own clock, not flagged as rotting. Get this wrong and agents learn to ignore the aging report because it cries wolf; get it right and every ticket in the danger bucket is a real one.

Making it visible in the tool

Aging only becomes a habit if the report lives where the team already works, not in a spreadsheet someone rebuilds on Fridays. Hitt Hosting Desk surfaces a backlog-aging view that buckets open tickets by time since last action, respects waiting and snoozed states so parked work is not miscounted, and lets you sort straight to the oldest untouched ticket in the queue. Plans start at 7.99 dollars per seat; see pricing for what each tier includes.

The honest test

Your aging is under control when the oldest untouched ticket in your queue is one you could defend out loud — a genuine investigation in progress, not a thread everyone forgot. Open the aging report and look at the 8+ bucket: if you can explain every ticket in it, you are running the queue. If half of them make you wince, aging has been happening the whole time and the raw open-count was hiding it.