Resolution Time

Resolution Time is the total duration from when a customer first reports an issue or submits a support request until it’s completely resolved and closed. This critical customer service metric encompasses all interactions, follow-ups, and work required to fully address the customer’s concern, making it a comprehensive measure of support efficiency and effectiveness.

Understanding resolution time is essential for making informed decisions about staffing levels, process improvements, and resource allocation within customer support operations. Teams use this metric to identify bottlenecks, set realistic customer expectations, and measure the impact of training or system changes on overall support performance.

High resolution times often signal understaffing, complex processes, or inadequate tools, potentially leading to customer frustration and churn. Conversely, low resolution times typically indicate efficient support operations and well-trained agents, contributing to higher customer satisfaction and loyalty. Resolution time closely correlates with other key support metrics including First Response Time, Customer Satisfaction Score, and Conversation Resolution Rate, as improvements in one area often drive positive changes across all related metrics.

“We’ve learned that speed of resolution is just as important as the quality of the solution. Customers remember how quickly you solved their problem, and that memory shapes their entire relationship with your brand.”

— Marc Benioff, CEO, Salesforce

Resolution time calculation is straightforward once you understand the core components. The metric measures the average duration between issue creation and final resolution across your support tickets.

Formula:
Resolution Time = Total Resolution Duration / Number of Resolved Tickets

The numerator (Total Resolution Duration) represents the sum of all individual resolution times for closed tickets within your measurement period. This duration typically includes business hours only, excluding weekends and holidays when your support team isn’t active. The denominator (Number of Resolved Tickets) counts all tickets that reached a “closed” or “resolved” status during the same timeframe.

You’ll typically pull resolution duration data from your helpdesk system’s ticket timestamps, while the ticket count comes from your support platform’s reporting dashboard.

Worked Example

Consider a support team that resolved 50 tickets last week with the following resolution times:

• 20 tickets resolved in 2 hours each = 40 hours
• 15 tickets resolved in 4 hours each = 60 hours
• 10 tickets resolved in 8 hours each = 80 hours
• 5 tickets resolved in 24 hours each = 120 hours

Total Resolution Duration: 40 + 60 + 80 + 120 = 300 hours
Number of Resolved Tickets: 50

Resolution Time = 300 hours ÷ 50 tickets = 6 hours average

Variants

Business Hours vs. Calendar Time: Business hours resolution time excludes nights, weekends, and holidays, providing a more accurate picture of actual working time spent. Calendar time includes all hours, which may inflate your metrics unfairly.

First Contact Resolution vs. Multi-Touch Resolution: Some teams separate tickets resolved in the first interaction from those requiring multiple exchanges, as these represent different service quality levels.

Priority-Based Calculations: Calculate separate resolution times for high-priority, medium-priority, and low-priority tickets, since service level agreements often vary by urgency.

Common Mistakes

Including Unresolved Tickets: Only count tickets that actually reached resolution status. Including open or pending tickets skews your average downward and provides false performance indicators.

Mixing Time Zones: Ensure all timestamps use consistent time zones, especially for global support teams. Inconsistent time zone handling can create artificial resolution time variations.

Ignoring Auto-Resolved Tickets: Some tickets close automatically due to customer inactivity rather than actual resolution. These should be excluded or tracked separately to maintain calculation accuracy.

While it’s natural to want clear benchmarks for resolution time, context is everything. Industry standards should guide your thinking and help you spot when something’s off, but they shouldn’t become rigid targets that ignore your unique business circumstances.

Resolution Time Benchmarks

Context Matters More Than Benchmarks

These benchmarks provide a useful reality check—if your B2B SaaS company is averaging 10 days to resolve tickets, you know there’s likely room for improvement. However, many customer service metrics exist in tension with each other. Optimizing resolution time in isolation can actually harm your overall support effectiveness.

The Resolution Time Balancing Act

Consider how resolution time interacts with first response time and customer satisfaction. If you pressure agents to close tickets quickly, you might see resolution time improve while customer satisfaction plummets due to rushed, incomplete solutions. Conversely, if you focus heavily on thorough problem-solving, resolution time may increase but customer satisfaction and conversation resolution rate could improve significantly.

For example, a company moving upmarket to enterprise clients might see their resolution time increase from 12 hours to 48 hours—not because their support got worse, but because enterprise customers have more complex technical environments and higher expectations for comprehensive solutions. In this case, longer resolution time paired with higher customer satisfaction scores actually indicates improved service quality.

When your resolution time spikes, it’s rarely a single culprit. Here’s how to diagnose what’s driving delays in your support process.

Complex Issues Are Dominating Your Queue
Look for an increase in technical or multi-departmental tickets that require escalation. If your Agent Performance Analysis shows longer handle times across the board, or your Support Ticket Escalation Rate is climbing, you’re likely dealing with more complex cases. These issues cascade into longer resolution times because they require specialized knowledge or multiple touchpoints.

Your First Response is Lagging
Check your First Response Time metrics. When customers wait longer for initial acknowledgment, they often become frustrated and less cooperative, making subsequent interactions more difficult. This creates a compounding effect where delayed first responses lead to extended back-and-forth conversations.

Agent Capacity is Stretched Too Thin
Monitor ticket volume against agent availability. If your Conversation Resolution Rate is dropping while volume increases, your team is likely overwhelmed. Overloaded agents take shortcuts, miss context, or provide incomplete solutions that require follow-up interactions.

Process Gaps Are Creating Friction
Examine tickets that require multiple agent handoffs or get stuck in pending status. Poor internal processes, unclear escalation paths, or inadequate knowledge bases force agents to spend time hunting for information instead of solving problems.

Customer Expectations Aren’t Aligned
Review your Customer Satisfaction Score alongside resolution times. Sometimes “high” resolution time reflects unrealistic customer expectations rather than actual performance issues. If satisfaction remains high despite longer resolution times, your customers may actually prefer thorough solutions over speed.

The key to reducing resolution time lies in identifying which factors are most impactful in your specific environment.

Implement Tiered Support with Smart Routing
Route tickets based on complexity and agent expertise rather than random assignment. Create clear escalation paths where Level 1 handles routine issues while specialists tackle complex problems immediately. This prevents simple tickets from getting stuck with overwhelmed senior agents and ensures complex issues reach the right expertise faster. Track resolution time by tier to validate that routing improvements are working.

Build a Comprehensive Knowledge Base and Macros
Develop standardized responses for common issues and empower agents with searchable internal documentation. When agents can quickly access proven solutions, resolution time drops significantly. Use cohort analysis to identify your most frequent ticket types, then create detailed playbooks for each. Monitor which macros get used most and track resolution time improvements for tickets using standardized responses.

Set Clear Internal SLAs with Escalation Triggers
Establish time-based escalation rules that automatically flag stalled tickets before they become problems. If a ticket sits untouched for your target first response time, it should escalate to a supervisor. This prevents issues from languishing in queues and creates accountability. Track escalation rates alongside resolution time to ensure your triggers are calibrated correctly.

Use Data to Identify Process Bottlenecks
Analyze your support data by time period, agent, and issue type to spot patterns. Look for tickets that consistently take longer than average—these reveal process gaps or training needs. Run cohort analysis on resolution times by month to see if improvements stick or if problems resurface. A/B testing different approaches with similar ticket types helps validate which process changes actually reduce resolution time.

Cross-Train Agents on Multiple Issue Types
Reduce handoffs by ensuring agents can handle a broader range of issues. When fewer tickets need to bounce between departments, resolution time improves dramatically. Track resolution time before and after cross-training initiatives to measure impact.

Stop calculating Resolution Time in spreadsheets and losing valuable insights in manual processes. Connect your customer support data and ask Count to automatically calculate, segment, and diagnose your Resolution Time in seconds—giving you instant visibility into what’s driving delays and how to fix them.