Are You Handling Requests or Reading Emotions?

Some companies have every metric in green and every customer in red.

Response times fine. Tickets closed. Surveys sent. And people still describe the experience as unpleasant.

The diagnosis is almost always the same: the team was trained to handle requests, not to read emotions.

Two conversations that look identical

A customer writes: "I need to move my Thursday appointment."

Answer A: "Done, moved to Tuesday."

Answer B: "Done, moved to Tuesday. Did something come up? If you need anything sooner, I can pull it forward."

Both resolve the request. Only one noticed there was a person behind it.

Handling requests is processing. Reading emotions is serving.

What the customer feels is almost never written down

Behind a complaint there's fear of losing money, embarrassment about a mistake, time pressure, exhaustion, or the feeling of not being taken seriously.

None of that shows up in the form. All of it decides how the interaction will be remembered.

How to train it without turning it into a script

• Name the emotion before solving: "I get that this left you stuck, let's fix it."
• Ban the word "system" as an explanation. Explain in the person's terms.
• In service meetings, review a whole conversation, not just the metric.
• Ask your team what the customer felt. If nobody knows, nobody was listening.

Judgment and empathy don't mix

There's a silent obstacle: judging. The moment you decide the customer is exaggerating, didn't read, or is just difficult, you lose the ability to understand them. Judgment and empathy can't share the same head at the same time.

That's why serving well starts on the inside: look past what you see, and risk understanding before you grade.

Where this comes from

It's one of the ideas from the "Understanding you" chapter of my book *Estoy para servirte*.