What to Say When a Prospect Asks a Question You Can't Answer

What to Say When a Prospect Asks a Question You Can't Answer

When a prospect asks a product or technical question you cannot answer, say so in one sentence, ask what sits behind the question, and commit to a named person and a date for the answer. Do not guess. A wrong answer given with confidence costs more than an honest "I don't know", and the question itself is usually the best reason to book the next call.

Why guessing is the expensive option

The reflex is to keep the call moving. You say "yes, I think we do that" and hope it is true.

If it is true, you gained nothing. If it is false, the prospect finds out in the demo, in front of colleagues, and everything else you said gets discounted with it.

An SDR's job on a cold call is not to be the product manual. It is to find out whether there is a problem worth 30 minutes of an AE's time. Our benchmark of 1,000,000 B2B cold calls in France shows that 65% of reps already open by explaining what they sell. The reps who book meetings talk less about the product, not more.

So a question you cannot answer is not a test you failed. It is a prospect showing you what matters to them.

Three moves when you do not know the answer

1. Find out what the question is really about

"Does it integrate with our ERP?" can mean ten different things. They may need a nightly export. They may have been burned by a tool that promised an integration and delivered a CSV. They may be looking for a polite reason to end the call.

Ask before you answer. In our data, asking "What do you mean?" before responding to an objection lifts conversion by 197%. The same move works on a technical question, because a hard question is often an objection in disguise.

Three ways to say it without sounding evasive:

  • "Good question, and I want to give you the right answer. What would you need it to do exactly?"
  • "How do you handle that today?"
  • "If the answer is yes, what does that change for you? And if it is no?"

The second one matters most. Discovery questions starting with "how" lift conversion by 190% in our benchmark. A prospect describing their current workflow gives you more than any feature answer would.

2. Say what you know, then draw the line

You rarely know nothing. Split your answer in two parts and say both out loud.

What is confirmed: "We connect natively to HubSpot and Salesforce. That part I can tell you for certain."

What is not: "Your custom objects, I do not know. I would rather check than tell you something wrong."

Avoid the two words that cause the damage: "should" and "probably". "It should work" is heard as "it works". Three weeks later it becomes "your colleague told us it works".

Avoid the opposite mistake too. Do not say "no, we don't do that" when you have not checked. An unverified no kills a deal as surely as an unverified yes.

3. Turn the open question into the next step

"I'll get back to you" is where most of these questions go to die. Make the commitment specific enough that the prospect could hold you to it.

  1. Repeat the question back. "So the question is whether call outcomes can write to a custom object in your CRM, without manual export. Correct?"
  2. Name who will answer. "Our solutions engineer knows this in detail."
  3. Give a date and a channel. "You will have the answer by email tomorrow before noon."
  4. Attach the meeting. "And if the answer is yes, it is worth 30 minutes with her on Thursday. Does 10am or 4pm work?"

The fourth step is the one reps skip. A technical question is a legitimate reason for a meeting with someone more senior. It is a stronger reason than "I would love to show you the platform".

If the feature is a deal-breaker and the answer might be no, say that as well. "If we cannot do this, I will tell you tomorrow and save you the demo." Prospects remember the rep who did not waste their time.

The questions European prospects ask that SDRs rarely know

In France and across Europe, the unanswerable question is often not about features. It is about data and procurement.

  • "Where is the data hosted?"
  • "Are calls recorded, and who can access the recordings?"
  • "Can you send your DPA to our legal team?"
  • "Do you work with our reseller or do we contract directly?"

These are the worst questions to improvise on. A vague answer about data hosting reaches the prospect's DPO, and the DPO has no reason to be generous.

Prepare a one-line answer for each, written by the person who actually knows, and a rule: anything beyond that line goes to the named colleague. "I do not want to paraphrase our security documentation. I will send it to you today" is a perfectly good answer on a cold call.

Build an "I don't know" list as a team

The same eight or ten questions come back every month. Treat them as coaching material, not as individual failures.

  • Log every question a rep could not answer, in the call notes, word for word.
  • Review the list every two weeks. Questions that appear three times get a written one-line answer and an owner.
  • Roleplay the moment of doubt, not the perfect answer. The skill to train is noticing "I am not sure" and switching to a question, in under two seconds.
  • Listen to how your best rep says "I don't know". It usually sounds calm, short and followed by a question.

Enterprise sales teams pair their sellers with technical specialists for a reason. Our founder spent five years as an account executive at Google Cloud. Nobody there expected one person to hold the whole product in their head. Give your SDRs the same permission.

How Sonik approaches questions a rep cannot answer

We try to shrink the number of surprises before the call, then use the remaining ones for coaching. Sonik's AI call prep puts the account context in front of the rep before the pickup, so the conversation starts from the prospect's situation instead of a feature list.

Sonik contact view: account intelligence and AI qualification before the call
Before the pickup: account intelligence, experiences and the signals that qualify the contact, on one screen.

A rep who knows why this contact is on the list today, whether it is a website visit, a job change or a closed-lost deal, asks better questions and gets fewer feature interrogations in the first minute. The list itself comes from the signals already in your CRM.

After the call, AI coaching works from the real conversations. The moments where a rep hesitated, guessed or over-promised are the ones worth replaying in the next one-to-one.

Conclusion

You do not need every answer. You need three moves: ask what sits behind the question, separate what is confirmed from what is not, and commit to a name, a date and a meeting. This week, pull your last 10 recorded calls and note every question where you said "should" or "probably". That list is your team's first "I don't know" list, and writing the real answers is an hour of work.