In modern call centres, customer service teams, and community teams, performance is measured almost entirely through metrics.

Metrics like call handling time, emails to resolution, leaderboards, and CSAT rankings give organisations a clear way to identify who appears to be performing best.

But these assessments have two critical limitations that are often overlooked:

1. Metrics can only measure what we’ve chosen to track.
2. The boundaries staff operate within are defined by policy, not by them.

Staff who strictly enforce policies and shut down conversations quickly often record faster resolutions and shorter call times. By contrast, those who try to find workarounds or exceptions naturally see longer conversations, chats, and email threads.

In many cases, poor CSAT scores reflect policy and process constraints more than agent behaviour.

Most people aren’t deliberately gaming metrics; they’re simply doing the job as it’s been defined for them. But over time, the job quietly changes.

Those metrics, assessments and conversations make it clear to our people what their job actually is. Reward and recognition means to do it more, and punishment and negatives mean to do it less. As time passes our customer service and support staff find themselves in an entirely new role.

There’s nothing sudden about it – it’s a slow tectonic shift driven by incentives.

In interviews and training, the role is clear: to solve problems for customers.

6 months later it’s “to avoid calls exceeding 4 minutes” “to not issue credits more than $25”

Customers needs fall to the wayside in service of the script. Future issues go unserviced to avoid exceeding call timers.

When our systems reward speed over resolution, empathy is a liability.

Your best people are heartfelt and genuine — quick to engage, willing to go the extra step just to hear relief in someone’s voice. In these kinds of environments their hands are tied. They struggle to perform on paper and score worse across most metrics. They feel burdens and exhaustion from knowing what a customer needs, knowing what’s right and never being able to deliver it.

And as competent, capable adults, they don’t just feel this frustration toward the system,  they feel it toward the organisation itself.

Disengagement, attrition, and cynicism are symptoms of people being unable to do the job you expect and ask of them. These are the people you can’t afford to lose.

Customer dissatisfaction is rarely a staff failure. It’s far more often a policy or process failure. Customer feedback is not a performance score – it’s feedback on policy design, and a lens into friction points in your products and services.

Customers should feel like it’s them and the agent versus the problem. Not David and Goliath, with the company playing the terrifying part.

When is the last time you looked at your policies and compared them to customer feedback?

How often are customer complaints traced back through the company? From the policies that led their calls and emails, to the process that delivered the wrong item to them.

Great customer experience is designed upstream – long before a customer ever speaks to an agent.

Where to start

Start by separating staff performance from policy-driven outcomes. Looking at the issues customers raise most often, but also those that consistently score the lowest and talk to frontline staff about which ones they’re structurally unable to resolve. If an agent can’t fix a problem without bending policy, that’s not an issue to bring up in coaching – it’s a design constraint.

Following complaints back through the organisation to see where they flowed. From the moment a customer encountered friction, trace it to the policy, process or system that created it. Patterns matter more than outliers. Repeated complaints are clear signals pointing to where experience breaks down.

Use your metrics as indicators, not verdicts. Pair quantitative scores with real qualitative context. Reward clarity, ownership and escalation, not just speed. The goal isn’t faster interactions, but fewer problems that require them to begin with. There’s always room to speed things up later.

This kind of work sits at the intersection of customer support, community management and experience design. If you ever need a second set of eyes, Preface has spent decades helping teams build systems that support both customers and the people serving them.