Metric Definition
Output per available hour
Track from
Agent productivity score
Agent productivity score is a measure of how much useful support work an agent completes relative to the time they are available to work. It rewards resolved contacts and active handling while penalising idle and unproductive time. The aim is to capture genuine output, not raw activity or hours logged.
7 min read
What is agent productivity score?
Agent productivity score is a measure of how much useful support work an agent completes relative to the time they are available to work. If an agent resolves 40 tickets across a 7 hour available shift, the simplest version of the score is roughly 5.7 resolutions per available hour. More refined versions weight that output by quality so that rushed, reopened tickets do not inflate the number.
The score matters because it separates effort from outcome and hours from results. An agent logged in all day can still be unproductive if most of that time is idle, in wrap-up or spent on tickets that bounce back. By dividing real output by the time genuinely available, productivity isolates the part of performance a team can plan and staff around.
Available time is the honest denominator
Dividing output by total shift length punishes agents for breaks, training and meetings they were told to attend. Use scheduled available time, the period an agent was actually expected to take work, so the score measures productivity rather than attendance.
How to calculate agent productivity score
At its core the score is productive output divided by available time. The judgement sits in how you define each side. Output can be resolved tickets, handled contacts or a quality-weighted blend of both. Available time should exclude scheduled non-handling activities, so the denominator reflects time the agent could genuinely have been working.
Without a quality weight, the formula quietly rewards speed over outcome. A version that multiplies output by a resolution-quality factor keeps a fast but sloppy agent from outscoring a steady, effective one.
- 1
Productive output
Count resolved tickets or actively handled contacts in the period, ideally weighted by resolution quality.
- 2
Available time
Take scheduled time minus breaks, training and meetings, leaving the time the agent could take work.
- 3
Quality weight
Apply a factor for reopen rate or satisfaction so closed-but-not-solved work does not inflate the score.
- 4
Normalisation
Express the result per available hour so part-time and full-time agents can be compared fairly.
Agent productivity score in a metric tree
Productivity is a ratio of output to time, so it moves when either side shifts. A metric tree separates the output drivers from the time drivers, then breaks each into the levers a team can pull. When productivity falls, the tree shows whether output dropped, idle time grew or the difficulty of incoming work changed, which lead to very different fixes.
Metric tree insight
A drop in productivity is rarely about the agent trying less. It is often idle time from poor routing, a heavier complexity mix, or tooling that slows every resolution. KPI Tree assigns RACI ownership to each branch, so a workforce manager owns scheduling and idle time while a support operations lead owns enablement. When the score moves, the push reaches the owner who can actually change that driver.
Agent productivity score benchmarks
Productivity benchmarks depend heavily on channel and ticket type, so the ranges below are directional. Chat agents handle several conversations at once and so post higher resolution counts than phone agents on complex issues. The benchmark exists to flag the outliers, not to set a single quota.
| Channel | Resolutions per available hour | Healthy occupancy | Watch zone |
|---|---|---|---|
| Email and tickets | 4 to 7 | 70 to 85 percent | Above 90 percent |
| Live chat | 6 to 12 | 70 to 85 percent | Above 90 percent |
| Phone | 3 to 6 | 65 to 80 percent | Above 85 percent |
| Complex and escalations | 1 to 3 | 60 to 75 percent | Above 80 percent |
How to improve agent productivity score
Improving productivity means lifting useful output or reclaiming wasted time, without trading away quality. The levers below target both sides of the ratio.
Cut idle and wrap-up time
Tighten routing and after-contact work so available time turns into handling time rather than dead space between tickets.
Deflect and automate the routine
Move repetitive queries to self-service and macros so agent hours go to the work that genuinely needs a person.
Balance the work mix
Route by skill so complex tickets reach specialists and simple ones do not clog senior agents, lifting output across the team.
Protect quality as you push
Keep the quality weight in the score so faster handling does not quietly raise reopen rates and erase the gain.
Common mistakes when tracking agent productivity score
- 1
Dividing by total shift length
Counting breaks and training as productive time understates the score and punishes scheduled non-handling work.
- 2
Leaving quality out of the score
Pure output rewards rushing. Without a quality weight, reopened tickets are counted as productive work twice over.
- 3
Comparing channels head to head
A chat agent will always out-resolve a phone agent on volume. Compare within channel, not across it.
- 4
Treating high occupancy as a goal
Occupancy above the watch zone burns agents out and raises errors. Sustained productivity needs slack, not saturation.
Related metrics
Average resolution time
Customer Support Metrics
Metric Definition
Average Resolution Time = Total Resolution Time Across All Tickets / Total Tickets Resolved
Average resolution time measures the mean elapsed time from when a support ticket is created to when it is fully resolved and closed. It captures the end-to-end customer experience of getting an issue fixed, encompassing wait times, agent work time, escalations, and any back-and-forth exchanges required to reach a solution.
First response time
Customer Support MetricsMetric Definition
FRT = Total First Response Times / Total Tickets With a First Response
First response time measures the elapsed time between a customer creating a support ticket and receiving the first substantive response from a human agent. It is the metric that shapes the customer's initial impression of the support experience and sets the tone for the entire interaction.
Ticket volume
Customer Support MetricsMetric Definition
Ticket Volume = Total New Tickets Created in Period
Ticket volume is the total number of new support tickets created within a defined period. It is the fundamental demand metric for support operations, determining staffing requirements, budget allocation, and the urgency of self-service and product quality investments.
Customer satisfaction score
CSAT
Product MetricsMetric Definition
CSAT = (Satisfied Responses / Total Responses) × 100
Customer satisfaction score measures how satisfied customers are with a specific interaction, product, or experience. Unlike NPS which measures loyalty, CSAT captures satisfaction at a moment in time, making it ideal for evaluating specific touchpoints in the customer journey.
Metric trees for customer success
Metric Definition
See how agent productivity score sits within a wider customer support metric tree so the team is measuring output alongside quality and resolution outcomes.
Input metrics vs output metrics
Metric Definition
Agent productivity score is an output measure, so understanding which inputs drive it helps the team improve it rather than just watch it.
Model agent productivity as a tree with an owner on every lever
Decompose the productivity score into output, available time, work mix and enablement, then put a named owner on each branch with RACI. When productivity moves, KPI Tree pushes the alert to the accountable owner and verifies whether the change actually held.
