Every service leader gets asked the same question:
“How do we reduce contact?”
It shows up in budget meetings.
It shows up in vendor pitches.
It shows up in executive dashboards dressed up as strategy.
And it sounds reasonable—until you examine what it actually assumes.
It assumes the contact itself is the problem.
It’s not.
Contact is evidence.
The Factory You Can’t See
Most organizations treat the contact center like a factory. Inputs come in. Agents process them. Outputs go out.
But that framing misses something critical:
The contact center doesn’t create demand. It receives it.
Every call, chat, or email started somewhere else.
- A confusing bill
- A broken product
- A missed expectation set by marketing
- A policy that made sense in a spreadsheet but not in real life
- A digital journey that collapsed at step four
The contact center is not the factory.
It’s the spillway.
And yet we manage it as if tightening the spillway will stop the water.
Why Deflection Feels Like Progress
Deflection is seductive because it produces immediate results.
Lower volume.
Shorter queues.
Cleaner dashboards.
You can stand in front of leadership and show improvement within a quarter.
But deflection doesn’t eliminate demand. It redistributes it.
- Customers try again later
- They switch channels
- They abandon and come back angrier
- Or worse—they leave and never tell you why
From inside the organization, it looks like success.
From outside, it feels like avoidance.
That gap is where trust erodes.
The Math Nobody Wants To Do
There is a version of this conversation that almost never happens:
What is the cost of not solving the underlying issue?
Not just operational cost—real cost.
- Repeat contacts
- Escalations
- Churn
- Brand damage
- Employee burnout
These costs are diffuse. They don’t sit neatly on a single line item. So they’re easier to ignore than the very visible cost of a contact.
So we optimize what we can see.
And we externalize what we can’t.
Customers pay with time.
Agents pay with stress.
Leaders pay with credibility.
Your Best Data Is Being Ignored
Every day, your operation collects a massive, unfiltered dataset of failure.
Not survey responses. Not curated feedback.
Raw friction.
Customers tell you exactly where things broke:
- “I was told something different when I signed up.”
- “Your website wouldn’t let me complete the process.”
- “I’ve called three times and no one can fix this.”
That is not noise. That is signal.
But most organizations don’t treat it that way.
Instead, they:
- Categorize it into high-level buckets
- Report on it monthly
- Nod in agreement
- And move on without changing the upstream system
The contact center becomes a reporting function instead of a forcing function.
The Incentive Trap
Service leaders don’t ignore root cause because they don’t care.
They ignore it because they are not rewarded for fixing it.
They are rewarded for:
- Hitting service levels
- Reducing cost per contact
- Improving efficiency metrics
None of those require eliminating the problem at its source.
In fact, solving root cause can make short-term metrics worse.
Volume might spike before it drops.
Handle time might increase while agents actually fix things.
So the system trains leaders to avoid the very work that would make service better.
Again—this is not failure.
It’s design.
What a Different Approach Looks Like
A small number of organizations treat contact differently.
They don’t start with “How do we reduce it?”
They start with “Why does it exist?”
They assign ownership of contact drivers outside the contact center.
They quantify repeat demand as a failure, not a cost of doing business.
They tie upstream teams to downstream consequences.
And most importantly:
They accept short-term discomfort to remove long-term friction.
This is slower. Harder. Politically messier.
It also works.
The Role of the Service Leader
This is where the job shifts.
You are not just running an operation.
You are managing the consequences of decisions made elsewhere.
Which means your leverage is not just inside the contact center. It’s in how you translate what you see into language the rest of the business cannot ignore.
Not anecdotes.
Not complaints.
Economic impact.
- “This billing issue is driving X repeat contacts per month.”
- “Those contacts cost Y dollars and create Z churn risk.”
- “Fixing the root cause removes the demand entirely.”
That is how you move from reporting pain to reallocating resources.
I break this down in more detail in HOLD, particularly for leaders stuck inside systems that reward containment over correction.
Because until the organization sees contact for what it is—evidence, not inconvenience—you will keep solving the wrong problem.
The Question That Changes Everything
Stop asking:
“How do we reduce contact?”
Start asking:
“Why does this contact exist at all?”
Everything downstream changes when you do.
Amas Tenumah is
