Average Ticket Age
Definition
Average Ticket Age
Average ticket age is the mean time that tickets in your current open queue have been waiting, counted from the moment each one arrived. It tracks the backlog you still owe right now, not the closed work that has already left your queue.
That distinction does real damage when it gets blurred. Resolution time looks backwards at finished work. Ticket age looks at what is still sitting in front of you, unfinished and getting older by the hour.
A team can post a fast resolution time while a pile of hard cases quietly ages behind the easy ones. Age is the number that catches them.
Key takeaways
- Average ticket age counts the current open queue, never the tickets you already closed.
- One ancient case can drag the mean, so read ageing buckets alongside the average.
- Pausing the clock for waiting on customer time is defensible, but it has to be disclosed.
- Rising age with flat volume points at capacity; rising age with rising volume may be a spike.
How it works
Average ticket age sums the open time of every unresolved ticket, then divides by the number of tickets in the queue. Run it daily, on the same snapshot, so the number moves with real work rather than with reporting habits.
Every support ticket starts its clock at creation and keeps counting until it closes. Nothing about that clock cares how hard the case is, who owns it, or whether anyone has looked at it since Tuesday.
Most help desk support tools do the arithmetic for you. The trap is trusting the single figure it hands back — a mean is one number describing a queue that holds two very different populations of work.
Split the queue into ageing buckets and the shape appears. Buckets tell you whether you carry a thin tail of stubborn cases or a broad slide across the whole backlog. Those two problems need different fixes.
| Ageing bucket | What it usually means | Sensible next move |
|---|---|---|
| 0–1 day | Healthy flow; most work lands and clears fast | Leave it alone |
| 2–7 days | Normal for cases that need a second touch | Watch for repeat contacts |
| 8–30 days | Stalled work, unclear ownership, or missing information | Assign an owner and chase |
| 30 days plus | Forgotten tickets that quietly skew the mean | Resolve or close with a reason |
Buckets also make for an honest conversation with the business. A claim that the average looks fine dies quickly once somebody points at the 30 days plus column and asks who owns the cases sitting in it.
Pause states are the other lever. Most teams stop the age clock while a ticket waits on the customer, and that is fair enough — you cannot fix what nobody will answer questions about.
The rule is disclosure. Say plainly whether your average ticket age runs on raw elapsed time or on paused time. The two numbers are not comparable — and quietly mixing them makes a queue look healthier than it really is.
Age also reacts to first contact resolution. When more cases close on the first touch, fewer of them survive long enough to age at all, so the two measures tend to move in opposite directions.
Reading the trend matters more than reading today’s figure:
- Rising age, flat volume. Capacity is short. Work arrives at the same rate but leaves slower, so the queue deepens without anyone noticing.
- Rising age, rising volume. You may simply be in a spike. Check whether the peak is already fading before you hire against it.
- Flat age, rising volume. The team is absorbing the extra load. Watch quality signals so speed is not being bought with accuracy.
Examples
Average ticket age reads differently by sector, and the useful examples are the ones with public reporting or public cost data sitting behind them. Three settings show how the number gets used in practice, and what it costs when it drifts.
Public service delivery. The US federal customer experience programme runs on published accountability rather than private dashboards.
Executive Order 14058, signed in 2021, set ongoing accountability for federal service delivery through High Impact Service Providers. It also directed 17 agencies to take 36 specific actions on customer experience.
OMB Circular A-11, Part 6, Section 280 carries the annual guidance behind that work. Where a public service reports its backlog, ticket age is the number citizens actually feel — the waiting, not the tidy close time.
Contact centre staffing. The US Bureau of Labor Statistics tracks the labour side of the same queue.
Its handbook puts the median hourly wage for customer service representatives at $20.59 in May 2024, and projects employment to decline 5 percent from 2024 to 2034.
About 341,700 openings a year are still projected on average across that decade, mostly from people leaving the job. So a queue that ages while headcount holds flat is not warning you about a future shortfall — it is reporting one you already have.
The cost of carrying a backlog. The US Bureau of Labor Statistics compensation series prices the hours that an old ticket quietly eats.
Total employer compensation for private industry workers averaged $46.60 per hour worked in March 2026. Wages and salaries made up $32.60 of that, or 69.9 percent, and benefits accounted for $14.01, or 30.1 percent.
Across all civilian workers, total compensation averaged $49.32 per hour worked. Those rates are what an ageing queue is spending while nothing visible happens to the customer.
Old tickets get reread, re-explained and rehandled every time a new agent picks one up. Each of those touches buys the same hour twice, which is why age turns expensive long before anyone complains.
Related terms
Average ticket age sits inside a small family of queue measures, and the differences between them are where most reporting arguments start. These five terms give you the vocabulary to describe queue health precisely instead of loosely.
- Open Ticket: any case still sitting in the queue and still adding to its own age.
- Resolution Time: backward looking measure of how long closed cases took to finish.
- Ticketing System: software that timestamps, routes and stores every case in the queue.
- Escalation: handover of a stuck case to a higher tier, often the point where ageing stops.
- Service Level Agreement (SLA): contracted response and resolution promise that ageing tickets quietly breach.
FAQ
What is a good average ticket age?
There is no universal target, because it depends on what you promised. Compare the number against your own service thresholds and your own trend line rather than an outside benchmark.
Is average ticket age the same as resolution time?
No. Ticket age measures cases that are still open right now, while resolution time measures cases you have already closed. A queue can look fast on one and poor on the other.
Should waiting on customer time count toward ticket age?
Either choice works, as long as you publish which one you use. Pausing the clock is defensible when the customer holds the next action, but the paused number cannot be compared with raw elapsed time.
Why use ageing buckets instead of a single average?
Because one very old ticket can pull the mean up while most of the queue is perfectly healthy. Buckets show the shape of the backlog, so you can tell a thin tail of stubborn cases from a broad slide.
How often should you measure average ticket age?
Take a snapshot daily at the same hour, so the trend reflects real work rather than the timing of your reports.
Explore how outsourcing teams keep support queues moving at scale with Outsource Accelerator.
Independent
