Content
I’ve always said that if you still believe the customer is always right, you have no business being in Customer Success.
CS leaders who’ve been in the field long enough know that customers are sometimes wrong. They misremember what was promised. They underinvest in adoption and blame the product. They escalate on things that were clearly documented in the contract. Part of the job is knowing how to hold your ground in those moments without damaging the relationship.
But sometimes the customer is right. Genuinely, unambiguously right. And they have every reason to be unhappy.
These situations happen. They happen at good companies with good CS teams. And when they do, CS has to sit across from someone with legitimate grievances and figure out how to hold the relationship together without losing credibility in the process.
That’s a different conversation than the one most CS training prepares you for. And it has its own playbook.
First, understand how the customer got here
Before CS does anything else it needs to understand exactly what happened.
There are three common ways a customer ends up legitimately unhappy and each one has a different starting point for the conversation.
The overpromise. Something was sold that the product couldn’t deliver. A timeline that was never realistic. A feature that was on the roadmap but not in the product. A use case that Sales stretched to close the deal. The customer built their decision around a promise CS is now holding the bag for.
The product failure. Something broke that shouldn’t have. An outage. A data issue. A bug that affected the customer’s business in a way they can quantify. The customer paid the price for a failure that was entirely on the vendor side.
The neglected account. The account was deprioritized. The CSM got stretched. Check-ins got less frequent. Nobody noticed the customer was struggling until the health score dropped or the customer reached out frustrated. The customer didn’t get what they were paying for and they knew it before CS did.
Each scenario is real. Each one is legitimately the company’s fault. And walking into the conversation without knowing which one you’re dealing with and why it happened is one of the most common mistakes CS leaders make.
Do the diagnosis before you pick up the phone. Pull the account history. Talk to the CSM. Talk to Sales if the overpromise happened in the sales cycle. Understand exactly what went wrong, when, and why. Walk in with the full picture. Not discovering the problem in real time with the customer watching.
Acknowledge without over-apologizing
Here’s where most CS leaders get it wrong.
The instinct when a customer is legitimately unhappy is to apologize your way through it. More sorry. More empathy. More assurances that it won’t happen again. The thinking is that enough remorse will soften the customer enough to save the relationship.
It doesn’t work. And here’s why.
Over-apologizing without a plan signals weakness, not accountability. It tells the customer that CS is uncomfortable with what happened and is trying to make that discomfort go away rather than addressing the actual problem. Customers who are right to be unhappy don’t need more apologies. They need to see that the person across from them understands what went wrong and has a real plan to address it.
There’s a difference between these two versions of the same conversation.
Version one: “I’m so sorry this happened. I completely understand your frustration. We really dropped the ball and I sincerely apologize for the impact this has had on your team. We’re going to do everything we can to make this right.”
Version two: “I want to be direct with you about what happened. Here’s what went wrong. Here’s what we own. And here’s specifically what we’re doing about it.”
The first version is about managing CS’s discomfort. The second is about addressing the customer’s problem. Customers can tell the difference immediately.
Own the failure clearly and specifically. Name what went wrong without hedging or minimizing. Take accountability without collapsing into excessive apology that makes promises CS can’t keep. And move quickly to what happens next, because that’s what the customer actually needs to hear.
One more thing. Don’t say “it won’t happen again” unless you can explain exactly why it won’t happen again. That phrase without a structural reason behind it is a promise CS can’t keep. Customers who have heard it before know that. It erodes trust rather than building it.
Rebuild trust deliberately
Trust after a legitimate failure doesn’t come from words. It comes from a specific, time-bound plan that the customer can hold CS accountable to.
Most CS leaders handle the recovery by committing to being more attentive, more available, more responsive. Those are intention statements. They don’t rebuild trust. Actions on a timeline rebuild trust.
Here’s what a real recovery plan looks like.
It names the specific failure and what’s being done to address it structurally. Not “we’re going to do better” but “here’s the process change we’ve made so this specific thing doesn’t happen again.”
It has milestones. Not “we’ll check in more frequently” but “here’s what we’re committing to in the next 30, 60, and 90 days and here’s how you’ll know whether we’re delivering.”
It gives the customer a way to hold CS accountable. A shared document. A standing check-in specifically to review progress against the recovery plan. Something the customer can point to if things slip again.
And it’s honest about what CS can and can’t control. If the failure was a product issue and the fix is on the roadmap, CS can commit to keeping the customer informed about progress. It can’t commit to a delivery date it doesn’t control. Being honest about that boundary while still showing up consistently is more trust-building than an optimistic promise that gets broken.
Present the recovery plan in the conversation, not after it. Customers who leave a difficult conversation with a concrete plan in hand feel differently than customers who leave with a verbal commitment to do better. The plan is the signal that CS is serious about the recovery, not just the conversation.
Decide whether the relationship is worth saving
This is the question most CS leaders don’t ask out loud. And it’s one of the most important ones.
Not every customer who is right to be unhappy is a customer worth fighting to keep. That’s an uncomfortable thing to say. But treating every at-risk customer as a save-at-all-costs situation isn’t strategic. It’s exhausting. And it sometimes means investing significant time and goodwill into a relationship that was never going to work regardless of the recovery effort.
Here’s how to make that assessment honestly.
Is the customer a good fit for the product as it exists today? If the original sale was a stretch and the product has never delivered on what was promised and isn’t going to, saving the renewal is delaying the inevitable churn by one cycle. That’s not a save. That’s a deferral.
Is the failure recoverable within a timeline the customer can accept? Some product gaps get fixed. Some don’t. Some customers can wait. Some can’t. If the fix isn’t coming in a timeframe that works for the customer’s business, the most honest thing CS can do is acknowledge that rather than managing expectations until the renewal conversation falls apart.
What does the customer’s future look like with the product? If they’re a good fit, the gap is fixable, and the relationship has enough trust left to work with, fight for it. If none of those things are true, the most integrity-driven move is to be honest with the customer about where things stand and let them make an informed decision.
When the relationship isn’t worth saving, handle it with the same care and honesty as when it is. The way a company handles a customer who chooses to leave after a legitimate failure says as much about the organization as how it handles the recovery when the customer stays. Customers who leave with dignity become references. Customers who leave feeling managed become detractors.
The internal conversation CS can’t skip
What happens inside the org after a legitimate customer failure matters as much as what happens with the customer.
Most CS leaders manage the customer conversation and then move on. They absorb the failure internally, patch the relationship, and hope it doesn’t happen again. That’s the most common response. It’s also how the same failures keep happening.
After every legitimate customer failure CS needs to answer three questions internally.
What exactly went wrong and why? Not the surface answer. The root cause. If the onboarding was deprioritized, why was the CSM stretched to that point? If the promise was made in the sales cycle that CS couldn’t keep, what in the handoff process allowed that to happen? If the product failed, what in the escalation process meant CS found out at the same time as the customer?
Who needs to know about this? Some failures are isolated. Others are patterns. CS leaders who absorb failures account by account without connecting them to systemic issues miss the signal that something upstream needs to change. When the failure has a root cause that lives in Sales, in Product, or in CS process design, the right people need to be in the room for the post-mortem.
What changes as a result? Accountability without a process change is just blame with a debrief attached. If CS identifies a root cause and doesn’t change the process that created it, the same failure happens to the next customer. Name the change. Assign ownership. Set a timeline. Make the internal accountability as specific as the external recovery plan.
What’s actually at stake
CS leaders who handle rightfully unhappy customers well build something most CS orgs never develop.
A reputation for integrity under pressure.
Customers who watch a vendor own a failure honestly, address it specifically, and follow through on the recovery become some of the most loyal advocates in the book. Not despite the failure. Sometimes because of it. Because they saw how the organization behaves when things go wrong and they trusted what they saw.
The customers who watch a vendor deflect, over-apologize, and underdeliver on the recovery become the loudest detractors. Not because the failure was unforgivable. Because the response was.
How CS handles the moments when it’s clearly in the wrong is one of the clearest signals of what kind of organization it actually is. And CS leaders who understand that treat those conversations not as damage control exercises but as some of the highest-leverage relationship moments they’ll ever have.
The customer who is right to be unhappy is also the customer who is watching most closely to see what CS is made of.
Show them.
