Agent Productivity: How to Measure It Correctly and Improve It

Most contact centers measure agent productivity, and a surprising number measure it wrong. The formulas get inverted, the metrics get read one at a time, and a team that is doing well can look like it is failing. Before anyone coaches an agent, the numbers have to mean what everyone thinks they mean, and on many dashboards, including ones built by experienced teams, they quietly do not.

This guide covers what agent productivity is, the seven metrics that capture it with the correct formula and a worked example for each, why productivity usually drops, and six changes that raise it. It is written for contact center leaders who need numbers they can defend in a review.

What is agent productivity?

Agent productivity is how much good work an agent completes in the time available. Both halves matter, and most measurement programs quietly drop the second one because speed is easier to count than outcomes. An agent who closes forty contacts an hour and sends half of them back as repeat calls is busy. Not productive. One who resolves twenty cleanly may be the most productive person on the floor.

For that reason, no single metric captures it. Speed metrics such as handle time and calls per hour show volume. Quality metrics such as first contact resolution, satisfaction and quality scores show whether the work stuck. Time metrics such as schedule adherence and utilization show whether the capacity existed in the first place. Read one group alone and the picture tilts.

The seven agent productivity metrics, with the correct formulas

Here are the seven, each written so the result reads the way you would expect. The worked examples use round numbers for one agent across one week.

A quick check catches most errors. In every percentage metric, the smaller number sits on top. If the result comes out above 100, the division is upside down.

In addition, definitions vary between teams, especially for utilization. Some divide by paid time, others by logged-in time, which is closer to what many call occupancy. Neither is wrong. What matters is that everyone on the team, from the analyst building the dashboard to the supervisor reading it in a Monday review, uses the same one and says which it is. Our guide to agent utilization rate walks through that choice in more detail.

Reading the metrics together

Instead, the value is in the combinations, because each metric can be gamed on its own.

Handle time falling while first contact resolution also falls usually means agents are rushing and customers are calling back. Calls per hour rising while quality scores drop points the same way. Utilization above roughly 85% for weeks on end tends to show up later as absence and attrition rather than as higher output. And a strong satisfaction score beside weak adherence often means one agent is carrying a queue that others are avoiding.

So review productivity as a set. A single bad day explains nothing. Four weeks of the same pattern, on the other hand, explains a great deal about where the friction really sits. The two metrics most worth pairing are average handle time and first contact resolution, because together they show whether speed is coming at the expense of the outcome.

Schedule adherence, the most misunderstood of the seven

Schedule adherence measures whether an agent is doing what the schedule says at the time it says to do it. It is not attendance. An agent who logs in on time but takes lunch an hour early has perfect attendance and poor adherence for those two hours.

The formula is minutes in adherence divided by scheduled minutes. In the example above, the agent was scheduled for 2,400 minutes across the week and spent 2,280 of them in the right state, which gives 95%. Many operations aim for the low to mid 90s rather than 100%, because a target of perfection punishes the agent who stays on a difficult call past the start of a break.

Why does this matter? Workforce plans assume it. When adherence slips across a team, queues build at predictable times, service levels fall, and everyone else absorbs the load. It is a team metric. It just wears an individual’s name.

Calls per hour: useful, and easy to misread

Calls per hour is the metric most leaders reach for first, because it is simple and it moves quickly. It misleads easily.

Context is everything here. Ten password resets an hour is slow. Ten complex billing disputes an hour would be remarkable, and probably a sign that something is being skipped. So compare agents who take the same mix of contacts, or compare one agent against their own history.

Also, watch the denominator. Divide by hours spent handling contacts, not by the whole shift. Otherwise training time, team meetings and coaching sessions drag the number down, and the agents who attend them look least productive. Nobody wants that.

Used carefully, calls per hour is a good early warning. A sudden fall across a whole team usually points to a system problem, a new policy nobody has explained, or a spike in harder contacts. It almost never means that everyone on the floor got slower on the same day, which is the conclusion a single chart invites.

Agent productivity vs call center productivity

The two terms get used interchangeably, but they answer different questions. Agent productivity looks at the individual: how much good work one person completes in their time. Call center productivity looks at the operation: whether the whole floor meets demand at the right cost and quality.

As a result, you can improve one without the other. A team of highly productive agents can still miss its service level if the schedule puts too few of them on the phones at the busiest hour. And a well-staffed floor can hit its targets while individual agents struggle quietly. Our wider guide to call center productivity covers the operational side. This page stays with the agent.

Why agent productivity drops

When productivity falls, the first reflex is usually to look at the agents. The cause is more often the environment they work in, and the biggest single factor is how long it takes to find an answer.

The McKinsey Global Institute estimated in its 2012 report on the social economy that interaction workers spend nearly 20 percent of the workweek searching for internal information or tracking down colleagues who can help. On a contact center floor, that search happens with a customer waiting. It inflates handle time. Worse, when the agent gives up and guesses rather than keep the customer waiting any longer, the wrong answer lowers first contact resolution too and sets up a repeat contact a few days later.

Meanwhile, load is rising. In Gartner’s December 2025 release, 55% of service leaders reported stable staffing with higher customer volumes. The same agents are handling more contacts, so every minute lost to searching now costs more than it did.

How to improve agent productivity in a call center

These six changes work because they remove friction from the job itself rather than asking people who are already stretched to simply work harder, faster or longer than they do today.

1. Put answers inside the agent desktop. For example, an agent handling a billing dispute sees the refund policy open beside the case rather than searching three documents. A single call center knowledge base that surfaces inside the workflow is usually the largest productivity gain available.
2. Turn procedures with conditions into guided steps. For example, a warranty claim that depends on product, purchase date and region becomes a sequence of questions. An interactive decision tree removes the memorizing and the guessing, which lifts first contact resolution and quality scores together.
3. Measure by contact type, not in total. For example, a team whose average handle time rose may simply be taking more complex technical contacts this month. Splitting the metrics by contact type separates a real problem from a change in mix.
4. Coach on patterns, not single calls. For example, an agent whose quality score dips only on cancellation calls needs help with retention offers, not a general review. Four weeks of data shows the pattern; one call shows noise.
5. Protect schedule adherence with achievable plans. For example, if breaks consistently slip after long calls, build a buffer into the schedule instead of marking the agent down. Adherence improves when the plan reflects real call lengths.
6. Fix the content agents flag. For example, when three agents report the same outdated article in one week, correct it within days and tell them it changed. Agents stop reporting problems that never get fixed, and the searching begins again.

Measuring without burning people out

Any productivity metric can be pushed too far. Handle time targets that ignore contact type teach agents to end calls early. Utilization held near its ceiling for months tends to reappear later as sick days, quiet disengagement and eventually resignations from the people you most wanted to keep. Leaderboards are worse. A ranking by calls per hour rewards whoever avoids the hard contacts.

The better approach is to set ranges rather than single targets, review the metrics together, and treat a sudden change as a question rather than a verdict. Productivity that lasts comes from making the work easier. Productivity extracted by pressure tends to disappear, taking experienced agents with it.

Frequently asked questions about agent productivity