Resolution Time

5 min read

Also known as: Time to Resolution, TTR, Ticket Resolution Time

The total elapsed time from when a support ticket is opened to when it's fully resolved and closed for the customer.

Definition

Resolution time measures how long it takes your support team to fully solve a customer issue, from the moment a ticket is created to the moment it's closed with the problem fixed. It's typically reported as a median or average across a ticket cohort, often segmented by priority, channel, or issue type.

Support teams track resolution time alongside first response time to understand the full customer experience, not just how fast someone replied. It's used in SLA contracts, agent performance reviews, and capacity planning to decide when to hire or restructure tiers.

Resolution time is different from first response time (how fast you acknowledged the ticket) and handle time (the active minutes an agent spent working it). Resolution time includes all the waiting, escalation, and back-and-forth in between.

Why It Matters

Shorter resolution times correlate directly with higher CSAT, lower churn, and reduced cost per ticket. When you cut resolution time, you free agent capacity to handle more volume without adding headcount, which is the single biggest lever in support unit economics.

Teams that ignore resolution time end up with ticket backlogs that quietly compound, SLA breaches that trigger contract penalties, and customers who churn before you even realize they're frustrated. Long resolution times also mask deeper problems like broken handoffs between tiers, missing internal documentation, or product bugs nobody is escalating.

Examples in Practice

A B2B SaaS support team sets a 24-hour resolution SLA for paid-tier customers. After tracking resolution time by category, they discover billing tickets average 38 hours because they require finance team approval, prompting them to give Tier 1 agents direct refund authority up to a threshold.

A 50-person ecommerce brand notices average resolution time spiked from 6 hours to 14 hours after a product launch. Drilling into the data shows 60% of new tickets are about sizing on a single SKU, so they update the product page and add a sizing FAQ, dropping resolution time back within a week.

A managed services provider reports resolution time per client in monthly business reviews. One client's tickets average 4 days versus the 1.2-day book average, which surfaces that the client's internal IT contact is slow to approve changes, a conversation that gets escalated before it becomes a renewal risk.

Frequently Asked Questions

What is resolution time and why does it matter?

Resolution time is the total elapsed time from ticket creation to ticket close. It matters because it's the metric customers actually feel — they don't care how fast you replied if their problem stayed broken for three days. It also drives cost per ticket and agent capacity, making it one of the most leveraged numbers in any support operation.

How is resolution time different from first response time?

First response time measures how quickly an agent acknowledged a ticket, usually within minutes or hours. Resolution time measures how long until the issue was actually fixed. You can have an excellent first response time and a terrible resolution time if tickets get acknowledged fast but then sit in queues. Both metrics matter, but resolution time is what correlates with retention.

When should I start tracking resolution time?

From day one of running any support function. Even with ten tickets a week, baseline resolution time tells you whether you're improving or drifting. Once you have SLAs with customers, formal tracking is non-negotiable because breaches often carry financial penalties or credits.

What metrics measure resolution time?

Common cuts include median resolution time (better than average because outliers skew it), 90th percentile resolution time (catches the worst cases), and resolution time by priority, channel, agent, or issue category. Most teams also track SLA compliance rate, which is the percentage of tickets resolved within their target window.

What's the typical cost of slow resolution time?

Hard costs include SLA credits or refunds, which can run 5-25% of monthly contract value per breach. Soft costs are larger: research consistently shows customers who experience long resolution times churn at 2-3x the rate of those with fast resolutions, and each escalation roughly doubles the labor cost of a ticket.

What tools handle resolution time tracking?

Help desk and ticketing platforms calculate resolution time natively, and modern CRM systems with built-in support modules do the same. AI-powered support platforms go further by predicting which tickets are likely to breach SLA, auto-routing complex issues to the right tier, and surfacing patterns in long-resolution tickets so you can fix root causes.

How do I implement resolution time tracking for a small team?

Start by defining what 'resolved' means — usually the ticket status changing to closed with no reopen within 72 hours. Set one initial target like 'resolve 90% of tickets within 24 business hours' and review weekly. Segment by issue type once you have a few hundred tickets to spot patterns worth investing in.

What's the biggest mistake teams make with resolution time?

Gaming the metric by closing tickets prematurely. Agents under pressure to hit resolution targets sometimes mark issues resolved before the customer confirms the fix, which inflates the number but tanks CSAT and creates reopens. Always pair resolution time with reopen rate and CSAT so you can't improve one by sacrificing the others.

Should resolution time include time waiting on the customer?

Most mature teams track two versions: total resolution time and 'agent-active' resolution time that pauses the clock when a ticket is waiting on customer reply. The first reflects customer experience, the second reflects team performance. Reporting both prevents agents from being penalized for slow customer responses.

How do AI agents reduce resolution time?

AI agents handle Tier 1 tickets like password resets, order status, and FAQ-style questions instantly, removing them from the queue entirely. For complex tickets, AI assists human agents by drafting responses, surfacing similar past tickets, and recommending next steps, which compresses the back-and-forth that historically inflates resolution time.

The AMW Suite