The Four Things Prospects Say That Sound Like Objections but Aren't
'Send me an email' isn't an objection. Neither are the other three phrases reps keep treating as brick walls in outbound calls.
Every CRM I've ever audited has the same pattern sitting in the disposition field: a fat cluster of outbound calls logged as "objection – not interested" or "objection – happy with current vendor," closed out at the twelve-second mark. Pull the call recording and you'll usually hear something different. No objection was raised. The prospect said four words and put the phone down, and the rep coded it as resistance because resistance is the only category the CRM gives them to choose from. It isn't resistance. It's a reflex — the sales-call equivalent of saying "fine, you?" to someone who asks how you are without meaning it. Training reps to fight reflexes with objection-handling technique is a big part of why so many outbound calls die on a no that was never really a no.
The test that tells you which one you're dealing with
An objection is specific resistance to something you introduced — a claim, a price, a timeline — and it requires the prospect to have actually processed what you said before they can push back on it. A stall is a scripted disengagement line the prospect would say to any unsolicited caller, about any subject, at any point in the conversation, usually before you've said anything they could rationally evaluate.
The test is simple: would they say this exact sentence to a caller selling something completely different? If "no thanks, we're happy with our vendor" would come out of their mouth for a product they've never used from a company they've never heard of, it's not an evaluation. It's a door closing on reflex, and it deserves a different response than a door closing on a considered judgement.
Four phrases, four misdiagnoses
| Phrase | Sounds like | Actually is | What moves it |
|---|---|---|---|
| "Send me an email" | A request for information | An exit with plausible deniability | A specific question an inbox can't answer |
| "I'm not interested" (inside 5 seconds) | A verdict | A conditioned response to caller ID | Refusing to argue with it — reclaiming ten seconds instead |
| "We're happy with our current vendor" | A competitive objection | An unexamined default | A question about what "happy" is actually measured against |
| "Now's not a good time — call me back in Q3" | A scheduling constraint | A polite no with a return date stapled to it | Decoupling "time to talk properly" from "time for one sentence" |
Ranked in the order I see reps mishandle them most often, worst first.
"Send me an email." This one costs the most pipeline because it feels like a win when it happens. The rep hears "email," treats it as a genuine next step, says "great, what's the best address?", and hangs up having logged a positive outcome. Send-through rate on those emails sits somewhere around 2%, because nothing about the interaction gave the prospect a reason to ever open it. The fix isn't refusing to send the email — it's refusing to let the request end the conversation. "Happy to — so it's not generic, are you currently running something for this, or is it more of a capacity problem right now?" costs five seconds and turns a dead end back into a live one.
"I'm not interested," said before you've finished your opener. This is the purest reflex of the four, and the easiest to misdiagnose because it sounds so final. There is nothing to be "not interested" in yet — you haven't said anything worth evaluating. Reps handle this two bad ways: apologise and hang up, or over-argue for the next thirty seconds trying to manufacture interest from nothing, which reads as needy. What works is holding your ground for one line without arguing the merits: "Totally fair, you don't know what this is yet. Ten seconds, then tell me to get lost properly." Most people performing a reflex, rather than a decision, will give you the ten seconds.
"We're happy with our current vendor." This one deserves the 'We're Happy With Our Current Vendor' Response Guide because it's the phrase most likely to be hiding a genuinely valid objection behind a reflexive one. A real version of this sounds like "we just signed a three-year renewal in March" — specific, falsifiable, worth respecting. The reflexive version is vague and instant, delivered before you've named a single capability gap. The move is a clarifying question, not a battlecard: "Happy in what sense — has anyone actually benchmarked that against what's out there in the last year?" Half the time nobody has, and "happy" turns out to mean "haven't looked."
"Now's not a good time — call me back next quarter." The failure mode here is the callback graveyard: the rep sets a task ninety days out, the prospect never answers again, and a stall with a date stapled to it gets logged as a legitimate future opportunity. The fix is decoupling two things the prospect has conflated — a proper conversation, and twenty seconds of context. "Understood, I won't keep you — worth me sending one line now, so it's not a cold callback in three months?"
Why this is worth fixing at the training level, not the script level
Across the outbound floors I've reviewed calls on, I'd put it somewhere around six or seven in ten of the interactions logged as "objections" in the first thirty seconds are actually one of these four stalls. That matters because most objection-handling training is built to fight a battle that isn't happening — it drills reps on countering price resistance and competitive comparisons, real skills for later in a conversation that never got that far, because the call died to a reflex at second fifteen and got coded as though it died to a considered objection at minute five.
The 7 Objection Types Every Rep Must Recognize is worth reading for exactly this contrast — it'll show you what a genuine objection actually looks like, which makes the four reflexes above much easier to spot in your own calls.
What to actually train
- Split the CRM disposition codes. Stall and objection are different events with different remedies; collapsing them into one bucket means you can't see the problem, let alone coach it.
- Drill the specific one-liners above until they're just as reflexive as the stalls they're answering. You're not out-arguing a reflex with logic — you're meeting a fast, low-effort response with an equally fast one that happens to reopen the door.
- Run call reviews looking specifically for false-positive objections — moments the rep treated a stall as a wall and gave up early. The Objection Handling Scorecard for Call Reviews is built for exactly this kind of pattern-spotting across a batch of calls, not just one.
The prospect isn't lying when they say send me an email. They mean it, in the sense that it will genuinely get you off the phone. Your job isn't to catch them out or argue them off a position — there is no position yet. It's to be interesting enough, fast enough, that the reflex doesn't finish closing before you've said something worth hearing.