Operations

What are aging tickets (ticket ageing)?

Also known as: ticket age, aged tickets, aging tickets, ageing tickets, ticket aging, aging ticket report

Published September 10, 2026 · Last updated October 8, 2026 · Reviewed by the Fidiora team

Definition

Aging tickets are support tickets that are still unresolved after a set period, and ticket ageing is the practice of tracking how long each open ticket has been waiting. Teams group open tickets into age buckets, such as under a day, one to three days, and over a week, so old work stays visible inside a queue that looks small.

Why it matters

Age is the metric that correlates with customer anger. Nobody churns because a company has four hundred open tickets. They churn because theirs has been open for eleven days with no update. Ageing turns an abstract backlog into a list of specific relationships at risk.

What to know

Report age buckets, not an average age, because the average hides the tail where the damage is.
Separate waiting-on-customer from waiting-on-us. Only the second is your problem to solve.
Old tickets are usually stalled rather than hard, and stalling is nearly always an ownership gap.
An update, even without a resolution, resets the customer perception of neglect. Silence is what hurts.
Set an age threshold that triggers automatic escalation, or old tickets will only be found by complaint.

How to calculate it

Ticket age = current time - time the ticket was opened (excluding time waiting on the customer). Aged ticket share = (open tickets older than your threshold / all open tickets) x 100

An example

Example: a queue of two hundred tickets looks healthy at an average age of one day. The bucket view shows six tickets over three weeks old, all from paying customers, all stalled waiting on an internal answer nobody owns.

Ticket aging buckets and what to do in each

A common way to bucket open tickets by age. Adjust the boundaries to your own response and resolution commitments.
Age bucket	What it usually means	Typical action
0 to 24 hours	Normal working queue	Work in priority order. No special handling needed.
1 to 3 days	Needs a second touch or is waiting on an answer	Check it has an owner and the customer has had an update.
3 to 7 days	At risk. Usually stalled on another team or on missing information	Team lead review. Chase the internal dependency and send a status update.
7 to 14 days	Aged. Customer patience is probably gone	Escalate by rule, name a single owner, and give the customer a date.
14 days and over	Critical. Often forgotten, or blocked with nobody chasing	Daily review by the support manager. Resolve, close with an explanation, or convert to a tracked bug.

Common mistakes

Reporting average age instead of age buckets
Counting time waiting on the customer against your own ageing
Having no automatic trigger for tickets past a threshold
Letting stalled tickets sit without an owner

Where Fidiora fits

Fidiora keeps the routine volume out of the queue entirely, which makes ageing visible rather than buried. Rules can escalate anything past a threshold automatically, so an old ticket surfaces before the customer has to chase it.

See Pricing

FAQ

Questions

What does aging tickets mean?

Aging tickets are support tickets that are still unresolved after a set period, so they are getting older in the queue. Ticket ageing is the practice of tracking that age, usually in buckets such as under a day, one to three days, and over a week, so the oldest work is visible rather than buried under new arrivals.

What is an aged ticket?

An aged ticket is an open ticket that has passed the age your team treats as too old, commonly somewhere between three and seven days for standard priority. The threshold should come from your own SLA or resolution promise rather than a generic number, and crossing it should trigger a named owner and a customer update.

Is it ageing tickets or aging tickets?

Both are correct. Aging is the American spelling and ageing is the British one, and help desk tools use either in their reports. The meaning is identical: tracking how long unresolved tickets have been open, so the oldest ones get attention before the customer has to chase.

How do you reduce aging tickets?

Give every ticket past the threshold a named owner, chase the internal dependency it is usually waiting on, and send the customer an update even without a fix. Then reduce inflow by resolving routine questions automatically, so nothing slips to the back. Our guide to fixing aging tickets includes a weekly review process.

What is a good ticket ageing profile?

One where the oldest bucket is small and shrinking, and where every ticket in it has a named owner and a recent customer update. The exact thresholds depend on your promises, but silence past a week is a problem in almost any business.

Why do tickets get stuck?

Almost always because they depend on something outside support, such as an engineering answer or a finance approval, and nobody owns chasing it. It is an ownership problem far more often than a difficulty problem.

Should time waiting on the customer count toward age?

Track it separately. A ticket waiting three days for a customer reply is not neglected. Blending the two makes your ageing report unusable for finding real problems.

Get Started

See Fidiora resolve a ticket in 60 seconds.

No credit card, no sales call required. Connect your docs and watch it work.

Start Free Book a Demo

No credit card · Live in under an hour · Read the setup guide