Average Resolution Time: How to Measure It and Bring It Down

J. Parekh··5 min read
Average Resolution Time: How to Measure It and Bring It Down

Customers judge support on two moments: how quickly someone answers, and how quickly the problem goes away. The first is measured by first response time. The second is average resolution time, and it's the one customers actually remember.

This guide explains how to calculate it, the choices that change the number, and seven ways to bring it down without rushing anyone.

What is average resolution time?

Average resolution time is the average time between a customer opening a ticket or chat and that issue being marked solved.

Average resolution time = total time to resolve all issues ÷ number of issues resolved

If you solved 200 tickets this week and together they took 1,600 hours from creation to solved, your average resolution time is 8 hours.

The TNT Chat ticket list with status, priority, SLA and assignee for every ticket

The TNT Chat ticket list with status, priority, SLA and assignee for every ticket.

Choices that change the number

Two teams can measure the same work and get very different results. Decide these up front and write them down.

Calendar hours or business hours?

A ticket that arrives at 6 pm Friday and is solved at 10 am Monday took 64 calendar hours, but maybe 1 business hour. Customers experience calendar time; your team controls business time. Track both if you can, and use business hours when setting targets for the team.

What counts as solved?

Use the moment the status changes to solved, not closed. If a ticket is reopened, most teams measure until the final solve, so reopens don't flatter the number.

Average or median?

A handful of tickets waiting weeks for a supplier will drag the average up. The median shows what a typical customer experiences. Report both, and look at the slowest 10% separately; that's where the stories of bad service come from.

Waiting on the customer

If you asked for a screenshot and the customer took two days to send it, should that count? Many help desks offer a "pending" status that pauses the clock. Be consistent and say which version you're reporting.

What's a good resolution time?

It depends on the channel and the work:

  • Live chat problems are usually solved in the same conversation, often in minutes.
  • Email and web form tickets commonly take hours to a day.
  • Technical issues that need a developer can take days, and that's fine if the customer is kept informed.

Measure your own baseline for a month, then set a target per priority. Our guide to a customer service SLA shows how to turn that into a promise.

Why resolution takes longer than it should

When you look at slow tickets, the same causes appear:

  • The ticket sat unassigned for hours.
  • The agent needed information they couldn't find.
  • It bounced between too many people.
  • Each reply waited in a queue before the next.
  • The fix needed another team that had no deadline.

Notice that most of this is waiting, not working. Total working time on a ticket is often under 15 minutes even when resolution takes two days.

7 ways to reduce resolution time

1. Route tickets automatically

A ticket that waits for someone to pick it up loses hours. Triggers in a help desk can assign by topic, channel or customer the moment it arrives.

2. Ask for everything the first time

Each back-and-forth adds a full response cycle. Ask for the order number, screenshot and device in the first reply, or in the form before the ticket is created.

3. Solve in chat when you can

A problem solved in a live conversation doesn't wait in a queue between messages. Many teams find chat cuts resolution time sharply for simple issues.

4. Give agents answers and authority

An internal knowledge base and clear rules on refunds, replacements and exceptions remove the "let me check with my manager" delay. See how to build a knowledge base.

5. Fix escalations

Write down who handles what and how fast. A clear ticket escalation process stops tickets drifting between teams.

6. Warn before targets are missed

SLA timers that alert the team before a resolution target passes let you act while there's still time, instead of reading about it in a report next week.

7. Let customers solve the simple ones

Password resets, delivery questions and "how do I" questions often don't need an agent at all. A help center and an AI assistant answering from it take those out of the queue entirely.

Don't rush to a lower number

Resolution time can be pushed down in bad ways: closing tickets before the customer confirms, splitting one problem into several tickets, or skipping the hard cases. Always read it alongside reopen rate, first contact resolution and satisfaction. If resolution time drops and satisfaction drops too, the speed isn't real.

Report it in a way people can act on

A single company-wide average hides everything useful. Break it down by:

  • Channel: chat, email, WhatsApp.
  • Priority: urgent tickets should be fastest.
  • Topic or tag: billing might be quick, shipping slow.
  • Agent or group: for coaching, not blame.

That breakdown usually points to one or two topics that make up most of the slow tickets. Fixing those moves the number more than anything else. Our guide to customer support KPIs shows how this fits into a simple dashboard.

Common questions

Is resolution time the same as handle time? No. Handle time is how long agents actively work on an issue. Resolution time is the full elapsed time the customer waits.

Should I include chats? Yes, but report them separately from tickets; mixing them makes both numbers meaningless.

How often should I check it? Weekly for the team, monthly for trends.

See your own number

Resolution time by priority, channel and agent, SLA warnings, triggers and a help center are all included in our help desk, even on the free package. Start free and see your baseline in your first week.

Keep reading