10 cold call objections and how to answer them without a script
An objection on a cold call is rarely an argument. Most of the time, it’s a polite way to take back control of a call they never asked for.
That’s why memorized comebacks fail: they address the sentence that was said instead of what triggered it. The prospect can hear the answer missing the point, and they hang up.
Why canned answers don’t work
An SDR who recites holds a rhythm that isn’t the rhythm of a conversation. You can hear it within two seconds, and it triggers exactly the distrust you were trying to avoid.
The other problem runs deeper. A prepared answer assumes you’ve understood the objection. But “I don’t have time” doesn’t mean the same thing at 8:30 am from someone starting their day and at 5 pm from someone who hasn’t figured out who you are.
The only rule that holds: ask before you answer. A short question gives you the information you need, and it turns the call from a monologue into an exchange.
The ten that keep coming back
“I don’t have time.” The most common one, and often the most sincere. Don’t negotiate for thirty more seconds, offer a real slot: “I get that. Would you rather I call you back tomorrow morning, or later this week?” You get either a phone appointment or a clear no, and both beat a conversation squeezed out of someone.
“Send me an email.” In most cases, it’s an exit from the conversation. Accept, then get one piece of information: “I’ll send it over. So I don’t send you something generic, what exactly do you handle on this?” You’ll know whether the address leads anywhere.
“We already have a tool.” Good news: the need exists and so does the budget. The useful question isn’t what they have, it’s how long they’ve had it and what annoys them about it. “Have you been on it for long?” opens more doors than any feature comparison.
“I’m not the one who handles this.” Don’t leave right away. The person on the line knows who decides, and often why things are stuck. “Do you know who owns this topic on your side?” and, if you can, “is it an active subject right now, or more on the back burner?”
“Not interested.” Said in the first five seconds, it’s not an opinion on your offer: the person hasn’t had time to find out what this is about. One follow-up, short, naming the problem rather than the product. If the no is confirmed, exit cleanly.
“Call me back in six months.” Ambiguous. It can be a real budget calendar or a polite no. One question settles it: “Is anything specific happening between now and then?” If the answer is vague, you know where you stand, and you don’t block a slot for nothing.
“How much is it?” Asked very early, this question often serves to cut the call short. Answer it anyway, no dodging: an evaded price loses trust immediately. Give the ballpark, then bring it back to usage: “it mostly depends on how many people are calling, how many of you are there?”
“How did you get my number?” Handle it seriously and without embarrassment. Say where the information comes from, and if the person asks not to be called again, write it down and respect it. A contact who asks this question has often been approached badly before you.
“We don’t have budget.” Rarely final. What’s missing, most of the time, is a priority. The money comes after. “Is this a subject that just isn’t a priority this year, or is the budget itself really locked?” The answer tells you whether to follow up later or move on.
“Send me some documentation, I’ll take a look.” A variant of the polite exit. Same method: accept, then propose the next step right away. “I’ll send it today. Can we grab five minutes Thursday so you can tell me if it’s off the mark?” Without a date, there won’t be a next step.
What matters more than the answer
The silence after the question. Most SDRs fill it within two seconds, and they kill the information they just asked for. Let the person answer.
The tone, next. An objection handled in a negotiating tone turns the call into a power struggle. Handled with real curiosity, it becomes a conversation, and sometimes a meeting.
Finally, knowing when to leave. A clear no beats a “maybe” that will clutter your pipeline for six months. An SDR who can get out of a dead call fast fits more useful conversations into their day.
How to get better at this
Objections are worked on with recordings. A shared document won’t change anything.
Take twenty calls from the week where an objection was raised. Listen only to the thirty seconds that follow. You’ll see two things very quickly: the objections that come up for you in particular, and the team’s reflex in front of each one. That reflex is what you correct. The vocabulary will follow.
This exercise assumes you have the recordings and can find the calls in question. At Ubic, every call leaves its recording, its transcript and its status in the CRM. You filter on the status to replay only the calls where an objection was raised.
And keep the structure of the call in mind while you do this: most objections appear when a block was skipped earlier. We cover that in building a cold call script in 4 blocks.
Frequently asked questions
Should you memorize answers?
Learn the question to ask, not the answer to give. The question is stable, the answer depends on what the person says.
How many times should you push back on an objection?
Once. Two pushes on the same no tip the call into insistence, and that’s what gets your number reported.
Is an objection a good sign?
On balance, yes. It means the person listened long enough to formulate something. The real bad sign is polite silence followed by a “goodbye.”
How do you handle an objection you’ve never heard?
By repeating it. “If I understand correctly, the problem is that…” buys you time to think and checks that you’ve understood. It’s the only universal answer there is.
