The Customer Who Says Yes But Isn't On Board

That yes cost you a second call. And you could hear it was hollow the first time, if you knew what to listen for.

The yes that isn't one

Some people say yes to end the friction, not because they're convinced. It's most common in S-style callers. The S runs steady and conflict-avoidant, and when they're on the phone with someone who sounds like the expert, pushing back feels rude or pointless. So they agree on the surface while they're not actually on board. Easier to say fine now and deal with it later, or just live with the problem.

It's not only an S thing. A C will say "sure, that makes sense" in a clipped tone, then hang up and go check your fix against the website before they believe it. An i might agree to keep things warm between you. A D might say fine just to get off the call and take their complaint somewhere else. The reason changes by style. The move you make about it is mostly the same.

And here's the part that trips reps up: the most agreeable-sounding callers are the ones most likely to hand you a hollow yes. The difficult customer tells you they're not satisfied. The pleasant one just agrees and disappears, and you find out later nothing was resolved.

Learning to hear it

This is trainer craft, not science, so take it as something you tune over time rather than a rule that's always right. Experienced reps learn to hear the difference between a real yes and a compliance yes.

A compliance yes tends to come fast and flat. "Sure, whatever works." It arrives before the caller could have really thought about it. They don't ask a single question about a fix they supposedly just accepted. The words go soft, "I guess that's okay," "yeah, I suppose." They go quiet.

A real yes usually has some engagement in it. The caller asks a clarifying question. They restate the plan in their own words. They name the next step themselves. Their tone shifts, even a little, like something actually settled. When you hear that, you can close with confidence.

None of these are proof. A quiet yes is sometimes a genuine, quiet yes. Treat the soft signals as a reason to check, not a verdict you've reached.

Testing the yes without a fight

The wrong instinct here is to argue them into it, to keep talking until they cave. That just produces another hollow yes from a more tired customer. The move isn't to overcome the objection. It's to make the objection safe to say out loud.

Two ways to do that. First, ask an open question that invites the doubt instead of closing it off. "Does that work for you?" begs another reflexive yes. Try "what part of that feels shaky?" or "what's your hesitation?" You're telling them it's fine to have one.

Second, and this is the strongest move on a tech call, check the concrete next step. Don't ask if they're satisfied. Ask them to walk the fix. "When you go to reconnect tonight, what's the first thing you'll do?" Now you find out. Either they walk it back to you clean, and the yes was real, or they fumble, go quiet, or admit they're not sure where to start. That fumble is exactly what you wanted to hear. It's the real objection surfacing while they're still on the line and you can still fix it.

Why it's worth the extra minute

Getting the real objection out on this call is cheaper than the callback. A hollow yes doesn't make the problem go away. It just moves it to next week, when it comes back as a repeat call, an unresolved ticket, or a customer who trusts you a little less because the last fix didn't take.

So when a yes comes too fast and too flat, don't bank it. Spend the extra thirty seconds. Ask what feels shaky, or have them walk the step. You'll catch the ones who were never really with you, and you'll turn a polite goodbye that was going to bounce into an actual resolution.