Making Requests Instead of Demands

That close sounds fine. It is warm, it is polite, and it commits nobody to anything. "We'll get that sorted out" is not a request. It is a mood. The customer leaves the call feeling better and understanding nothing about what happens next, who does it, or when.

NVC draws a hard line between a request and a demand, but the line reps trip over more often is between a request and a vague reassurance. A vague reassurance feels kind in the moment. It is actually the least respectful option on the table, because it hands the customer nothing they can hold you to.

What makes something a demand

A demand is any ask where the other person only has one acceptable answer. "You'll need to reset your router and call back if it's still down" is a demand dressed as a request, because there's an implied penalty (another call, more frustration) if they push back or ask for something else. Customers feel the difference even when they can't name it. A demand narrows the room. A request opens it.

Specific beats warm

The instinct to close soft comes from a good place. Reps don't want to sound like they're issuing orders, so they round every commitment down into something vaguer and friendlier. But vague isn't actually friendlier. It just delays the moment the customer finds out nothing concrete happened.

A specific request does more emotional work than a warm, fuzzy one, because it's the thing that lets the customer relax. "I'll follow up" is an abstraction. "I'll call you back by 3pm today with the credit amount" is a fact the customer can plan around. Specificity is what stops the callback.

Doable is not the same as easy

A request also has to be something the other person can actually do right now, in this conversation. "Can you just be more patient with our hold times" is technically a request, but it's not doable in any concrete sense. There's no action attached to it. Compare that to, "Can I text you a status update in two hours instead of you calling back in?" That's a request with a verb, a time, and a channel. The customer can say yes or no to it immediately.

This matters just as much when the rep is the one making an internal request, to a supervisor, to dispatch, to another department. "Can someone look into this" gets ignored because it's not doable by anyone specific. "Can you confirm the truck roll for account 40021 is still scheduled for tomorrow morning" gets an answer, because there's a name, an account, and a yes or no waiting on the other end.

Why this cuts repeat calls

Most repeat calls aren't about the original problem going unfixed. They're about the customer not knowing what was supposed to happen, so they call to check, or call because the vague thing they were told never materialized on the timeline they assumed. A specific request at close removes the ambiguity that generates that second call. The customer knows exactly what to expect and when to be surprised if it doesn't happen.

It also gives the rep something to be accountable to. "I told them I'd follow up" is unfalsifiable. "I told them I'd call by 3pm" is a promise you either kept or didn't, and that clarity tends to change behavior on both sides of the call.

Building the habit

Before ending a call, ask yourself one question: could the customer repeat back exactly what happens next, who does it, and by when? If the answer is no, the close wasn't a request. It was a nice-sounding placeholder. The fix isn't more warmth. It's one more sentence with a name, an action, and a time attached to it.