Macha
CX & Support Metrics

Average Resolution Time

Definition

Average Resolution Time is the average length of time it takes to fully resolve a support ticket, measured from when it's created to when it's marked solved.

Also known as: ARTtime to resolutionmean time to resolutionMTTR

How to calculate it

Average Resolution Time = sum of (resolution time − creation time) across resolved tickets ÷ number of resolved tickets. Many teams measure it against business hours and may exclude time spent "pending" on the customer so the metric reflects agent-controllable time.

Example: four tickets resolve in 2, 4, 6, and 8 hours. Average Resolution Time = (2 + 4 + 6 + 8) ÷ 4 = 5 hours. Because outliers skew the mean, some teams also track the median resolution time.

Why it matters

Resolution time captures the full customer wait, end to end — not just the first reply. It's a headline indicator of support throughput and directly shapes satisfaction. AI agents shorten it most on repetitive requests they can resolve instantly, leaving humans the complex tickets where longer times are expected.

Frequently asked

What is the difference between resolution time and handle time?

Resolution time is the whole calendar (or business-hours) span until a ticket is solved, including waiting and back-and-forth. Handle time is only the active time an agent spends working the interaction.

Should I use the average or the median resolution time?

The average is intuitive but sensitive to a few very slow tickets. The median is a more robust view of the typical customer experience, so many teams report both.

Put these ideas to work

Macha is an AI agent layer that sits on top of the help desk you already run — Zendesk, Freshdesk, Front, Intercom, or Gorgias.

Start Trial