Resolution Time

Resolution time is how long a support team takes to close a customer issue, from ticket creation to verified fix. It is a headline support metric that shapes churn, satisfaction scores, and cost per contact, the levers every outsourcing leader tracks.

Support leaders separate resolution time from response time. Response time captures the acknowledgment; resolution time captures the actual fix. Confusing the two rewards teams that answer fast and solve nothing.

Most contact centres report the median rather than the mean, so one runaway ticket cannot flatter the number. Consumer teams close most tickets inside a day. Business to business (B2B) tickets run longer, because the fix crosses vendors.

Buyers treat resolution time as the primary quality gauge when comparing providers. It shows up in requests for proposal (RFPs), quarterly business reviews, and renewal negotiations, usually beside satisfaction scores.

Key takeaways

• Resolution time measures how long support takes to close an issue end to end.
• It differs from response time, which only tracks the first acknowledgment.
• The median is more honest than the mean, because outlier tickets distort an average.
• Pause rules decide whether a provider is in breach, so negotiate them before you sign.
• Automation, tiered escalation, and named ownership are the biggest levers to shrink it.

How it works

Resolution time starts the second a customer opens a ticket and stops the second an agent or an automation confirms the issue is fixed. Teams measure it in business hours and segment it by channel, priority, and product line.

The stopwatch usually pauses when the ticket sits with the customer or a third party vendor, then resumes on hand back. Teams that skip that pause punish agents for delays they cannot control — and morale goes with it.

The clock starts on ticket creation, so how a ticket enters matters. Chat and self service trigger fastest. Email lags because inbox polling adds latency, and social messages land in between.

Median and mean answer different questions. The median tells you what a typical customer felt; the mean tells you what the backlog cost. Report both, then add the 90th and 95th percentiles.

Treat those bands as a starting shape, not a published standard. The only binding numbers are the ones in the contract you signed.

Formal service level agreements (SLAs) put those targets in writing. Miss the number and the provider owes credits, so resolution time becomes a contract line with a cash figure attached.

Credit clauses are why clock definitions get negotiated line by line. A generous pause rule can move a provider from breach to compliance on the same ticket set, so buyers audit the pause log.

Automation now takes a bigger bite out of the number than headcount does. A self service portal, a tuned chatbot, and a current knowledge base can shave 30 to 60 percent off the median.

Automation only clears the easy cases, though. The queue that remains skews harder over time and pulls the median back up unless you staff for complexity, not volume.

Cadence matters too. Weekly averages catch operational drift, monthly medians catch staffing gaps, and quarterly percentile splits expose the tickets an average hides.

Examples

Resolution time benchmarks vary sharply by sector, channel, and ticket complexity, so treat any single industry average with care. The examples below use operating detail from named companies, so you can check your own numbers against comparable peers.

ContactBabel’s 2026 US Contact Center Decision-Makers’ Guide and HubSpot’s 2024 State of Service report both survey support leaders rather than audit ticket logs. Read them as sentiment, then trust your own export.

Zendesk’s 2024 CX Trends report shows top quartile teams resolving most chat tickets on the first touch, with average handle times well under 15 minutes. Skill based routing, not round robin queueing, is the usual driver.

Amazon closes most order related queries in under a minute through a self service flow that asks where your parcel is before it offers an agent. Agents handle only the exceptions, which keeps the tail short.

Philippine providers serving US retail typically target resolution inside 24 hours for tier one tickets and 72 hours for tier two escalations. Manila operators publish those targets openly, because buyers compare them line by line.

In 2026, most retail proposals crossing our desk at Outsource Accelerator ask for the 95th percentile beside the median. A flattering average and a three day tail live comfortably in the same report.

Zappos publishes no resolution time SLA and lets an agent stay on one call as long as the customer needs — one famously ran past ten hours. The company tracks loyalty and lifetime value instead.

Platform defaults decide the number more often than policy does. ServiceNow and Salesforce Service Cloud both let an administrator pause the SLA clock on a configurable condition, so one ticket set reports two different times.

The pattern here is that targets follow the business model. Volume commerce optimises for speed, loyalty brands for outcome, regulated sectors for accuracy, and outsourced partners for whichever one the buyer pays for.

Related terms

Resolution time sits inside a family of support metrics that each measure a different slice of the same ticket. The neighbours below stop you optimising one number so hard that the others quietly drift.

• Customer Service: the umbrella function that owns resolution time reporting in a contact centre.
• Service-Level Agreement: the contract that binds resolution time targets between buyer and provider.
• First-Call Resolution: the share of tickets closed on first contact.
• Customer Experience: the broader outcome that resolution speed feeds into.
• Average Handle Time: the per interaction duration cousin to resolution time.
• Ticket Management: the workflow layer that logs, routes, and closes each issue.

FAQ

These are the questions buyers and support leads ask most about resolution time. The answers below cover the difference from response time, the calculation, realistic targets by severity, the strictest sectors, the tooling, and what outsourcing changes.

How is resolution time different from response time?

Response time measures how fast an agent acknowledges a new ticket. Resolution time measures how long the fix actually takes. Reporting only the first number flatters teams that reply in seconds and solve nothing.

What is a good resolution time?

Targets depend on channel and severity. A common working rule is under four business hours for critical issues, under one business day for standard tickets, and under three business days for complex escalations.

How do you calculate resolution time?

Add the in progress time for every ticket closed in the period, then divide by the number closed. Exclude paused time if your contract allows it, and state that rule on the report.

Which industries measure resolution time most strictly?

Financial services, healthcare, and mission critical software run the tightest clocks, often under four business hours for critical tickets. Regulators, patient outcomes, and revenue loss risk all push the target down.

What tools track resolution time?

Every major help desk platform — Zendesk, Freshdesk, ServiceNow, Salesforce Service Cloud, Intercom — reports resolution time out of the box. They differ in how each handles pauses, reopens, and multi touch tickets.

Does outsourcing reduce resolution time?

Well run outsourced teams often beat in house benchmarks by running 24/7 shifts and pooling subject matter experts across accounts.

Ready to tighten your resolution time numbers? Compare vetted providers on OA hubs.