Support leaders are drowning in data. Every help desk platform generates dozens of reports, and every vendor claims their tool will improve your metrics. But which metrics actually matter? Which ones tell you whether your support operation is healthy — and which ones are vanity numbers that look good in a dashboard but mean nothing for the business?

This guide covers the 12 help desk efficiency metrics that genuinely matter, how to calculate each one correctly, what good performance looks like, and how AI automation affects each metric.

Why Most Support Teams Track the Wrong Things

The most commonly tracked support metric is ticket volume. It is also one of the least useful.

High ticket volume could mean your product has problems, your documentation is poor, your customers are engaged, or your business is growing. Without context, it tells you nothing about efficiency.

The metrics that matter are the ones that connect support performance to business outcomes: customer retention, agent productivity, cost efficiency, and service quality. Here are the 12 that do that.

---

Metric 1: First Contact Resolution Rate (FCR)

What it measures: The percentage of tickets resolved in a single interaction, without requiring follow-up from the customer.

How to calculate it:

FCR = (Tickets resolved on first contact / Total tickets) × 100

What good looks like: Industry benchmarks vary by sector, but 70–75% is generally considered strong for a B2B SaaS support team. Below 60% suggests systemic issues with agent knowledge, tooling, or knowledge base quality.

Why it matters: FCR is the single best predictor of customer satisfaction. Customers who need to contact support multiple times for the same issue are significantly more likely to churn.

How AI affects it: AI resolution systems dramatically improve FCR for L1 tickets by providing complete, accurate answers on the first automated response. See our first contact resolution guide for the full methodology.

---

Metric 2: Average Handle Time (AHT)

What it measures: The average time an agent spends on a ticket from opening to resolution, including any follow-up.

How to calculate it:

AHT = (Total handle time across all tickets) / (Total tickets handled)

What good looks like: For L1 tickets, 8–12 minutes is typical. For complex L2/L3 tickets, 20–45 minutes is normal. If your AHT is significantly higher than these benchmarks, investigate whether agents have adequate tooling and knowledge base access.

Why it matters: AHT directly drives staffing costs. Reducing AHT by 20% is equivalent to adding 20% more capacity without hiring.

How AI affects it: AI automation removes L1 tickets from the agent queue entirely, which improves the apparent AHT for remaining tickets (since agents are handling a higher proportion of complex work). More importantly, AI-assisted tools that surface relevant knowledge base articles reduce AHT for tickets that do require human handling.

---

Metric 3: Ticket Resolution Time (TRT)

What it measures: The elapsed time from ticket creation to resolution — including any time the ticket spent waiting in the queue.

How to calculate it:

TRT = Timestamp of resolution - Timestamp of ticket creation

What good looks like: For L1 tickets, under 4 hours is strong; under 1 hour is excellent. For complex tickets, 24–48 hours is typical. Customers who receive resolutions within 1 hour report significantly higher satisfaction than those who wait longer.

Why it matters: TRT is what customers experience. AHT is what agents experience. Both matter, but TRT is the one that drives CSAT scores.

How AI affects it: Automated resolutions are delivered in minutes, not hours. This has an outsized impact on TRT for L1 tickets. See our guide on reducing ticket resolution time for the full framework.

---

Metric 4: Customer Satisfaction Score (CSAT)

What it measures: Customer satisfaction with a specific support interaction, typically measured via a post-resolution survey.

How to calculate it:

CSAT = (Positive responses / Total survey responses) × 100

What good looks like: Above 85% is strong for B2B SaaS. Below 75% indicates systemic quality issues. Note that CSAT surveys typically have low response rates (10–30%), so your data may not be representative.

Why it matters: CSAT is the leading indicator of retention. Customers with consistently poor support experiences churn at 2–3× the rate of satisfied customers.

How AI affects it: AI resolution improves CSAT through speed (faster resolutions) and consistency (no variation in response quality based on which agent handles the ticket). See our guide on improving CSAT with AI.

---

Metric 5: SLA Compliance Rate

What it measures: The percentage of tickets resolved within the contracted service level agreement timeframe.

How to calculate it:

SLA compliance = (Tickets resolved within SLA / Total tickets) × 100

What good looks like: Above 95% for first-response SLAs; above 90% for resolution SLAs. Below 85% creates contractual risk and customer dissatisfaction.

Why it matters: SLA breaches have direct financial consequences — service credits, contract termination clauses, and reputational damage. For enterprise support teams, SLA compliance is often the most scrutinised metric.

How AI affects it: Automated resolutions are delivered instantly, making SLA compliance near-perfect for L1 tickets. This dramatically improves overall compliance rates. See our SLA compliance guide.

---

Metric 6: Cost Per Ticket (CPT)

What it measures: The fully-loaded cost of resolving a single support ticket.

How to calculate it:

CPT = (Total support costs) / (Total tickets resolved)

Total support costs should include: agent salaries and benefits, management overhead, tooling costs, office/infrastructure, and training.

What good looks like: For B2B SaaS, £8–£15 per ticket is typical for L1 tickets handled by agents. Automated resolutions cost £0.50–£2.00 per ticket.

Why it matters: CPT is the primary driver of support ROI calculations. Reducing CPT while maintaining quality is the core value proposition of support automation. See our cost per support ticket guide for the full methodology.

How AI affects it: Automating 60–70% of L1 tickets at £1 per ticket versus £12 per agent-handled ticket reduces blended CPT by 40–60%.

---

Metric 7: Ticket Deflection Rate

What it measures: The percentage of potential tickets that are resolved before reaching the support queue — through self-service, knowledge base articles, or automated responses.

How to calculate it:

Deflection rate = (Deflected interactions / (Deflected + Submitted tickets)) × 100

What good looks like: Above 30% is strong; above 50% is excellent. Note that deflection rate is only meaningful if deflected interactions actually resolve the customer's problem — deflection that frustrates customers is worse than no deflection.

Why it matters: Deflected tickets cost nothing to resolve. Improving deflection rate is the highest-leverage way to reduce support costs.

How AI affects it: AI resolution systems can be deployed at the point of ticket submission to resolve issues before they enter the queue. See our guide on ticket deflection versus resolution for the important distinction between the two.

---

Metric 8: Agent Utilisation Rate

What it measures: The percentage of available agent time spent on productive support work.

How to calculate it:

Utilisation = (Time on support work / Total available time) × 100

What good looks like: 70–80% is healthy. Above 85% leads to burnout and quality degradation. Below 60% suggests overstaffing or poor workload distribution.

Why it matters: Utilisation is the efficiency metric for your human capital. Under-utilised agents are expensive; over-utilised agents make mistakes and leave.

How AI affects it: By removing L1 tickets from the queue, AI automation reduces utilisation for teams that are currently over-utilised — giving agents breathing room to handle complex work well. For teams that are under-utilised, it enables headcount reduction or redeployment.

---

Metric 9: Reopen Rate

What it measures: The percentage of resolved tickets that are reopened because the resolution was incomplete or incorrect.

How to calculate it:

Reopen rate = (Reopened tickets / Total resolved tickets) × 100

What good looks like: Below 5% is strong; below 2% is excellent. High reopen rates indicate resolution quality problems.

Why it matters: Reopened tickets cost twice — once to resolve incorrectly, once to resolve correctly. They also damage CSAT and erode customer trust.

How AI affects it: AI systems with well-calibrated confidence thresholds have low reopen rates because they only automate resolutions they are confident about. Uncertain tickets are escalated to humans rather than resolved incorrectly.

---

Metric 10: Escalation Rate

What it measures: The percentage of tickets that require escalation from L1 to L2 or L3 support.

How to calculate it:

Escalation rate = (Escalated tickets / Total tickets) × 100

What good looks like: Below 20% for a well-structured support operation. Above 35% suggests L1 agents lack the knowledge or tools to handle their scope.

Why it matters: Escalations are expensive — L2/L3 agents cost more, and escalated tickets take longer to resolve. Reducing unnecessary escalations is a significant cost lever.

How AI affects it: AI systems that handle L1 tickets automatically reduce the total escalation rate. More importantly, they improve the quality of escalations by providing agents with full context, confidence scores, and relevant knowledge base articles.

---

Metric 11: Knowledge Base Utilisation Rate

What it measures: The percentage of tickets where agents accessed the knowledge base during resolution.

How to calculate it:

KB utilisation = (Tickets with KB access / Total tickets) × 100

What good looks like: Above 60% for L1 tickets. Low KB utilisation suggests agents are not using available resources, which leads to inconsistent responses and longer handle times.

Why it matters: Knowledge base quality and utilisation are the foundation of both agent performance and AI resolution quality. A team that does not use its knowledge base cannot benefit from AI automation.

How AI affects it: AI systems that surface relevant KB articles during agent-handled tickets improve utilisation rates. More importantly, the quality of AI automated responses depends entirely on KB quality — which creates a virtuous cycle where teams invest more in KB maintenance.

---

Metric 12: Agent Satisfaction Score (ASAT)

What it measures: How satisfied your support agents are with their work, tools, and working conditions.

How to calculate it: Regular pulse surveys, typically monthly or quarterly, using a 1–10 scale or NPS format.

What good looks like: Above 7/10 is healthy. Below 6/10 predicts high turnover.

Why it matters: Agent satisfaction predicts agent retention, and agent retention predicts support quality. Replacing a support agent costs 50–200% of their annual salary in recruiting, onboarding, and ramp time. High turnover is one of the most expensive problems in support operations.

How AI affects it: Agents who spend their days on repetitive L1 tickets report lower job satisfaction than those handling complex, interesting problems. AI automation that removes the repetitive work consistently improves ASAT scores — and reduces the support agent burnout that drives turnover.

---

Building a Metrics Dashboard

Tracking 12 metrics manually is not practical. Here is how to prioritise:

Tier 1 (review weekly): FCR, TRT, CSAT, SLA compliance Tier 2 (review monthly): CPT, AHT, reopen rate, escalation rate Tier 3 (review quarterly): Deflection rate, utilisation rate, KB utilisation, ASAT

Most help desk platforms provide Tier 1 and Tier 2 metrics natively. Tier 3 metrics often require custom reporting or supplementary tools.

How AI Automation Moves the Needle

Across all 12 metrics, AI ticket resolution has a consistent directional effect:

Metric	Direction	Typical Improvement
First Contact Resolution	↑	+10–20 percentage points
Average Handle Time	↓	20–40% reduction
Ticket Resolution Time	↓	60–80% reduction for L1
CSAT	↑	+5–15 points
SLA Compliance	↑	+10–20 percentage points
Cost Per Ticket	↓	40–60% reduction
Deflection Rate	↑	+20–40 percentage points
Reopen Rate	↓	30–50% reduction
Escalation Rate	↓	20–40% reduction
Agent Satisfaction	↑	Qualitative improvement

Use our ROI calculator to model the financial impact of these improvements on your specific operation.

Getting Started

The first step is establishing your baseline. Before implementing any automation, measure your current performance on all 12 metrics. This gives you the before/after comparison that makes the ROI case compelling.

If you are ready to see how AI automation affects your metrics in practice, start a free trial — TicketResolve AI connects to your existing help desk and gives you real performance data on your actual ticket history within days.