My Wife Made Me Better at Customer Support. And Better as a Leader.

TLDR: The ability to de-escalate and redirect a frustrated customer is a real skill. But if you move straight to resolution without seeing the person first, you are not delivering great support. You are handling people. There is a difference, and it matters more than you think.


Super Slip Up

I used to think I had a superpower.

Take a frustrated customer. Someone who is ready to blow up the call, the chat, the ticket. Acknowledge the frustration just enough to dial down the heat, redirect them toward the problem, and get them focused on a resolution. Close the ticket. Move on.

I was good at it. Really good. And for a long time, I genuinely believed that was the whole job.

Then my wife called me out on it.

We were in an argument. What it was about is not important now, but she was frustrated and rightfully so. During that back and forth my brain (I) switched modes. Without even realizing it, I started addressing the conversation the way I would address a support ticket. Calm. Measured. Redirect the emotion, identify the problem, move toward resolution.

She stopped me cold when she said:

“Stop customer servicing me. Stop HANDLING me.”

That shut me up.

While I was not trying to dismiss her, I thought I was helping by identifying the problem and finding ways to address it. Yup, I missed that the source of the problem (Me) was not being addressed. I thought if we could just “get past the frustration” and get to the “actual issue”, we would be fine.

But that was exactly the problem.

In my rush to fix things, I had stepped right over the person in front of me. She was not asking me to resolve the argument faster. She needed me to see her frustration, the weight it put on her, the why it became a problem. She needed to have her emotional investment recognized, not just as a waypoint on the road to a resolution, but as something real and valid that deserved to be acknowledged on its own terms.

I have carried that with me for well over a decade, both personally and professionally. It sits there with me in every support interaction. It continually inflects how I lead. I will not pretend I get it right every time, but I try to remember the lesson.

The “Superpower” Was Real. It Was Just Incomplete.

I am not sure that my instinct was wrong, just incomplete. The ability to de-escalate a frustrated customer and redirect toward a solution is a genuine, valuable skill that every support member should hone.

But there is a version of that skill that goes too far, and it is easy to miss because, on paper it still “works”.

Tickets close.

  • Customers move on.
  • Metrics look fine.

What we miss is the difference between these two responses to a frustrated customer. As an example that difference could look like this:

“I hear that you’re frustrated. Let’s get this resolved.”
versus
“I completely understand why this has been so disruptive, and I’m sorry you’re dealing with it. That makes complete sense. Here’s what we’re going to do.”

The first one placates and pivots and the second one approaches with validation and then moves to solve. They sound similar on the surface, but customers feel the difference. So do your teams when they watch you model it.

The first gets the ticket closed. The second builds trust that outlasts the ticket.

What Changes When You See the Person First

I want to be honest here because I think this topic can get a little abstract, and in CS and CX work, abstract advice doesn’t survive contact with a high-volume queue

So lets be specific about what actually shifts when you lead with seeing the person.

Customers return with less armor on.

    When humans feel genuinely seen, not managed, they carry less anxiety into the next interaction. They return with more faith that your team will actually be there for them. They are less defensive, more patient, more willing to work with you toward a solution. That is not a soft outcome. That is a measurably better support environment for everyone involved, including your agents.

    Your team becomes more resilient.

    Support agents who are given permission to acknowledge emotion, rather than troubleshoot around it, experience less of the emotional numbness that quietly leads to burnout. When we stop asking people to pretend a customer’s frustration is not there, you remove a kind of cognitive dissonance that wears people down over time. There is a cost to performing calm while internally managing the weight of someone else’s distress. Letting your team be present with it, rather than suppressing it, is actually the more sustainable ask, after all Employee Experience is >= Customer Experience.

    It becomes a differentiator you can not automate.

    While AI and self-service tools help your team close tickets, they can not practice actual empathy. Customers recognize when a real person genuinely registered their frustration and cared about it. Moments like this are when your team creates a loyalty signal that no CSAT or CES score fully captures. With many industries moving faster and faster toward automating human roles, those human moments are invaluable and worth protecting.

    It makes you a better leader, not just a better agent.

    The skill we are talking about, sitting with someone’s emotion long enough to understand the why before moving to a solution, is the same skill that makes a manager someone their team trusts. In hard conversations. In performance reviews. In times of organizational change. This is not just a customer support leadership principle either; it extends itself as a core leadership principle.

    Honest About the Hard Parts Too

    It is easy for me to share this with you. After all this happened a long time ago and I have had years to stew over it. However, I am also keenly aware that implementing this attitude with your team this is either simple or without cost. That would not be fair to the people doing the actual work, every day.

    The intent matters more than the language – that can be hard to teach.

    “Emotional validation” can become its own form of scripted placating if it is not genuine. “I completely understand your frustration” delivered flatly, or with no real belief behind it, is just a polished version of what my wife called out. The risk is that if you focus on teaching your team phrases, then those teams may learn the phrases without taking the posture to heart. And as I said earlier customers know the difference. Words, without real presence behind them, is still a way of “handling” people.

    It takes time, and that has real implications.

    In high-volume environments, adding genuine emotional acknowledgment to every interaction has a handle time impact and that is a tension worth naming honestly, not minimizing. The answer is not to skip the human moment, but instead help teams get fluent at it, so it does not feel like an add-on, but part of the natural flow of a good interaction. That fluency takes varying amounts of investment per agent, and it requires leadership to protect that space rather than optimize it away.

    Not every customer wants to be validated in this way.

    There are customers who find any emotional acknowledgment slow or even condescending – they “just want it fixed”, and quickly. Reading the room is as much a part of the skill as recognizing distress. The lesson here is not always “lead with feelings”, but that we should never skip them entirely without actually looking.

    Emotional labor without reciprocal care leads to burnout.

    When you are asking your team to be emotionally present for frustrated, sometimes hostile customers, and sometimes interaction after interaction. That is a meaningful and weighty ask. As a leader, if you expect that kind of presence from your teams, remember that you need to offer the same in return.

    • Check-ins.
    • Psychological safety.
    • Space to decompress.

    The expectation of empathy, without a culture that supports the people delivering it is a fast road to the exact employe burnout and customer dissatisfaction you need to prevent.


    The Research Landed Where the Story Did

    I find it reassuring that what I stumbled into through a hard personal lesson, has some science and research backing behind it.

    Zendesk ran research on the impact of Empathy in the support experience and found that 60% of customers were satisfied with an empathetic agent who couldn’t fully solve their problem, compared to only 16% satisfied with an agent who solved it but lacked empathy. (Ramoop, Zendesk Blog)

    A recent Harvard Business Review study of nearly 12,000 consumers across 11 countries found that feeling genuinely understood is one of the strongest drivers of customer loyalty. (Zaki & Kalcher, HBR, November 2025)

    Maybe the lesson isn’t new and maybe a lot of my fellow support folx already know it. However, knowing it and actually doing it, especially in a high-volume, high-stress, or low psychologically safe work environments can contribute to making this a harder mindset to practice.

    What I Actually Want You to Take From This

    Validating emotions, is part of the path to resolving the problem, which makes it better than just closing a ticket. To point.

    The human on the other side of that ticket, that email, that phone callthey are a full human being. They came to you carrying something. Maybe it is stress about the product, maybe it is stress from their job, maybe it is something you will never know about. You cannot and do not have to fix all of it, but recognizing it, and working with it makes a world of difference.

    When you work this way, something shifts over time, and more and more customers will sense how your team actually sees them as people. When they need to come back to support again, they can come back with less dread, and with trust and willingness to work with you.

    That is not just good for your customers, it is good for your team.

    My wife didn’t just challenge how I argued. She challenged how I expect myself to show up for people.

    I am still working on it, but I am grateful she said something.


    I will leave you with this. Think about the last time a customer came to you frustrated. When you solved their problem, did you see the person while you were doing it?


    Further Reading:

    “Customers Expect Empathy. Here’s How to Deliver It.” – Jamil Zaki & Conny Kalcher,
    Harvard Business Review, November 2025.

    “What Is Customer Empathy? Tips and Importance” – Tara Ramroop, Zendesk Blog.

    Add a Comment

    Your email address will not be published. Required fields are marked *

    This site uses Akismet to reduce spam. Learn how your comment data is processed.