Glossary

Resolution time

Resolution time is how long it takes to solve a customer's problem, from the moment their message arrives to the moment the conversation or ticket is marked resolved. You calculate it per ticket, then report the median and the average across tickets resolved in a period.

Last updated: 19 November 2026 · By

Fyncall wrote this entry. It makes no claims about other companies. Fyncall details come from our product pages and our docs, checked 19 November 2026.

What is resolution time?

Resolution time measures how long a customer's issue stays unsolved. The clock starts when the conversation or ticket is created and stops when it is marked resolved.

People also call it time to resolution or full resolution time. Teams often report two versions: average resolution time and median resolution time. Targets for it are usually written into an SLA.

How do you calculate resolution time?

For one ticket: resolution time = time resolved minus time created. For a period, take every ticket resolved in that period, then report the median and the average of their resolution times.

Here is a worked example for one day:

TicketCreatedResolvedResolution time
A: where is my order?09:0009:2020 minutes
B: change of address10:0011:0060 minutes
C: damaged item, needs photos10:3016:30360 minutes

The average is (20 + 60 + 360) ÷ 3, about 147 minutes. The median is 60 minutes. A few long cases, such as damaged goods or lost parcels, drag the average up, so the median is the better picture of a typical customer. Keep the average as well, because it shows that slow cases exist.

Agree the rules before you compare months:

  • Count tickets by the day they were resolved, not the day they were created, and say which you use.
  • Leave out spam and messages that needed no answer. They resolve instantly and flatter the number.
  • Track open tickets separately. Unsolved tickets have no resolution time yet, so a growing backlog does not show in the figure.
  • Choose business hours or calendar hours. Business hours show team speed. Calendar hours show what the customer waited through.

How should you handle reopened tickets?

Decide on one rule and apply it every time. The two common choices are to measure until the first time a ticket was resolved, or until the final time it was resolved.

MethodWhat it showsWeakness
Until first resolutionHow quickly the team believed the issue was fixedRewards closing tickets too early
Until final resolutionHow long the customer's problem really lastedOne late reply can stretch a ticket over days

Whichever you pick, count reopens as their own number. A falling resolution time with rising reopens usually means tickets are being closed before the problem is solved. It also helps to separate a true reopen (the fix did not work) from a new question sent on an old thread, such as a thank-you or a fresh order query.

Also decide whether time spent waiting for the customer counts. If a ticket sits for two days while you wait for photos of a damaged item, that is not team time. One way to handle it is to pause the resolution clock while a ticket is in a waiting status.

What is the difference between resolution time and first response time?

First response time measures how long the customer waits for the first reply. Resolution time measures how long they wait for the problem to be solved.

MetricFirst response timeResolution time
Clock startsWhen the message arrivesWhen the ticket or conversation is created
Clock stopsAt the first real replyWhen it is marked resolved
What it tells youWhether customers feel heardWhether problems actually get fixed
Easy to game byAutomatic acknowledgementsClosing tickets too early

Watch both. A fast first reply followed by a slow fix still leaves the customer waiting, and it often shows up later as a poor CSAT score.

How do you reduce resolution time?

Fix more issues in the first reply, and cut the back-and-forth needed to gather details. Much of the delay is often waiting between messages, not the work itself.

  1. Have order details beside the conversation. Agents who can see the order do not need to ask for an order number.
  2. Ask for everything at once. For a damaged item, request the [order number], photos and a description in one message. Return and refund reply templates help here.
  3. Let an AI agent close the simple ones. Questions like "where is my order?" can often be solved in one reply by an AI agent, with a human handoff for the rest.
  4. Review your slowest tickets each week. Look for a missing policy, a missing tool or a stuck approval.

How does Fyncall track resolution time?

SLA ticketing is part of the Fyncall Pro plan. Tickets track first response time and resolution time, and resolution deadlines are set by priority. According to the ticket preferences documentation, the default resolution deadlines are 1 hour for Urgent, 4 hours for High, 8 hours for Medium (called Normal on tickets) and 24 hours for Low, admins can change them, and tickets that pass their deadline are flagged.

According to the tickets documentation, SLA timers start when a ticket is created, and the resolution timer stops when the ticket moves to Resolved or Closed. It pauses while the ticket is Waiting on Customer and resumes when the customer responds. When a ticket is reopened (or set back to In Progress), the SLA timers resume. Reassigning a ticket does not reset the timer.

Conversations work slightly differently. When a customer messages again after a conversation is resolved, it reopens automatically, returns to the AI and reappears in your active queues, with the earlier history kept. See the helpdesk and plans.

Common questions

Should I report average or median resolution time?

Report both. The median shows the typical customer's experience, and the average shows how much the slow cases cost you.

What is a good resolution time?

There is no single right number. It depends on the type of issue, so set targets by priority or category rather than one figure for everything.

Does a reopened ticket count twice?

It should count once in resolution time, measured by the rule you chose, and once in a separate reopen count.

Is resolution time the same as handle time?

No. Handle time is how long agents actively work on a ticket. Resolution time includes all the waiting in between.

Ready to try Fyncall?

Install it tonight, let the AI draft your first replies, and switch it on one channel at a time as you start to trust it.

  • Free plan, no credit card
  • 14-day free trial on Pro
  • Unlimited human replies on every plan