What is Resolution Time?

Resolution time is the elapsed clock time between a customer's first contact and the moment their issue is fully closed. It is also called time to resolution (TTR) and is reported as a median or mean across a date range, channel, priority, or issue category.

The formula is simple: resolution_time = ticket_closed_at − ticket_opened_at. Unlike average handle time, which counts only the agent's active work on a conversation, resolution time runs the full calendar clock — including time spent waiting on the customer to reply, internal escalations, overnight gaps, and queue delays.

Channel ranges differ by an order of magnitude, so cross-channel comparisons are not useful. Live chat conversations typically resolve in 10–25 minutes, phone calls in 6–12 minutes of talk time, email in 12–72 hours, and messaging app threads (WhatsApp, Telegram, Messenger) anywhere from 30 minutes to 24 hours depending on whether the customer stays in the thread or replies after hours. Track each channel against its own baseline, and use median rather than mean — a few stuck tickets (chargeback disputes, bugs waiting on an engineering release) will skew the mean by days and hide what most customers actually experience.

Resolution time is one of the few support metrics that correlates with both satisfaction and cost. Zendesk's 2025 CX Trends Report identified speed of resolution as the single largest driver of negative CSAT outside of first response, with 70% of consumers spending more with companies that offer fluid experiences. Drawn-out tickets surface in negative reviews, churn surveys, and refund requests — a customer who waits 5 days for a fix often does not return for the second purchase.

Cost scales the same direction. McKinsey's 2024 customer-service research found that operating expense per ticket scales roughly linearly with total handle and resolution time: every additional hour of resolution adds touches, escalations, and reopens. Halving median resolution time typically reduces cost per ticket by 20–35% because faster resolution also produces fewer reopened tickets — and a reopen is a full second ticket from the cost side.

The diagnostic power shows up when you slice the metric. If billing tickets close in 6 minutes but integration tickets sit at 4 days, the integration documentation is the bottleneck, not the agents. The category breakdown tells you where to invest in self-service content, internal runbooks, or training.

A 6-person SaaS support team measured a median resolution time of 14 hours overall, but discovered that integration-related tickets averaged 4.2 days. The bottleneck was context transfer to engineering: engineers kept asking customers to re-paste error logs because the support thread did not include them. The team added a structured escalation note template — required fields for reproduction steps, version, error payload, and customer environment — that agents had to fill before handing off. Within two months, integration-ticket resolution dropped to 1.6 days and the reopen rate fell from 18% to 6%. They run the workflow on Converge's $49/month flat rate, which lets the engineering rotation read the same inbox without per-seat fees pricing them out.