One of the saddest conversations I used to have wasn't with angry customers.
It was with the ones who'd already made up their mind to leave.
By the time those conversations reached me, the technical issue had often been going on for weeks.
Multiple engineers had been involved.
Hours of troubleshooting had been carried out.
Countless emails had been exchanged.
From the outside, it looked like the customer was leaving because of a technical problem.
But after having those conversations time and time again, I started noticing something.
Almost nobody began by talking about the technology.
Instead, they'd say things like:
"I just didn't feel anyone was taking ownership."
"Nobody kept me updated."
"I didn't feel listened to or understood"
"I lost confidence that anyone was in control."
That's when something clicked for me.
The technical issue wasn't usually what ended the relationship.
It was the experience of living through it.
And once I started seeing that pattern, I couldn't unsee it.
I don't believe customers expect everything to work perfectly all the time.
Technology is complex.
Systems fail.
Projects overrun.
Unexpected problems happen.
Most customers understand that.
What they struggle to accept is feeling uncertain while those problems are being resolved.
They want confidence.
Confidence that someone understands the issue.
Confidence that someone is taking ownership.
Confidence that they're being kept informed.
Confidence that they're in safe hands.
When that confidence begins to disappear, customer loyalty often starts disappearing with it.
When a customer leaves, it's natural to ask questions like:
Was the technical issue too severe?
Did we miss an SLA?
Did another provider offer something cheaper?
Did we fail to resolve the problem quickly enough?
They're all reasonable questions.
But after spending more than a decade working across technical support, customer escalations, technical training, leadership and consultancy, I've come to believe they aren't the first questions we should be asking.
I'd start somewhere else.
What was it actually like to be our customer while we were solving the problem?
Because that's the part many businesses never stop to examine.
One of the biggest turning points in my career came when I joined a support escalations team.
By that point, I wasn't dealing with routine support tickets.
I was speaking almost exclusively with customers who had lost confidence in the business.
Some had raised formal complaints.
Others were already discussing leaving altogether.
Initially, I assumed the customers with the most complex technical issues would be the ones most likely to leave.
But that wasn't what I found.
Customers experiencing similar technical problems often made completely different decisions.
Some stayed.
Some left.
The difference wasn't always the severity of the issue.
It was how they experienced the journey.
That changed the way I thought about customer retention forever.
Most businesses treat customer renewals as a meeting.
A proposal.
A commercial discussion.
I see it differently.
I believe every support conversation is a renewal conversation.
Every phone call.
Every email.
Every ticket update.
Every difficult conversation.
Each interaction either strengthens the customer's confidence in your business or quietly weakens it.
Customers don't decide whether to renew a week before their contract expires.
That decision is shaped throughout the entire relationship.
One conversation at a time.
Customers rarely leave because of one bad day. They leave after losing confidence over many ordinary ones.
As I reflected on those years handling complaints and customer escalations, I realised something that completely changed how I think about customer retention.
The biggest cost of poor customer experience isn't the complaint itself.
It's the slow erosion of customer confidence that happens long before a cancellation ever arrives.
And that's where I'd like to go next.
When people talk about customer churn, they usually focus on the end result.
A cancelled contract.
Lost recurring revenue.
Another client moving to a competitor.
Those things are expensive.
But I think they distract us from the real issue.
Long before a customer leaves your business, they leave emotionally.
Not completely.
Not overnight.
But gradually.
They stop giving you the benefit of the doubt.
They become quicker to question decisions.
They lose patience when things take longer than expected.
They stop recommending you to other businesses.
Eventually, they start wondering whether there's a better alternative.
The contract usually ends much later.
The relationship started ending much earlier.
When I worked in support escalations, I was often asked to speak with customers who were considering leaving the business.
Some had been labelled internally as "unsaveable."
The assumption was usually that the technical fault had pushed them too far.
But I found something interesting.
If I started the conversation by talking about the fault, I rarely made much progress.
Instead, I wanted to understand something much more important.
How had the experience made them feel?
Had they felt listened to?
Did they feel anyone had taken ownership?
Did they feel they were having to fight for updates?
Did they believe anyone genuinely understood the impact the issue was having on their business?
Only once I'd rebuilt that confidence did the technical conversation become productive.
And time after time, customers who were expected to leave chose to stay.
Not because I magically fixed problems nobody else could.
But because I changed the conversation.
I became known internally for being able to handle some of the most difficult customer conversations, and eventually earned the nickname "Complaints King."
Hopefully not because I was the king of causing complaints!
But the nickname stuck, and the experience shaped the way I think about customer retention today.
Technology solves the issue. Communication protects the relationship.
It's easy to think of the support desk as a function that resolves tickets.
Of course it does.
But that's only part of the story.
Your support desk is also shaping:
Your reputation.
Your customer retention.
Your referrals.
Your online reviews.
Your team's confidence.
Your owner's time.
Every interaction leaves an impression.
Sometimes that impression lasts much longer than the technical issue itself.
Think about your own experiences as a customer.
Have you ever stayed loyal to a company even after they made a mistake?
Chances are, it wasn't because the mistake didn't matter.
It was because they handled it well.
Now think about the opposite.
Have you ever left a company, not because the product was poor, but because the experience left you feeling frustrated or ignored?
Most of us have.
Your customers are no different.
One pattern I've seen repeatedly throughout my career is this.
An engineer handles the ticket.
The customer isn't reassured.
The team leader becomes involved.
The customer still isn't confident.
Eventually, the owner steps in.
For many MSPs, that becomes normal.
Owners begin accepting that they'll always need to rescue important customer relationships.
But should they?
I don't think so.
Every time an owner is pulled into a complaint that the support team could have resolved independently, the business pays twice.
First, in the owner's time.
Second, in the message it sends to the team.
It quietly reinforces the idea that difficult customer conversations always need escalating.
Over time, engineers become less confident handling them.
Owners become busier.
Customers become conditioned to asking for management.
The cycle repeats.
Engineer lacks confidence
↓
Customer loses confidence
↓
Complaint escalates
↓
Owner steps in
↓
Engineer never develops confidence
↓
The next complaint follows the same path
The opposite is also true.
When engineers have a repeatable structure for difficult conversations, they begin handling more situations independently.
Customers gain confidence in the person they're speaking to.
Complaints reduce.
Owners step back.
The team grows.
Confidence builds.
That's how healthy support cultures are created.
One of the biggest shifts I'd encourage MSP owners to make is to stop thinking about customer experience as a "soft skill."
There's nothing soft about protecting recurring revenue.
There's nothing soft about reducing customer churn.
There's nothing soft about increasing referrals.
And there's certainly nothing soft about giving business owners back the time they're currently spending firefighting customer complaints.
That's why I believe customer experience deserves a seat at the leadership table.
Not because it's a nice thing to do.
Because it's one of the smartest commercial investments an MSP can make.
When support engineers communicate with confidence, customers stay calmer.
When customers stay calmer, complaints reduce.
When complaints reduce, owners spend less time firefighting.
When owners spend less time firefighting, they can focus on growing the business instead.
That's not just better customer service.
That's better business.
Throughout my career, I've often heard people describe customer communication as a "soft skill."
I've never really agreed with that.
To me, there's nothing soft about protecting customer relationships.
There's nothing soft about reducing churn.
There's nothing soft about earning referrals.
And there's certainly nothing soft about giving business owners back the time they're currently spending firefighting complaints.
Customer experience isn't simply about being polite.
It's about building confidence.
Confidence in your engineers.
Confidence in your business.
And ultimately, confidence in your customers that they've chosen the right MSP.
The MSP market has never been more competitive.
Most providers have access to the same technologies.
The same vendors.
The same cybersecurity solutions.
The same cloud platforms.
The same monitoring tools.
Technology is no longer the differentiator it once was.
That's not a bad thing.
It simply means the opportunity to stand out has changed.
The businesses that build long-term loyalty won't necessarily be the ones with the longest list of technical certifications.
They'll be the ones whose customers consistently feel listened to, reassured and looked after.
In other words...
The businesses that create confidence.
One of the biggest misconceptions I've encountered over the years is that some engineers are simply "good with customers" and others aren't.
I don't believe that's true.
I've seen engineers who dreaded difficult customer conversations become some of the calmest and most capable people in the room.
Not because their personalities changed.
Because their confidence did.
One engineer I coached had developed a reputation for struggling with customer conversations.
They'd even had a formal complaint raised about the way they'd spoken to a customer.
By the time we finished working together, they had progressed into the same Support Escalations team I used to work in - handling some of the business's most challenging customer conversations.
That transformation didn't happen because they suddenly became a different person.
It happened because they had a repeatable structure they could rely on.
Once they knew what to say, why they were saying it and how to guide difficult conversations, their confidence grew.
And as their confidence grew, so did the confidence of the customers they were supporting.
That's why I don't believe great customer experience is about finding people with the "right personality."
It's about giving good people the right tools.
Confident engineers create confident customers.
It's easy to think your reputation is built through marketing.
Your website.
Your branding.
Your social media.
Those things all matter.
But I believe your reputation is built somewhere else.
It's built in thousands of everyday conversations.
The engineer who explains a technical issue without making a customer feel foolish.
The update that arrives before the customer has to ask for it.
The difficult conversation that's handled calmly and professionally.
The phone call that ends with, "Is there anything else I can help you with today?"
On their own, they might seem like small moments.
Together, they become the experience your customers remember.
And that's what shapes whether they renew, recommend you or begin looking elsewhere.
If there's one idea I'd like you to take away from this article, it's this.
Technology gets you through the door.
Customer experience keeps you there.
As technology becomes increasingly accessible and standardised across the MSP industry, the experience you create for your customers becomes even more valuable.
Not because customers care less about technical excellence.
They absolutely do.
But because technical excellence is increasingly expected.
The experience you create is what customers remember.
The experience you create is what builds trust.
And trust is what protects long-term customer relationships.
That's why I believe customer experience isn't just another initiative for your support desk.
It's one of the most important commercial investments your business can make.
Because customers rarely leave because of one technical issue.
They leave when they no longer feel confident that they're in the right hands.
Build that confidence consistently, and you'll build something far more valuable than satisfied customers.
You'll build loyal ones.
I have spent more than a decade working across software development, technical support, support escalations, technical training, leadership and consultancy within the IT, technology and telecoms industries. Today, I help MSP owners build support teams that confidently handle customer conversations, reduce complaint escalations and create customer experiences that protect valuable client relationships.
If you'd like to discuss how your support team could build greater confidence in customer conversations, get in touch for an informal chat.