What he missed wasn't in the ticket. The problem was solved. What wasn't addressed was the story she'd been telling herself for three days about what it means that the internet keeps going out, about whether anyone at this company actually cares, about whether she's being taken seriously. She came in with a technical problem and an emotional narrative. He fixed the technical problem and left the narrative running.

Nonviolent Communication, developed by Marshall Rosenberg, is a framework for the other part of that call. Not the fix. The conversation around the fix. It gives you a way to locate what someone actually needs so you can respond to that instead of just the surface demand.

The four parts

NVC has four components. They don't have to be used in sequence on every call, but knowing all four changes how you listen.

Observation

What you can see or hear, stated without evaluation. "Your service has been down since Tuesday" is an observation. "You've been dealing with a nightmare" is an evaluation dressed up as one. The distinction matters because evaluations trigger defensiveness. Observations give you something to work from.

On a call, this is the part where you restate what's happened accurately and specifically before doing anything else. "I can see this is the third call about the same issue in two weeks." That's the observation. You haven't blamed anyone or promised anything. You've just named what's real.

Feeling

What the caller is experiencing emotionally. NVC makes a distinction most reps don't: feelings are different from thoughts. "I feel like no one cares" is a thought about what others are doing. "I'm frustrated and exhausted" is a feeling. The first one is a story. The second one is something you can actually respond to.

You're not diagnosing the caller or asking them to do therapy. You're making a quick, tentative read: frustrated, worried, embarrassed, relieved. That read tells you what kind of response will actually land.

Need

What the caller is trying to get at the level underneath the request. The customer demanding a supervisor usually needs to feel heard, not a different person to talk to. The customer asking for a credit might need to know the company takes the disruption seriously, not just the money back. The customer who keeps asking "but why did this happen" might need to trust that it won't happen again.

Needs are things like reliability, respect, clarity, safety, autonomy. When you can hear the need, you can often address it directly instead of chasing the stated demand through a script that wasn't built for it.

Request

A specific, doable ask that addresses the need. Not "I'll look into this for you" (vague) but "I'm going to note this as a recurring issue and flag it for our network team, and I'll give you a direct number to call if it happens again before Thursday. Does that work?" The request is concrete. The caller can say yes or tell you what's still missing.

NVC distinguishes between a request and a demand. A request leaves room for the caller to say no or ask for something different. A demand closes that off. On a support call, keeping it as a request means you find out faster if your proposed fix doesn't address what the caller actually needed.

This is a precision tool, not a therapy exercise

The reputation NVC has in some circles is that it's slow, soft, and only for difficult conversations. That's not how it works on a call floor. You're not walking through the four steps out loud with every caller. You're using the model to calibrate what you're hearing and what you say next.

The observation part takes five seconds. The feeling read is a background process you're running while the caller talks. The need is what you're trying to locate underneath the complaint. The request is how you close. None of that is slower than what you're already doing. It's just more targeted.

What changes is that you stop responding to the surface demand and start responding to what's generating it. That's usually faster, not slower, because you're not re-explaining things that weren't the actual problem.

Where it connects to DiSC

The four components land differently depending on who you're talking to. A D doesn't want you to name their feeling out loud, they want you to act on the need fast. An S needs the feeling acknowledged before they can hear the request. A C wants the observation to be precise and the request to be verifiable. An i wants the whole exchange to feel human, not procedural.

NVC tells you what to listen for. DiSC tells you how to deliver what you find. They work together, not instead of each other.

The rep who fixed the three-day outage and still got a 2 did the technical job. What NVC would have added is a sentence or two between the fix and the close: naming what the caller had been dealing with, checking that the resolution actually addressed it, and making a specific request about what happens if it comes back. That's the gap. Not a longer call. A more complete one.

Want the full communication playbook?

The DiSC Deep Dive Guide covers communication scripts for every style, a cross-style friction matrix, and 36 exercises for building real fluency in the conversations that matter most.

Download free PDF guide Book a free intro call