The Problem Is Trying to Tell You Something
The customer issue you’re trying to close may be pointing at the part of the business no one wants to own.
A customer problem is often the first honest version of what the business actually built.
I didn’t always see it that way.
Earlier in my career, I mostly wanted problems to go away. An angry customer needed relief. A launch issue needed a room. An executive escalation needed a timeline and enough context to lower the temperature.
That work matters. Customers don’t care that you’re still diagnosing root cause when they need service restored or a charge explained.
But urgency can fool you.
You can solve the customer in front of you and leave the next customer standing in the same hole. I’ve done that. The issue gets patched, the metric settles, the meeting ends, and everyone exhales too early.
Then the same problem comes back.
Different customer. Same bruise.
That’s when CX teaches the harder lesson: the problem is rarely just the problem. It’s evidence.
The customer finds the crack first
I didn’t enter CX through some carefully designed career plan. I came into it through messy work: product launches, broken handoffs, customer complaints that made more sense than our internal explanations, and frontline teams trying to protect a promise with tools that weren’t always built for the moment.
You can design a product, price it, sell it, support it, and explain it internally until everyone in the room feels comfortable.
Then a customer tries to use it.
That’s where the real test starts.
I remember when we started getting calls from Xfinity Mobile customers who wanted to unlock their phones earlier than the policy allowed. At first, it sounded like a normal policy dispute. Customers were saying they were entitled to unlock their devices, and the team was trying to figure out where that expectation was coming from.
Then we found it.
A support article had been overwritten. The unlock period in the article had changed to 30 days, even though the actual policy hadn’t changed.
That changed the whole conversation.
The customers weren’t being difficult. They were reading what we had published and asking us to honor it. The calls weren’t just call volume. They were evidence that we had created two versions of the truth: one inside the policy and one in the customer-facing support experience.
And the customer found the gap before we did.
That’s why problems matter. They show where internal confidence runs into the customer’s actual life.
I used to hear a complaint and think, “How do we fix this?”
Now I try to ask:
What had to be true inside the business for this to exist?
The problem isn’t always where the pain appears
Every company has a preferred version of its experience.
Then a customer tries to complete one ordinary task and the story starts to fall apart.
They want to understand the first bill. They want to change service without getting bounced across channels.
None of that is unreasonable.
Still, these are the moments where trust gets nicked. More often than not, the company makes the customer carry internal complexity.
Pain also tends to appear downstream from the cause.
By the time Care hears the anger, the experience has usually been shaped somewhere else. Maybe the expectation was set in Sales. Maybe the policy came from Legal. Or the doubt started in a digital flow that answered almost everything except the one question the customer actually had.
I’ve seen agents apologize for policy choices they didn’t make. I’ve seen good people create workarounds because the official process made the customer more frustrated.
After a while, that becomes its own operating model: the business designs the complexity, the employee humanizes it, and the customer decides whether to forgive it.
Bad bargain.
If the same issue keeps coming back, training may only be teaching people how to carry a problem the business should’ve removed.
Change what you listen for
When I was starting out, I used to listen for the fix. Who needs to respond? What do we tell the customer? What goes in the readout?
Fair questions. Incomplete questions.
The better question is less comfortable:
What is the problem revealing that we’d rather not see?
Sometimes it reveals a broken handoff. Other times it exposes a promise the company likes making more than supporting. A repeat call may show that the first resolution was more fragile than the report suggested.
This is where the numbers can lie a little. The customer may be marked as served, even if they leave less confident. The call may close, even if the agent knows the customer is coming back. One team may hit its target while the mess quietly moves to someone else.
This is where CX leaders need backbone.
Bring the customer story into the room. Keep it specific. Name the business condition behind it. Ask for the decision that would change the next customer’s experience.
Then stay with the issue long enough for ownership to become uncomfortable.
The reaction becomes the culture
Leaders often say they want problems surfaced early. Some do. Some want the sanitized version, though they may not say that out loud.
They teach it through the reaction.
A team brings a hard customer issue forward and gets cross-examined before anyone understands the pattern. A frontline leader shares what agents are hearing and gets asked whether the sample size is large enough. A CX team names a repeat friction point and the room drifts into metric defense.
People remember that.
The next version gets softened. The sharper customer quotes disappear. Someone changes “customer pain” to “opportunity area,” because apparently a plain sentence about customer frustration is where we lose our nerve.
I know why this happens. Leaders are under pressure. Teams protect their lanes. Nobody wants one more problem on the table.
Still, the signal lands.
Punish the raw version and people will bring you the edited one.
That’s how companies lose access to the truth while still believing they’re listening.
Use the problem before it gets wasted
I don’t think the goal is to love problems. Too tidy.
Pay attention to them.
A recurring issue deserves a better conversation than “how do we respond?”
Take one issue next week and write the customer moment in plain English. Not the theme name. Not the sanitized label. The actual moment a customer would recognize.
Then ask where the business created the condition. Was it the offer, the policy, the handoff, the system rule, the incentive, the channel design, or the way success is measured?
Identify the decision that would reduce the chance of the next customer hitting the same wall.
This is where judgment matters. Not every problem needs to become a company-wide initiative. But the right problem has to become harder for the business to ignore.
Repeat contacts cost money. So do credits, confused customers, worn-out agents, and trust that keeps leaking before anyone sees the cancellation.
So yes, fix the customer in front of you. Correct the order. Restore the service. Do the human thing.
Then don’t rush away from the problem too quickly.
Stay there for one more question:
What did this customer just tell us that our own system was trying not to say?
I’d love to hear your version of this: what’s a customer issue you’ve seen that turned out to be pointing at something bigger inside the business?
www.marklevy.co
Follow me on Linkedin
What Successful CX Leaders Do on Sundays
DCX Links: Six must-read picks to fuel your leadership journey delivered every Sunday morning. Dive into the latest edition now!
Thanks for being here. I’ll see you next Tuesday at 8:15 am ET.
👉 If you enjoyed this newsletter and value this work, please consider forwarding it to your friends and colleagues or sharing it on social media. New to DCX? Sign Up.
✉️ Join 1,600+ CX leaders who stay ahead of the next customer curve.
Human-centered insights. Plug-and-play frameworks. Smart tools that actually work. All designed for CX pros who want to build with purpose—and deliver with impact.
👉 Subscribe today and get the tools to elevate your strategy (and your sanity).