Support is one of the few business functions where the quality of the work directly and immediately affects customer retention. A customer with a bad support experience is significantly more likely to churn. A customer with a great one is more likely to stay and refer others.
But measuring "quality" requires the right metrics. Tracking the wrong ones — or tracking too many — produces noise rather than insight. This guide covers the metrics that actually drive decisions, what they measure, and how to interpret them.
The Core Metric Categories
Support metrics fall into four categories:
- Speed: how quickly your team responds and resolves
- Quality: how well the response actually serves the customer
- Volume: how many requests your team handles and from where
- Efficiency: how much work your team accomplishes per resource
A balanced scorecard includes at least one metric from each category. Teams that track only speed tend to incentivize fast, low-quality responses. Teams that track only quality lose sight of the operational picture.
Speed Metrics
First Response Time (FRT)
The time between a ticket being created and an agent sending the first reply. FRT is the most important individual metric in customer support because it has the largest direct impact on customer satisfaction. A fast first response — even one that says "we have received your request and are investigating" — dramatically reduces customer anxiety and follow-up contact.
Target: set by priority tier (e.g. Urgent: 1 hour, High: 4 hours, Medium: 1 business day). Measure separately for each priority level.
Watch for: averages that mask extreme outliers. A 2-hour average FRT is misleading if 10% of tickets wait 48 hours. Monitor both the median and the 90th percentile.
Resolution Time (also: Time to Close)
The total time from ticket creation to ticket closure. Resolution time is more variable than FRT because it depends on the complexity of the issue and on how long the customer takes to respond — time that is outside the agent's control.
For more useful data: measure agent handle time (total time the ticket is in an active Open or In Progress status, excluding Pending time waiting for the customer) separately from the wall-clock resolution time.
Time Between Replies
For multi-touch tickets, how long does the customer wait between the agent's response and the next agent action? Tickets that have a fast first response but then stagnate mid-conversation still produce frustrated customers.
Quality Metrics
Customer Satisfaction Score (CSAT)
A post-resolution survey, typically asking the customer to rate their satisfaction on a 1–5 or thumbs-up/thumbs-down scale. CSAT is the most direct measure of whether a support interaction left the customer happy.
Best practice: send the CSAT survey automatically when a ticket is marked resolved, not closed. Many tickets are closed by the system after inactivity — those customers may not have been satisfied, they simply stopped responding.
Benchmark: above 85% positive CSAT is generally considered strong. Below 70% warrants investigation into what types of interactions are generating negative ratings.
Caution: CSAT is self-selected — customers who feel strongly (positively or negatively) are more likely to respond than those in the middle. Use it for directional insight and trend monitoring rather than as a precise absolute score.
Ticket Reopen Rate
The percentage of resolved or closed tickets that are reopened because the customer came back with the same issue or a direct follow-up. A high reopen rate indicates that tickets are being resolved on paper without actually resolving the underlying problem — either because the answer was incomplete, inaccurate, or unclear.
Target: under 5% reopen rate is a reasonable benchmark for most support teams.
First Contact Resolution (FCR)
The percentage of tickets resolved in a single interaction — no follow-up reply required. FCR is a measure of how comprehensive and accurate your first replies are.
High FCR = agents are anticipating follow-up questions and answering them proactively. Low FCR = tickets require multiple exchanges, which is inefficient for the agent and frustrating for the customer.
Improving FCR has a multiplier effect: every ticket resolved in one touch removes one or more future touches from the queue.
Volume Metrics
Total Ticket Volume
Track total ticket volume over time. The trend is more useful than the absolute number:
- Volume growing faster than your customer base suggests customers are encountering more issues or finding fewer answers through self-service
- Volume declining relative to your customer base suggests self-service is working or the product is improving
- Sudden spikes often indicate a product bug, outage, or a confusing change to your product or pricing
Volume by Channel
How are tickets arriving — email, chat, contact form, customer portal? Channel distribution tells you where customers prefer to contact you and where you need to direct support resources.
Volume by Category
Which issue types generate the most tickets? The top categories drive your knowledge base content priorities, product improvement conversations, and agent specialization decisions.
Recurring spikes in a category often indicate either a product problem worth fixing at the root or a documentation gap that a knowledge base article could address.
New Tickets per Agent
Total ticket volume divided by number of active agents. This is your team's workload indicator. If volume per agent is consistently high, agents are either overwhelmed or becoming efficient enough to manage it — the CSAT and FRT metrics will tell you which.
Efficiency Metrics
Tickets Resolved per Agent per Day
A measure of individual agent throughput. This varies significantly by ticket complexity — a team handling mostly simple billing questions will have higher throughput than one handling complex technical troubleshooting. Compare agents within similar ticket types, not across the board.
Deflection Rate
The percentage of potential support contacts that were resolved through self-service (knowledge base, FAQ, contact form article suggestions) without becoming a ticket. This is one of the highest-value metrics for teams investing in a knowledge base.
How to measure: compare ticket volume growth to customer base growth. If customers are growing at 20% and tickets are growing at 5%, your self-service is deflecting roughly 15% of potential contacts.
A more precise method: track how many visitors view a knowledge base article and do not subsequently submit a ticket within the same session.
Cost per Ticket
Total support team cost (salaries, tools, infrastructure) divided by total tickets resolved in a period. This is a useful efficiency indicator for comparing team performance across quarters or evaluating the ROI of a new tool or process.
How to Use These Metrics
Build a Monthly Dashboard
A single-page monthly view with: FRT by priority, CSAT score, volume by channel, top 5 categories by volume, reopen rate, and deflection rate. Review it with the support team lead at the start of each month.
Set Targets and Track Trends
Absolute numbers matter less than trends. An FRT of 3.5 hours is unremarkable in isolation. An FRT of 3.5 hours trending down from 6 hours over three months is a significant improvement. Set a target for each metric and track the trend toward it.
Use Agent-Level Data Carefully
Agent-level metrics (individual FRT, CSAT, resolution rate) are useful for coaching and training, not for ranking or public leaderboards. Surface this data privately between the agent and their manager. Use it to identify both agents who need support and agents who are performing well in ways others can learn from.
Metrics to Avoid (or Use Carefully)
Handle time as a primary metric: pushing agents to close tickets faster incentivizes premature resolution — marking a ticket resolved before the issue is actually fixed to beat the clock. Track handle time as context, not as a performance target.
Volume as a performance target: telling agents their goal is to close 40 tickets per day will produce 40 low-quality closes. Volume is an input metric (workload), not an output metric (performance).
How Nura24 Supports Support Metrics
Nura24's reporting section provides ticket volume by channel, category, and agent; first response time tracking by priority level; CSAT scores from post-resolution surveys; reopen rate tracking; and SLA compliance reports. The knowledge base module reports article views and helpfulness ratings, feeding into the deflection picture. For support managers who want a single workspace where support data — from first contact to resolution — is tracked without switching between tools, Nura24 consolidates the operational and quality metrics in one place.