Support metric guide
Ticket resolution time explained
Calculate support-ticket resolution time, compare first and full resolution, account for reopens and improve outcomes rather than close tickets early.
First resolution and full resolution can diverge when a ticket reopens.
A faster chart is not improvement if customers must contact you again.
Segment by issue type and inspect the oldest unresolved cases.
Product shortlist
Tools for resolution analysis
Reproduce a reopened ticket in each finalist and check whether the report uses first or latest resolution, business hours and the status lifecycle you need.
Zendesk
Best for: Teams that expect multiple channels, mature routing and increasing operational complexity
The Support Team plan supplies core email ticketing, routing, analytics and automations. The broader Suite adds live chat, messaging, telephony and a knowledge base.
£15 per agent/monthSupport Team, paid yearly; checked September 2026
Useful strengths
- GBP pricing and a clear entry ticketing plan
- Strong upgrade path for multichannel operations
Watch for
- Suite Team rises to £45 per agent/month
- Small teams may buy more process than they need
- 14-day trial
- GBP pricing available
- Per-agent pricing
Freshdesk
Best for: Growing teams that need proper ticketing, self-service, automation and reporting
A broad email-first help desk with ticketing, a shared inbox, a customer portal, knowledge base and out-of-the-box reporting on its entry paid plan.
$19 per agent/monthGrowth, billed annually; checked September 2026
Useful strengths
- Ticketing, shared inbox and knowledge base on Growth
- Clearer route into routing, SLAs and custom reporting
Watch for
- Omnichannel needs differ from the email-first Freshdesk plan
- AI and connector usage can add cost
- Free trial
- Email-first help desk
- Per-agent pricing
HubSpot Service Hub
Best for: Businesses that want support, sales and marketing activity on one customer record
Free tools cover basic ticketing, inbox and live chat. The dedicated advanced help-desk workspace, knowledge base, SLAs and deeper routing are concentrated in Professional and Enterprise.
Free for up to 2 usersProfessional from $90/seat/month annually plus onboarding; checked September 2026
Useful strengths
- Support history beside CRM, sales and marketing data
- Free entry tools and a large integration marketplace
Watch for
- Advanced help desk features require a large price jump
- Professional has mandatory onboarding cost
- 14-day trial
- CRM-connected service
- Two users on free tools
Zoho Desk
Best for: Budget-conscious teams and businesses already using the Zoho ecosystem
The free edition covers three users and email ticketing. Paid tiers add broader messaging, knowledge-base, reporting, automation and telephony capabilities in stages.
Free for 3 usersPaid plans vary by selected billing currency; checked September 2026
Useful strengths
- Three-user free edition
- Broad channel and Zoho integration range
Watch for
- Plan and currency selectors make budgeting less immediate
- Live chat and advanced routing are plan-dependent
- 15-day trial
- Free edition
- Three users on free plan
Ticket resolution time answers how long it took from a support request to a recorded solution. That sounds simple until a case is reopened, paused for a customer response or marked solved automatically. The number is valuable only when it describes a dependable customer outcome.
Zendesk explicitly separates first resolution time and full resolution time: creation to the first solve versus creation to the latest solve. Freshdesk's support metrics describe resolution SLA time from ticket creation to resolution. These definitions should prompt you to test your own lifecycle rather than compare vendor dashboard headings at face value.
Use a documented formula
Ticket resolution time = selected solved timestamp − ticket creation timestamp. If a case arrives Monday at 10:00 and is genuinely solved Wednesday at 10:00, its calendar resolution time is 48 hours. If it was first marked solved Monday afternoon, reopened Tuesday and finally solved Wednesday, first and full resolution time tell different stories. Record both if reopens are meaningful in your operation.
State the clock as well. Business hours can be fair for a published weekday service commitment; calendar hours show the customer's total wait. A case can be within an internal business-hours target while still feeling slow after a weekend. Where both matter, display both rather than arguing that one is “the” truth.
Define a resolved case carefully
A case is not resolved merely because an agent has sent the last visible reply. A refund may still await approval; an engineering fix may not be deployed; a delivery investigation may require a carrier response. Use statuses such as waiting on customer, waiting on internal team and waiting on supplier so an owner knows the next action. Keep the customer-facing owner accountable for updates even when another team holds the work.
Test automatic closure rules. If an unanswered ticket closes after a fixed period, check how it affects the resolution chart, reopen count and customer experience. A 24-hour auto-close may make the median look better while producing more repeat contacts. The reopen-rate guide gives a companion check.
Read distributions and case mix
Report a median and a slow-tail measure, such as the 90th percentile or oldest unresolved cases. A few long investigations can inflate an average, while a median can conceal customers stuck for weeks. Keep unresolved tickets on the backlog report rather than analysing only completed cases.
Segment by issue type and priority. A password reset and a payment dispute need different work, even if both are tickets. If one month has more complex disputes, a higher resolution time does not automatically mean agents became less effective. Compare categories across comparable periods and read a sample of the longest cases to locate real bottlenecks.
Improve the process behind the number
Separate customer waiting from internal handling. If the delay is assignment, improve routing. If it is a missing customer detail, improve the intake form. If it is a specialist hand-off, agree an internal response owner and escalation point. If it is repeated diagnosis, create a troubleshooting article or safe macro. For each improvement, monitor full resolution, reopens and CSAT together.
Do not rank agents by raw resolution time. Complexity, working hours, partial shifts and ownership transfers make comparisons misleading. Use the metric to spot a process dependency, then coach with representative cases. The outcome is fewer customers waiting for an answer that lasts.
Sources
The workflow and product-fit conclusions are Support Sorted's editorial judgement.
Frequently asked questions
Questions readers ask before choosing
How is ticket resolution time calculated?
Subtract the ticket creation timestamp from the selected resolution timestamp, then apply your chosen calendar- or business-hours clock. State whether “resolution” means the first or latest solve after reopens.
What is the difference between first and full resolution time?
First resolution ends at the first time the ticket is marked solved. Full resolution ends at the latest solve, so a reopened case can have a longer full-resolution duration.
Should customer-waiting time be excluded?
Keep the total customer journey visible, then add status-based views for time waiting on the customer, a supplier or an internal team. Removing waiting periods entirely can conceal a stalled case.
Does a low resolution time mean good support?
Not by itself. It can fall because of easy-case mix or premature closure. Pair it with reopens, repeat contacts, customer feedback and a sample of actual outcomes.