Every founder, solutions engineer and new AE eventually hits the moment: the buyer asks something you can't answer, and your brain goes blank. These sales tips and sales scripts show you how to handle "I don't know" on a sales call without losing credibility, and how to practise it until it feels normal. Done well, a question you can't answer can actually build sales confidence on both sides of the table.

Why "I don't know" feels so dangerous

If you come from engineering, you're trained to be right. In a code review, guessing is a bad habit. On a sales call, the instinct flips into panic: "If I don't know this, they'll think the product isn't real."

So people do one of three things:

  • Bluff. "Yes, we support that." (You're not sure.) This is the one that comes back to hurt you in procurement or onboarding.
  • Ramble. Five minutes of thinking out loud until the original question is lost.
  • Collapse. "Uh, I'm not sure, sorry," followed by a visible drop in energy for the rest of the call.

Buyers don't expect you to know everything. They do watch how you behave when you don't. Calm and specific reads as trustworthy. Bluffing reads as risk.

The 4-step answer: Acknowledge, Clarify, Commit, Continue

Use this simple sales framework whenever you hit a question you can't answer.

1. Acknowledge honestly

Say it plainly, once, without apologising three times.

"Good question. I don't want to guess on that one."

That sentence does more for your credibility than a confident wrong answer.

2. Clarify what they actually need

Half the time, the question behind the question is easier than the question itself. Ask one of these discovery questions:

"Can I ask what's driving that? Is it something you need on day one, or more of a future concern?"

"When you say 'integrates with your CRM,' do you mean syncing contacts, logging calls, or something else?"

"Is this a must-have for the decision, or a nice-to-know?"

You'll often discover you can answer the real need, or that it's not a blocker at all.

3. Commit to a specific follow-up

Vague promises ("I'll look into it") sound like brush-offs. Be specific about who, what and when.

"I'll check with our CTO and send you a written answer by Thursday. Who else should be on that email?"

Then write it down where they can see you doing it. On video calls, saying "I'm noting that now" is enough.

4. Continue the call

Don't let one unknown hijack the conversation. Bridge back to what you were doing:

"So I've got that one on my list. Going back to what you said about onboarding new reps, how long does that take today?"

Sales scripts for the most common situations

The technical deep-dive you can't go into

"That's deeper than I can answer accurately right now. I'd rather get you the exact answer than a rough one. Would it help to set up 20 minutes with our engineer next week, or is a written answer enough?"

The feature you don't have

Don't pretend. Don't over-apologise either.

"We don't do that today. Can you walk me through how you'd use it? I want to understand whether it's a blocker or whether there's another way to get you the same result."

Pricing or contract terms you're unsure about

"I don't want to quote you something I'd have to walk back. Let me confirm the exact terms and send them over tomorrow. In the meantime, is there a budget range you're working within?"

Security and compliance questions

This is where bluffing is most expensive.

"Security questions deserve a precise answer. If you send me your questionnaire, I'll make sure it's filled in properly rather than me paraphrasing on a call."

The question that's really an objection in disguise

"Do you have customers in our industry?" sometimes means "I'm worried you won't understand us." Answer honestly, then address the worry:

"Not yet in your industry specifically. What would you need to see to feel confident we understand how your team sells?"

What not to do

  • Don't guess and hope. A wrong "yes" on a call becomes a broken promise in writing.
  • Don't say "great question" to everything. Once is fine. Every time sounds like a stalling tactic.
  • Don't hand over control. "I don't know, what do you think?" without structure makes you sound lost, not curious.
  • Don't forget the follow-up. The answer you promised is now part of your sales pitch. Missing it costs more than not knowing.

A quick pre-call checklist

Before any important sales call, spend five minutes on this:

  • [ ] List the three questions you'd least like to be asked.
  • [ ] For each one, decide: can I answer it, or do I need a "clarify and commit" script?
  • [ ] Know who on your team can answer technical, pricing and security questions, and how fast.
  • [ ] Have one bridge sentence ready to bring the call back on track.
  • [ ] Decide in advance what you will never promise on a call (custom features, discounts, timelines).

How to practise it

Reading the 4 steps is easy. Doing them while a buyer is waiting for an answer is not. That moment of blank-mind panic is a reflex, and reflexes change with sales practice, not with notes.

A simple drill for founders and teams:

  1. Ask a colleague to play the buyer and fire five hard questions at you, at least two of which you genuinely can't answer.
  2. Run the 4 steps out loud for each one. No pausing to think about the framework.
  3. Record it. Listen for apologies, rambling, and whether you actually got back to the call.
  4. Swap roles. Playing the buyer teaches you how calm "I don't know" sounds from the other side.

Repeat it a few times and the first sentence ("I don't want to guess on that one") becomes automatic. That's the point: when the panic arrives, your mouth already knows what to do.

Key takeaways

  • Buyers judge how you handle not knowing more than the gap itself.
  • Acknowledge, clarify, commit, continue.
  • Use discovery questions to find the real need behind a hard question.
  • Never bluff on features, pricing or security.
  • Rehearse with sales role play until the response is a habit.

If you want a place to practise hard questions like these against virtual customers who push back, that's what we're building at Kulissa.