Customers hate three things: unknowns, surprises, and repeating themselves.

Onboarding can produce all three in a single call, and the most common way it happens is that somebody agrees to something they aren't sure about, nobody challenges it, and the call ends on schedule.

I've written before about the Confidence Question, which asks how confident a customer is that you'll help them get what they came for. This is its twin, and it points the other way: at what they have to do.

Two Questions, One Trigger

The moment is specific. Immediately after you've laid out what the customer is responsible for, before you move on to anything else.

First, the discovery question:

Of the things I just laid out that are your responsibility, which do you have questions or concerns about?

Then stop talking. The pause is doing the work.

If they raise something, that's the good outcome, and I'll come back to what it costs. If they say they're fine, you don't move on yet. You lock it in:

So just to be clear, you're 100% confident in you or your team's ability to execute on those things we just laid out?

The second question exists because the first one is easy to wave off. "Any questions?" invites a no. Asking someone to affirm total confidence in their own team's ability to execute is a different request, and people hesitate before answering it in a way they don't hesitate before saying no thanks.

If they say yes, hold them to it out loud, and make it light:

I'm going to hold you to that. Seriously, if that confidence ever drops below 100%, you have to tell me. You'll do that, right?

Now you have a customer who has agreed to report their own drop. That's worth more than any health score, because it comes from the only person who actually knows.

What You're Trying to Catch

The uncertain affirmation. A yes with nothing behind it.

They aren't lying to you. They're being agreeable, or they don't want to look like they weren't following, or they genuinely don't know what they don't know yet. And nobody challenges it, because it was a yes and a yes is what everybody wanted.

So it stands. Then it compounds. Uncertainty turns into poor execution, poor execution into poor results, poor results into frustration, and frustration into blame.

When a customer comes back angry at the end, it's almost always an uncertain affirmation that nobody challenged at the beginning.

The Part Most Teams Won't Do

Here's the instruction that makes this real, and it's the one that gets quietly ignored.

If surfacing their uncertainty means you don't finish onboarding today, that's fine.

Not tolerable. Fine. Correct. Preferable.

A completed onboarding with hidden uncertainty inside it is worse than an unfinished one, because now the uncertainty is load-bearing and invisible. Everything downstream is built on a yes that wasn't real, and nobody will find out until the results don't arrive and somebody goes looking for who to blame.

This is hard to hold because onboarding completion is usually a tracked metric and confidence is not. So the incentive says finish the call, and the incentive is wrong. If you're going to run this, whoever owns the number has to say out loud that a paused onboarding is an acceptable outcome, or your team will keep collecting yeses.

When They Say They're Not Sure

That's the win, so treat it like one. Normalize it first:

That's completely normal. A lot of customers are new to this, and you don't know what you don't know. That's exactly why we're doing this.

Then break it down rather than solving it in the abstract. Walk each item and find where they're stuck. You don't have to fix everything on the call: gather the unclear items, send specific resources for the ones that are just information, and book a focused call for the ones that aren't.

When They Say They're Confident and You Don't Believe Them

Trust that instinct. It's usually reading something real.

What works is going first, so the admission costs them nothing:

A lot of the companies I work with started exactly where you are, feeling a little uncertain. The ones who did well were the ones who spoke up early and got help. I'm sensing you might not be at 100%. If I'm wrong, tell me and we'll move on. But if you're not fully confident, you've got to tell me, because if I know, I can actually help.

If they admit it, stop and support. If they double down, document it and move forward, and watch their early execution closely, because you now have a specific prediction to check.

Making Room for It

The objection is always that onboarding calls are already full. That's true, and the fix isn't a longer call.

Most onboarding calls spend their time explaining things the customer can't use yet. Deep tooling comparisons before anyone has configured anything. Full lifecycle walkthroughs in month zero. Re-explaining what was covered fifteen minutes earlier.

Defer all of it. Tell them what's coming and when you'll cover it properly. That buys back more time than these two questions cost, and it removes material that was generating uncertainty rather than resolving it.

Why This Is Worth a Process

Because it's the cheapest intervention available and it targets the most expensive failure mode there is.

Two questions. Maybe ninety seconds if nothing comes up. And what it prevents is the account that goes quiet, underperforms for two quarters, and arrives at renewal with a grievance nobody can trace, because the moment it started was a nod in an onboarding call that everyone experienced as a success.

Prevent uncertainty early, or fight it later. You don't get a third option.