Why Coaching Doesn't Work in Contact Centres - And What the System Is Hiding

There is a version of this situation that most contact centre leaders have experienced but few have named directly.

The coaching is happening. The feedback is being delivered. The one-to-ones are logged and evidenced. And somewhere in the building, an agent is sitting in a coaching session being told to improve an outcome that the process they work within will not allow them to reach.

They know it. They've known it for months. And the coaching conversation - however well-intentioned - is confirming something they already suspected: that the organisation believes the problem is them.

Understanding why coaching doesn't work in contact centres when the system is the problem starts here - not with the metric that isn't moving, but with what that coaching conversation is doing to the relationship between leader and team.

Why Coaching Doesn't Work in Contact Centres: The Structural Explanation

Coaching is a development tool. It builds capability, reinforces good practice, and closes the gap between current and expected performance. In the right context, it works.

The right context is one where the performance gap is caused by a capability deficit - where the agent genuinely lacks the skill, knowledge, or behaviour required to perform at the expected level.

When the performance gap is caused by a structural constraint, coaching doesn't work in contact centres for a straightforward reason: it's addressing the wrong layer of the problem.

Consider what happens when an agent navigates a contact that requires approval from another team before resolution is possible. The agent cannot control the approval timeline. They cannot shorten the queue. They cannot resolve the contact until the constraint releases.

That contact appears in the FCR data as a failure. The agent may be coached on resolution technique. But the cause of the failure was never resolution technique - it was authority design. And authority design is not something a one-to-one conversation can fix.

Coaching doesn't work when the system is the problem because the intervention is real, the effort is genuine, but the target is wrong. And effort directed at the wrong target produces no outcome improvement regardless of its quality.

The Illusion the Metrics Produce

The reason coaching doesn't work in contact centres goes unexamined for so long is that the measurement architecture makes it look like it should.

Outcome metrics point at agents because agents are the most visible moving part. Service levels, handle times, first contact resolution - every measure records what happened at the end of the process and traces it back to the person who was there when it went wrong.

So leaders respond to what the metrics show. Coaching increases. The structural constraint remains untouched. The outcome doesn't move. And the conclusion drawn - that the coaching needs to be more rigorous, more frequent, more targeted - doubles down on the same misdiagnosis.

The illusion is structurally produced. Leaders aren't making irrational decisions. They're making entirely rational decisions based on data that cannot see the real cause.

That distinction matters - because it means the fix isn't better leadership. It's a different diagnostic lens.

The Trust Cost of Coaching That Doesn't Work

There is a consequence of sustained coaching toward a structural constraint that rarely surfaces in performance management conversations - and it is more significant than the metric that isn't moving.

Agents who work inside a system that constrains their performance know the constraint is there. They experience it on every contact of the relevant type. They've developed workarounds, informal routes, and escalation shortcuts precisely because the official process doesn't reliably produce resolution.

When those agents are coached toward a standard the system won't let them reach, the message they receive - regardless of the language used - is that leadership either doesn't understand the real obstacle or has decided not to address it.

That discretionary effort doesn't disappear loudly. It withdraws quietly - one coaching session at a time, as agents absorb the message that the organisation sees them as the problem.

By the time that withdrawal is visible in the data, it has been building for months. And it is significantly harder to rebuild than the structural process problem that caused it.

What You Find When You Stop Coaching and Start Mapping

The shift that breaks the pattern of coaching that doesn't work in contact centres is a straightforward one - but it requires looking somewhere most leaders have never been asked to look.

The documented process describes how the work was designed to run. The real process is how agents actually navigate it on every contact. The gap between those two things is almost always larger than expected - and concentrated at exactly the points where performance is weakest.

When leaders map the real process from direct observation rather than documentation, they typically find:

• Steps that exist because they've always existed, with no current operational purpose

• Approval requirements introduced after a specific incident that have never been reviewed since

• Handoff points that remove agent authority at the exact moment resolution is possible

• Workarounds agents have developed and refined over months because the official route fails consistently

• Waiting points that generate hold time, callbacks, and repeat contacts entirely independently of agent behaviour

None of this is visible on the performance dashboard. But all of it is immediately recognisable to every agent in the team - because they navigate it every day.

When a leader maps the real process and shares it with the team, the response is almost always the same: relief. Not resistance. Relief that someone has finally looked at what they've been working around.

Authority Design: The Root Cause Coaching Cannot Reach

At the centre of most structural performance problems in contact centres sits a single issue: agents don't have the authority to resolve the contacts they're responsible for.

Authority design - the decisions about what agents can action, approve, and close without escalation - is rarely treated as a performance lever. It sits in policy, in risk frameworks, in system access controls. It was configured at some point in the past and has rarely been reviewed against the performance outcomes it produces.

But authority design is the most direct determinant of decision latency - the time between an agent identifying the correct resolution and being permitted to deliver it. When authority is too narrow, contacts wait, customers call back, FCR falls, and handle time rises.

Every one of those outcomes looks identical to a capability problem on a standard dashboard. None of them can be coached away.

Extending agent authority at the right process points - even modestly - typically produces faster outcome improvement than any coaching programme. Because it removes the constraint rather than coaching around it.

A Contained Intervention to Address the Real Cause

1. Recognition

Name the problem directly - to yourself first, then to your team. Coaching toward a structural constraint is not a failure of effort. It is a diagnostic error. And diagnostic errors require a different response, not more of the same.

2. Investigation

Select one contact type where performance has been the subject of repeated coaching cycles without improvement. Observe ten contacts of that type in real time. For each one, note every point where the agent waits, transfers, or cannot proceed without input outside their control. Map what you see - not what the process documentation says should happen.

3. Redesign

Share the observation map with the team before drawing any conclusions. Ask them to identify which constraints are familiar and which workarounds they've developed in response. Their input will surface the structural causes more accurately than any external analysis - because they've been living inside them.

4. Reinforcement

Redirect coaching investment away from outcomes that are structurally constrained. Replace performance conversations about metrics that can't move with process improvement conversations about the constraints preventing movement. That shift signals to the team that the diagnosis has changed.

5. Measurement

Track whether targeted authority extensions and process simplifications move the outcome metrics that coaching couldn't shift. Document the before and after states. That documentation becomes the evidence base for expanding the intervention - and for demonstrating to your own leadership that the structural cause was correctly identified.

The Bottom Line

Coaching doesn't work in contact centres when the system is the problem - not because of how it's delivered, but because of what it's targeting. The performance gap that hasn't moved after months of development investment is not evidence that the coaching needs to be more rigorous. It's evidence that the cause was never a coaching problem.

The agents in your team already know the difference. The map will show you too.

Not sure if this is your dominant problem? The Find Your Loop diagnostic will identify it.