Resolution Time
Definition
Resolution time
Resolution time is the average duration a support team takes to fully close a customer’s issue, from ticket creation to verified fix. It’s a headline customer-service KPI that shapes churn, CSAT, and cost per contact — the three levers every BPO leader watches.
Support leaders separate resolution time from response time. Response time captures the acknowledgment; resolution time captures the actual fix. Confusing the two is the fastest way to reward slow teams that answer quickly and never solve anything.
Most contact centers report the median, not the mean, so one runaway ticket doesn’t skew the number. Best-in-class B2C teams close the majority of tickets inside a day; B2B tickets often run longer because the fix crosses vendors.
Buyers use resolution time as the primary quality gauge when comparing outsourced providers. It shows up in RFPs, quarterly business reviews, and renewal negotiations, usually alongside CSAT and first-contact resolution as the three-metric quality triangle.
Key takeaways
- Resolution time measures how long support takes to close a customer’s issue end to end.
- It differs from response time, which only tracks the first acknowledgment.
- Median resolution time is more honest than the mean; outlier tickets skew the average badly.
- Automation, tiered escalation, and named ownership are the three biggest levers to shrink it.
How it works
Resolution time starts the second a customer opens a ticket and stops the second the agent (or the automation) confirms the issue is fixed. Teams typically 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 this pause end up penalising agents for delays outside their control, which quietly poisons morale.
The clock starts on ticket creation, so how a ticket enters the system matters. Chat and self-service typically trigger fastest; email lags because inbox polling adds latency; social DMs sit somewhere in between depending on the listening tool.
| Priority tier | Typical target (business hours) | Common industry |
|---|---|---|
| P1 (critical outage) | 4 hours | SaaS, fintech |
| P2 (major impact) | 8 hours | E-commerce, telecom |
| P3 (moderate) | 24 hours | B2B services |
| P4 (low / cosmetic) | 3 business days | Enterprise IT |
Formal service-level agreements bind those targets in writing. Miss the number and the provider owes credits, so the SLA turns resolution time from a soft KPI into a contract line item with a dollar figure attached.
Automation now takes a bigger bite of the number than headcount does. A self-service portal, a well-tuned chatbot, and a solid knowledge base can shave 30 to 60 percent off median resolution time before you hire a single extra agent.
The catch is that automation only handles the easy cases, which means the remaining human queue skews harder over time and pulls the average up again if you don’t staff for it.
Reporting cadence matters as much as the raw number. Weekly averages catch operational drift; monthly medians catch staffing gaps; quarterly percentile splits (the 90th and 95th) expose the runaway tickets you’d otherwise ignore because the average looks fine.
Examples
Real-world resolution-time benchmarks vary sharply by sector, channel, and ticket complexity per HubSpot’s 2024 State of Service report, which surveyed support leaders across SaaS, retail, financial services, and outsourced contact centres in the US and Europe.
The examples below pull from published operations data at named companies so you can sanity-check your own numbers against comparable peers rather than a generic industry average.
Zendesk’s 2024 CX Trends report consistently shows top-quartile support teams resolving the majority of 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 behind those numbers.
Amazon’s customer-service model, built on obsessive ticket categorisation and heavy automation, closes most order-related queries in under a minute via the “Where’s my stuff?” self-service flow. Human agents handle only the exceptions, which shrinks the tail.
Philippine BPOs serving US retail typically target resolution inside 24 hours for tier-1 tickets and 72 hours for tier-2 escalations. Manila-based providers publish these SLAs openly because outsourcing buyers now compare them line-by-line before signing.
Zappos publishes no formal resolution-time SLA and lets agents stay on a single call as long as needed — one famously ran ten hours. The company measures loyalty and lifetime value instead, which reframes the entire debate about speed.
The lesson from these four is that resolution-time targets follow business model. Volume commerce optimises for speed; loyalty brands optimise for outcome; regulated industries optimise for accuracy, and outsourced partners tune to whichever the buyer values.
Related terms
Resolution time sits inside a broader family of support metrics. Understanding the neighbours below helps you avoid the common trap of optimising one number so aggressively that the others quietly drift in the wrong direction.
Read across the six terms below and you’ll see resolution time is really a compound metric that lives on top of ticketing hygiene, agent skill routing, escalation rules, and the SLA you signed at the top.
- Customer service: the umbrella function that owns most resolution-time metrics 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 the initial contact.
- Customer experience: the broader outcome that resolution-time 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
How is resolution time different from response time?
Response time measures how quickly a support agent acknowledges a new ticket. Resolution time measures how long the fix actually takes. Reporting only the first number hides slow teams.
What is a good resolution time?
Targets depend on channel and severity, but a common industry rule is under four 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 up the total time each ticket spent in-progress over the reporting period, then divide by the number of tickets closed. Most teams report the median alongside the mean so outliers don’t distort the story.
Which industries measure resolution time most strictly?
Financial services, healthcare, and mission-critical SaaS run the tightest SLAs, often under four business hours for critical tickets. Regulators, patient outcomes, and revenue-loss risk all push the number 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. The differences show up in how each one 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 shrink your resolution-time numbers? Compare vetted providers on OA hubs.
Independent
