A conversation with an MSP owner once stopped me in my tracks.

They said something I've since heard dozens of times.

"My engineers are brilliant technically... I just wish they knew how to speak to customers."

At first, I thought they were talking about communication skills.

Looking back, I don't think they were.

I think they were talking about confidence.

Because when I asked them to explain what they meant, they didn't say they wanted their engineers to become more outgoing.

Or funnier.

Or better at small talk.

They wanted customers to feel reassured.

They wanted engineers who could calmly explain a complex issue.

Who could take ownership when things went wrong.

Who could handle a frustrated customer without sounding flustered themselves.

In other words...

They wanted customers to feel confident in the person they were speaking to.

That made me realise something.

Perhaps we spend too much time trying to teach communication...

...when what we're really trying to build is confidence.

Confidence changed the way I saw customer service

Early in my career, I noticed something that didn't make much sense to me.

Some of the engineers I worked alongside were technically better than I was.

They diagnosed faults faster.

They knew the products inside out.

They could solve incredibly complex problems.

Yet when it came to speaking with customers, many of them struggled.

Not because they didn't care.

Far from it.

They cared deeply.

But difficult conversations seemed to knock their confidence.

A frustrated customer.

A challenging question.

Someone asking for an update they didn't yet have.

You could almost see the uncertainty creeping into the conversation.

The interesting thing was...

I never believed they needed to become different people.

They didn't need bigger personalities.

They didn't need to become salespeople.

They simply needed confidence in how to guide the conversation.

That curiosity stayed with me for years.

So I started paying attention

At the time, I wasn't consciously doing anything different.

Talking to customers just felt... natural.

But because I wanted to help my colleagues, I started asking myself a simple question.

"What am I actually doing differently?"

So I paid attention.

Not just to what I said.

But to the order I said it in.

I noticed I naturally followed a similar structure in almost every conversation.

I acknowledged the customer's situation before jumping into technical details.

I explained what I was doing as I worked.

I checked their understanding instead of assuming it.

And before ending the call, I'd almost always ask:

"Is there anything else I can help you with today?"

None of it felt revolutionary.

But together, those small habits created something much bigger.

They helped customers feel looked after.

That's when I realised good customer communication wasn't random.

It had a structure.

And if it had a structure...

It could be taught.

Great customer conversations aren't improvised. They're built on confidence and structure.

Confidence isn't a personality trait

One of the biggest misconceptions I still hear today is that people are either naturally good with customers or they aren't.

I've never believed that.

If that were true, I wouldn't have seen so many engineers grow into exceptional communicators over the course of my career.

I wouldn't have seen people who dreaded difficult conversations become the colleagues others turned to for advice.

And I certainly wouldn't have watched engineers who'd been labelled "poor communicators" develop into trusted members of support escalation teams.

None of those transformations happened because their personalities changed.

They happened because their confidence changed.

And confidence grows when people know what good looks like.

When they have a repeatable framework to follow.

When they understand not just what to say, but why they're saying it.

That's when conversations stop feeling unpredictable.

And that's when confidence starts replacing uncertainty.

Customer Service or Confidence?

For a long time, I thought I was teaching customer service.

Looking back, I don't think I was.

I think I was helping engineers build confidence.

And once that confidence grew, something else grew with it.

The confidence of the customers they were supporting.

The problem usually isn't knowledge

Over the years, I've coached engineers with all kinds of technical abilities.

Some were new to the industry.

Others had decades of experience.

What surprised me was that their biggest challenge was rarely technical knowledge.

More often, it was confidence.

They already knew how to solve the problem.

They just didn't always know how to guide the customer through it.

There's a big difference.

Think about the last time one of your engineers dealt with a frustrated customer.

Was the conversation difficult because they didn't understand the technology?

Or was it difficult because they felt under pressure?

Perhaps they were worried about saying the wrong thing.

Perhaps they didn't know how to explain a complicated issue in simple terms.

Perhaps they weren't sure how to respond when a customer challenged them.

Those situations aren't usually technical problems.

They're confidence problems.

And once I started looking at them through that lens, the way I coached people changed completely.

The engineer everyone had given up on

One of the moments I'm most proud of in my career wasn't winning an award.

It was working with an engineer who'd developed a reputation for being "uncoachable."

They'd become known as someone who struggled with customer conversations.

Eventually, a formal complaint was raised about the way they'd spoken to a customer.

By the time they came to me, it felt like a last resort.

Not because they lacked ability.

But because people had started believing they couldn't improve.

I didn't see it that way.

I saw someone who'd never been shown a repeatable way of handling difficult conversations.

So we slowed everything down.

We didn't try to change who they were.

We didn't ask them to become more extroverted or change their natural communication style.

Instead, we focused on the structure behind the conversation.

How to open it.

How to acknowledge the customer's frustration.

How to explain technical information clearly.

How to take ownership.

How to close the conversation in a way that left the customer feeling reassured.

We practised.

Refined.

Repeated.

Little by little, their confidence started growing.

A few months later, something happened that nobody expected.

They joined the same Support Escalations team I'd previously worked in.

The very team responsible for handling the business's most challenging customer complaints.

I still smile when I think about that.

Not because it proved I was a good coach.

But because it proved something I'd suspected for a long time.

People aren't born confident communicators.

Confidence can be built.

I've only ever met one or two engineers who wanted to give poor customer service. But I've met plenty who simply lacked the confidence to deliver the service they were capable of.

Confidence changes everything

When an engineer becomes more confident, something interesting happens.

They stop focusing so much on themselves.

Instead of thinking:

"What if I say the wrong thing?"

They start thinking:

"What does this customer need from me right now?"

That shift is powerful.

Because confidence creates clarity.

Conversations become calmer.

Explanations become simpler.

Customers feel reassured.

And when customers feel reassured, they naturally become more confident in the business they're dealing with.

That's why I've never believed confidence is just an individual skill.

I think it's contagious.

It spreads from engineer to customer.

From customer to relationship.

And from relationship to the reputation of the entire business.

This is why frameworks matter

People sometimes hear the word "framework" and imagine something rigid.

Something scripted.

That's not what I mean.

A framework isn't there to make conversations robotic.

It's there to give people confidence when conversations become unpredictable.

Think about learning to drive.

At first, every decision feels conscious.

Mirrors.

Indicators.

Gears.

Speed.

You're thinking about everything.

Eventually, those actions become second nature.

The same thing happens with customer communication.

Once engineers have a simple structure they can rely on, they stop worrying about what to say next.

They become more present.

They listen more carefully.

They respond more confidently.

Ironically, the more structure they have behind the scenes, the more natural the conversation feels.

And that's where real trust begins to grow.

So what?

If confidence is something that can be developed rather than something people are simply born with, it raises an important question.

What does a support team look like when confidence becomes part of its culture?

Culture

If there's one thing I've learned over the years, it's this:

Great customer experiences don't happen by accident.

They're the product of confident people working within a supportive culture.

That's why I don't think trust starts with the customer.

I think it starts inside your business.

Every engineer influences your reputation

It's easy to think your brand is defined by your logo.

Your website.

Your marketing.

Your social media.

Those things all have a role to play.

But in reality, your reputation is shaped somewhere else.

It's built one conversation at a time.

Every engineer who answers the phone.

Every email that's sent.

Every update that's given.

Every difficult conversation that's handled professionally.

Those moments quietly shape how customers feel about your business.

Long before they speak to an Account Manager.

Long before a Quarterly Business Review.

Long before a renewal meeting.

By then, your customers have already decided what it's like to work with you.

Trust isn't built through perfection

If we've ever spoken before, you'll probably have heard me say this:

One of the biggest misconceptions in customer service is that trust comes from never making mistakes.

If that were true, no MSP would have loyal customers.

Technology is unpredictable.

Problems happen.

Projects slip.

Unexpected issues arise.

Customers understand that.

What they remember is how you responded.

Did someone take ownership?

Did they feel informed?

Did they feel listened to?

Did they finish the conversation feeling more confident than when they started it?

Those are the moments that build trust.

Not because everything went perfectly.

But because someone made them feel they were in safe hands.

Customers don't expect perfection. They remember the experience.

The support teams people remember

When I look back over my career, the best support teams I've worked with all had something in common.

It wasn't that they knew more than everyone else.

It wasn't that they closed tickets faster.

And it certainly wasn't that they never made mistakes.

It was the way they approached customers.

There was a quiet confidence about them.

They listened before they spoke.

They explained things clearly.

They took ownership.

They followed through on what they promised.

When a customer finished speaking to them, they felt reassured.

That's what people remember.

Not the ticket number.

Not the troubleshooting steps.

The feeling they were left with.

Building confidence starts with one decision

One of the things I've learnt over the years is how quickly confidence can grow when engineers are given practical conversation frameworks they can start using immediately.

Sometimes, all it takes is for an engineer to say:

"I never thought I'd understand this, but now I do."

Or:

"I know exactly what I'll do differently on my next call."

Those moments create momentum.

But like any new skill, confidence grows through use.

That's why the businesses that see the biggest long-term improvements are the ones that continue reinforcing those conversations after receiving external support.

I provide the frameworks.

Managers and team leaders reinforce them.

Engineers practise them.

The frameworks provide the foundation.

The business builds on it.

And that's how confident behaviours become part of the culture, rather than something that's remembered for a few weeks before everyone slips back into old habits.

My final thought

I hope there's one idea you'll take away from this.

I no longer believe the strongest support teams are simply the most technically capable.

I believe they're the ones that consistently build confidence.

Confidence in themselves.

Confidence in each other.

And confidence in the customers they support.

Because when support engineers communicate with confidence, customers feel reassured.

When customers feel reassured, trust grows.

When trust grows, complaints reduce.

Relationships become stronger.

Owners spend less time firefighting.

And customers are far more likely to stay.

For me, that's what great customer service has always been about.

Not teaching engineers to become someone they're not.

Rather, helping them become the most confident version of who they already are.

Because confident engineers don't just solve technical problems.

They create customer experiences people remember.

And in an industry where technology is becoming increasingly similar, those experiences may be the most valuable competitive advantage an MSP can build.