The Skeptical C Who Wants Proof

That's a C, and the skepticism isn't a problem to get around. It's how they decide whether to trust you. Give them proof and the whole call gets easier. Try to reassure your way past them and you'll be on the phone a long time.

What the skepticism actually is

C-style callers run on accuracy. They want things correct, and they build trust by verifying, not by feeling reassured. So when a C pushes back on your fix, they're usually not attacking you. They're checking your work, the same way they'd check anyone's. The rep who reads that as hostility gets defensive, and a defensive rep against a C is a bad call for everyone.

Here's the reframe that helps, and I'll be straight that this is trainer experience more than measured fact: a C's doubt is an invitation to show your reasoning. They're not saying "I don't believe you." They're saying "show me why this is right and I'll come with you." Most reps hear the first thing. The good ones answer the second.

Where reps lose a C

The instinct under pressure is to sound confident and warm. "Don't worry, this'll definitely fix it, I do this all day." To a C, confidence with no specifics behind it is a warning sign, not a comfort. It sounds like someone covering for not knowing. The warmer and vaguer you get, the more they dig in, because now they're not sure you actually understand the problem.

The other common miss is guessing. A C will catch it. If you float a fix you're only half sure about and present it as certain, and it doesn't work, you've confirmed their suspicion that you were winging it. From there they want a supervisor, or they want a case number and a paper trail, and the call's gone sideways.

What works with a C

Match their currency, which is specifics. Say what you're checking and why. "I'm looking at the signal levels on your line right now. Your downstream is fine, but the upstream is out of spec, which is exactly what causes the drops you're describing." You just gave them something concrete that lines up with what they've seen. That's what earns a C's trust, evidence that fits the facts they already have.

Be precise about what you know and what you don't. A C respects "I'm not certain this is it, but here's what the data points to and here's how we'll confirm" far more than false confidence. Naming your uncertainty accurately reads as competence to them, because it means you know the difference between a fact and a guess.

Then give them something to verify against. A reference number. The exact next step and what to watch for. "If this is the fix, your upstream reading will come back in range within about ten minutes, and you'll see it stabilize on the modem page you were already looking at." Now they can check you, which is the only kind of resolved a C fully believes.

The point

You don't calm a C down by turning up the reassurance. You calm them down by showing your work. Say what you're checking, be exact about what's certain and what isn't, and hand them something they can verify for themselves. The skeptical caller who was interrogating you at the start of the call is often the easiest one to satisfy by the end, because once a C has proof, they're done. They don't need to like you. They need to be able to check that you were right.