AI SDR & Autonomous Outbound Pipeline EnginePlaybook3 min readUpdated September 2026

Cold Call Objections: What to Say When a Prospect Tries to Hang Up

Handle cold call objections by working out what each one really means: ask about their current setup after not interested, propose a specific follow-up when they say send me information, and treat a gatekeeper as a policy problem rather than a pitch audience. Know when to let the call end.

The goal with any objection isn't to argue past it. It's to find out whether there's a real reason behind it worth addressing, or whether the prospect genuinely isn't a fit and the call should end there.

Vendors Covered in this Article

Disclosure: We may earn a commission if you buy through some links on this page. It doesn't change what we recommend.

The excuses that show up before you've said anything useful

"Not interested" delivered within the first few seconds of a call usually isn't a considered rejection of your offer; it's a reflex response to being interrupted by an unknown caller. The content of your pitch hasn't registered yet, because there hasn't been time for it to.

Rather than defending the offer against an objection that isn't really about the offer, acknowledge it and ask a short, specific question that requires more than a yes or no to answer. That shifts the interaction from a scripted brush off to an actual exchange, even a brief one.

"Not interested" almost never means what it says

A useful response is something like, "Fair enough, most people say that on a cold call. Can I ask what you're using for this today?" This doesn't argue with the objection; it moves past it by asking about their current situation, which most people will answer even right after brushing you off, because it's an easy, low commitment question.

If they answer, you have a real conversation started. If they repeat that they're not interested and decline to engage further, that's a genuine signal, and pushing further at that point usually just damages the interaction rather than saving it.

"Send me some information" without getting ghosted afterward

This phrase is often a polite way to end the call without committing to anything, and sending information with no plan for what happens next means the conversation is effectively over. Before agreeing to send anything, propose a specific follow up: "I'll send that over. Can I call you back Thursday to see what you thought?"

This converts a vague request into a concrete next step with a date attached, which is far more likely to result in an actual second conversation than sending a document into an inbox and hoping for a reply.

Turn a vague request for information into a concrete next step:

  1. Agree to send the information, then propose a specific follow-up, such as calling back on a named day.
  2. Ask for that follow-up before you hang up so the request doesn't quietly end the conversation.
  3. Send the information promptly, and reference the callback you agreed on in the message.
  4. Treat a refusal of any follow-up as a sign the request was a polite way to end the call.

"We already use a vendor" without trashing the incumbent

Criticizing a prospect's current vendor directly puts them in the position of defending a choice they made, which tends to make them dig in rather than reconsider. A better path is asking what's working well with the current setup and what, if anything, they'd change if they could, which surfaces real gaps without forcing them to admit the original decision was wrong.

If there's a genuine gap, you now have something specific to address rather than a generic pitch about being better. If there isn't a gap they'll admit to, that's useful information too, and a reason to note the account for a later check-in rather than pushing on a closed door.

The gatekeeper objection is a different problem, not a mini pitch

A gatekeeper isn't evaluating your offer; they're following a policy about who gets through to their boss, so pitching them your product like a mini version of the real pitch usually fails, because they're not the audience and don't have the authority to say yes anyway.

A more effective approach treats the gatekeeper as a person doing their job, briefly and honestly explaining the reason for the call without oversellng, and asking directly for the best way to reach the person you're trying to reach, whether that's a specific time, an email introduction, or a different department entirely.

When to actually let the objection stand and end the call

Not every objection deserves a rebuttal. If a prospect clearly states they have no budget, no authority, and no interest after you've asked a real follow up question, continuing to push rarely changes the outcome and tends to burn the account for a future call. Ending politely and moving on preserves the relationship for a later attempt when circumstances might have changed.

Apollo's dialer can log call outcomes and notes directly against the contact, which makes it easy to flag an account as genuinely not a fit right now rather than losing that context and calling the same dead end again in three months.

Executive Capability Standard

What Good Looks Like

A team that handles objections well has a documented response for each common objection that asks a real follow up question rather than arguing, and reps who can tell the difference between an objection worth working and a genuine no.

Building The Capability (5-Stage Skill Ladder)

1. Learn:Listen back to a handful of your own recent calls and note exactly where an objection ended the conversation versus where a follow up question kept it going.
2. Do Manually:Draft your own responses to the common objections your team hears most and practice them out loud before the next round of calls.
3. Delegate:Have a senior rep run a short session reviewing real call recordings with newer reps, focused specifically on objection moments rather than the whole call.
4. Automate:Log call outcomes and objection types in Apollo so patterns across your whole team, not just one rep's calls, become visible over time.
5. Buy:Bring in outside sales coaching only if call recordings show the same objection consistently ending calls across multiple reps despite documented responses.

How to Get Started

Disclosure: We may earn a commission if you buy through some links on this page. It doesn't change what we recommend.

Apollo

Apollo's dialer lets you log call outcomes and objection notes directly against the contact, which is useful for tracking patterns and avoiding repeat dead ends.

Visit Apollo→

Frequently Asked Questions

How many times should I push back on the same objection in one call?

Once, maybe twice with a different angle if the first response clearly didn't land. Pushing a third time on the same objection tends to read as not listening, and most prospects who were going to reconsider will have shown some sign of it by the second attempt.

Should I use the same objection responses on every call?

Have a starting response for each common objection, but adapt it to what the prospect actually said rather than reciting it word for word. A response that sounds memorized is often what triggers the next objection, even if the words themselves were reasonable.

Is it worth calling back someone who said "not interested" and hung up?

Usually not on the same day or week. If nothing else has changed about their situation, a callback shortly after will likely get the same reaction. A call weeks or months later, ideally with a new reason to reach out, has a better chance of a different result.

About the numbers

This guide doesn't quote a sourced benchmark. Figures in it are estimates or general guidance, so check them against your own numbers.

Related Guides