88% resolved. 22% stayed loyal. What went wrong?
That's the AI paradox hiding in your CX stack. Tickets close. Customers leave. And most teams don't see it coming because they're measuring the wrong things.
Efficiency metrics look great on paper. Handle time down. Containment rate up. But customer loyalty? That's a different story — and it's one your current dashboards probably aren't telling you.
Gladly's 2026 Customer Expectations Report surveyed thousands of real consumers to find out exactly where AI-powered service breaks trust, and what separates the platforms that drive retention from the ones that quietly erode it.
If you're architecting the CX stack, this is the data you need to build it right. Not just fast. Not just cheap. Built to last.

Hi, Markus here. Welcome to a new episode of the Customer-Value-Led-Growth Newsletter.
I share strategies and guides to help you become a proactive CSM, deliver more value for your customers, and turn it into revenue for your company every week.
Need additional help? COMING NEXT WEEK 👇
The CSM Operating System Notion Workspace
The Cost of Avoidance
You’ve been in this situation (many times). You are on call, and the tension is rising. There’s something uncomfortable that needs to be said.
A promise can’t be upheld
Customer Expectations have drifted away
The customer is making a decision they will regret
The relationship is heading toward a cliff
But instead of saying it like it is, you remain silent. You make a note to bring it up next time. You tell yourself the moment is not right, that the relationship is too important to risk, that you will find a better way to say it when you have had more time to think.
That next time never comes. The moment passes. And that little issue that could be handled quietly blows up in your face and breaks the relationship. Not because it was too difficult to say, but because it was left unsaid for too long.
Successfully navigating difficult customer conversations is a heavily underrated skill in CSM. More so during times when customer expectations have gone through the roof.
The ability to say what needs to be said, when and how, is what separates the CSMs who consistently retain and grow their accounts from those who are always surprised when something goes wrong.
In this episode, you’ll learn what makes conversations difficult, why avoiding them makes things worse, and how to have them in a way that strengthens rather than damages the relationship.
Why CSMs Avoid Difficult Conversations
Before diving into the conversations themselves, it's necessary to understand why we avoid them in the first place. Because the reasons are not personal but rather structural, and recognising them is the first step to breaking through.

1. Confusing harmony with health
A call where everyone is in a good mood, no difficult topics come up, and customers say thank you, feels successful. It produces none of the discomfort that comes from naming a problem or delivering unwelcome news.
Over time, you develop a bias toward conversations that feel good in the moment. Leaving underlying issues unaddressed and the account quietly deteriorating. The most dangerous accounts are often the ones with the most pleasant check-in calls.
Harmony is not health. A relationship where nothing difficult is ever said is not a strong relationship. It is a fragile one that has never been tested, and one that will not survive the first serious challenge.
2. Fear of damaging the relationship
This is the most common reason why CSMs avoid difficult conversations. It's based on a fundamental misunderstanding of how trust works. Trust is not built on comfort. It's built on honesty.
The relationships with the longest lifespan are the ones where both sides can handle difficulty together. Where they have been through challenges without declines in respect for each other.
Avoiding a difficult conversation does not protect the relationship. It protects your comfort at the expense of the relationship. And at some point, customers begin to notice, and that knowledge quietly erodes the trust.
3. Ambiguity about how to say it
Sometimes the avoidance is not about fear. It's because CSMs know the conversation needs to happen, but don't know how to start it, frame it, or handle the reaction. They lack a framework.
Without preparation, the difficult conversation feels like diving headfirst into the unknown. So you wait until you have clarity. But the answer is not to wait for it. It's to get it through developing frameworks.
4. The emotional weight
One of the most overlooked sources of avoidance is the emotional capacity. If you are managing a larger book of business, you are carrying the weight of dozens of relationships simultaneously.
Accounts at risk, frustrated champions, desired features not being implemented – you name it. Over time, this weight accumulates, and adding another difficult conversation feels like one too much.
This is a real cost, and it deserves to be acknowledged. But the answer is not avoidance; it is developing the skills and the emotional resilience to handle frequent difficult conversations. And the most effective way is to have them more often, not less.
The 6 Conversations CSMs Avoid
What adds complexity to handling difficult conversations is that they are not restricted to a single type. There are 6 different scenarios you need to handle:

1. Behind on results
This is the conversation that needs to happen when customer progress is behind expectations. Or when things are entirely moving in the wrong direction.
CSMs avoid it because it feels like admitting failure. But the failure is not permanent. The trajectory of the project can be corrected. The failure is when you are not calling it out early enough to act in time.
Example Opener: "I want to talk with you about where we are right now. Based on the goals we set in the beginning and where we are today, we have not made the progress we expected. That's likely not what you want to hear, but I'd rather bring it up so we can fix it before we're further behind. Can we spend some time on this today?"
This is direct without being alarming. It frames the conversation as collaborative rather than accusatory. It signals that you are paying attention and care about the outcome.
What you need to avoid is the temptation to soften the message. Like "Things are going pretty well overall, and there are a few areas we could maybe look at improving". Because it masks the significance of taking immediate action.
2. Wrong product usage
This is the conversation that needs to happen when a customer is blaming the product for the lack of results that's actually caused by their own doing. Like using the wrong workflows, not adopting critical features, or skipping training sessions.
CSMs avoid it because it feels like criticising the customer. But if you are saying nothing, the customer continues to get poor results, continues to blame the product, and eventually churns.
Example Opener: "I've been looking at how your team is using the product, and noticed some things. The results you are seeing right now are a common pattern when the X workflow has not been set up properly. Can I show you what I mean?"
This frames the conversation around patterns rather than personal failing. It is diagnostic rather than accusatory. It offers an immediate path forward rather than just naming the problem.
What you need to avoid is being vague, where the customer leaves the conversation without understanding that their usage is the issue. Saying things like "You might want to explore feature Y more" will not change behavior. Specific, honest observations will
3. Unrealistic expectations
This is the conversation that needs to happen when the product can't deliver what customers want. Or at least not within the timeline they have in mind. They are often set during the sales process (deliberately or by accident).
CSMs avoid it because it feels like sabotaging the sale. They hope that customers will naturally settle for less, which they rarely do. If unrealistic expectations are not addressed directly, they are (even more) difficult to reverse.
Example Opener: "I want to make sure we're aligned on what's a realistic outcome here. Because I think there might be a gap between what you are expecting and what we can deliver in the timeframe you have in mind. I'd rather have that conversation now than have you feel let down later. Can we look at this together?"
This frames the conversation as starting on the desire to start on the right foot. It creates the opportunity to build the relationship on a foundation of honest expectations. It demonstrates that you really care about their success.
What you need to avoid is softening the misalignment. Not even if the conversation is heading toward an early customer exit. This is the natural downside, as customers might feel they were lured into the purchase with false promises on purpose
4. Delivering bad news
This is the conversation that needs to happen when something has gone wrong. A promised feature has been delayed, an integration is no longer working, or a commitment by your company can't be upheld.
CSMs avoid it by delaying, minimising, or hoping the customer will not notice. But they always do. And postponing it over and over makes it worse. In terms of the impact on the work and the damage to trust.
Example Opener: "I have some news I want to give you directly, because I think you deserve to hear it from me rather than discover it on your own. Unfortunately, [name the problem]. I know this is not what you were expecting, and I want to talk about what that means for you and what we are doing about it."
This frames the conversation around taking ownership without being defensive. It shifts immediately from lingering on the problem to what happens next.
What you need to avoid is the passive voice, the non-apology in corporate speech, and the temptation to bury the news within some other context. You can recover from clearly and quickly delivered bad news. You can't recover from delivering bad news delivered evasively and slowly.
5. Pushing back on the customer
This is the conversation that needs to happen when the customer is wrong. Wrong about product capabilities, responsibilities, or strategies. It also includes inappropriate behavior of all sorts that needs to be called out.
CSMs avoid it because pushing back feels like jeopardizing the relationship. In reality, never pushing back is what actually puts the relationship at risk. Because it creates a dynamic where the customer has no reason to respect your perspective or take your advice seriously.
Example Opener: "I want to talk with you about something because I think it's diminishing your results. From working with X companies in your field, I noticed that doing Y is negatively affecting Z. Are you open to hearing what creates better results?"
This signals that you have a point of view and you are willing to defend it. That's exactly what a trusted advisor does. Putting customer results first, even when it means hurting some egos. Customers do not need a CSM who agrees with everything they say. They need one who tells them the truth.
What you need to avoid is framing the pushback as a personal disagreement rather than a professional observation. You are not pushing back because you want to win an argument. You are pushing back because you genuinely believe the current situation is not serving your customers' best interests.
6. Pre-Emptive churn conversation
This is the conversation that needs to happen when you notice an account is heading toward churn. It needs to happen before the customer says anything, before the renewal becomes imminent, and (obviously) before the decision has been made.
CSMs wait for customers to talk about it, but by the time they do, it's too late. Proactively initiating the conversation is one of the most powerful retention moves available. Naming the risk, acknowledging the gap, and genuinely discussing whether the collaboration is working.
Example Opener: "I want to have an honest conversation with you about how things are going, because I'm not sure we're delivering what you need. I'd rather talk about it now than wait until it becomes a bigger issue.”
This demonstrates that you are paying attention. That you care more about their success than protecting your revenue and that you are willing to have a hard conversation about it.
What you need to avoid is the conversation drifting into a renewal discussion. Its purpose is to evaluate whether there's a viable solution or it's better to go separate ways. And you are absolutely prohibited from bringing up potential discounts.
The Framework For Difficult Conversations
There are 6 different conversations, but there's a common framework that applies to all of them. It consists of 4 parts:

1. Name it directly
The most important thing you can do at the start of a difficult conversation is to say clearly what it is about. Do not
beat around the bush
spend 5 minutes on pleasantries
mention it at the end of the agenda
Customers respect directness - even more because that's not what they get from most CSMs. And the longer you procrastinate, the amount of discomfort piles up.
2. Separate observation from judgment
A difficult conversation often goes south because the observation becomes entangled with the judgment. State what you have observed through facts before you provide an interpretation of what it means.
✅ Observation: "You have not participated in the training program."
❌ Interpretation: "You are not taking this seriously."
This is not just a communication technique. It keeps the conversation on what is known rather than jumping to (possibly wrong) conclusions. The right context (explanation) comes from the customer.
3. Let customers respond
After you have stated the issue, you stop talking. Give the customer enough space to respond. Even if it results in awkward silence for a moment. The silence is doing important work.
It gives the customer the chance to process what they have heard. The most important information in a difficult conversation often comes in the first "unscripted" response to a direct statement. Do not talk over it.
4. Move to what happens next
A difficult conversation has only done half of its job when the problem is clearly stated, but there's no path forward. Every difficult conversation should end with a specific next step that both sides have agreed upon.
Not vague intentions like "let's continue our talks in 3 weeks" but with a defined action, a timeline, and an owner.
After The Conversation
Having the conversation is only half the work. What happens after determines whether it was worth having.
1. Follow up
After any difficult conversation, send a summary of what was discussed, what was agreed upon, and what the next steps are. It creates accountability for both parties, and it demonstrates that you took the conversation seriously enough to document it.
2. Keep your word
Nothing invalidates a difficult conversation faster than failing to follow up on the conversation. If you told them you would come back with a revised plan, come back with it on time.
3. Reflect on what you learned
Every difficult conversation is a source of information about the account, the relationship, and your own skills as a CSM. Take 5 minutes to reflect on what you noticed, what worked, and what you would have done differently.
Final Thoughts
There is a version of Customer Success Management that is comfortable and pleasant, but ultimately ineffective. It is the version where nothing difficult is ever said, and issues accumulate quietly until they blow up in your face.
And there is a version of Customer Success that is sometimes uncomfortable, occasionally tense, but consistently effective. It is the version in which CSMs say what needs to be said with the directness and care of a true trusted advisor.
The gap between these two versions is not talent, experience, or job title. It's courage. It is courage. The willingness to prioritize your customer's long-term success over your own short-term comfort.
The willingness to be the person in the room who says what everyone shys away from saying. The willingness to trust that honesty, delivered with genuine care, almost always strengthens a relationship rather than damaging it.
That courage is available to every CSM. It just needs to be chosen.


