Rémi KokabiNovember 4, 202610 min read
Sales objection handling for cold calls and email replies
“Just send me an email.” You hear it eight seconds into a cold call, before you’ve even explained why you’re calling. Open your inbox the next morning and the same line is waiting for you, this time as a one-line reply to your outreach. Same objection, different channel, and the right answer changes depending on where it lands.
That’s what this article covers. I’ll walk you through sales objection handling for both cold calls and written replies, with a simple framework you can use on every objection you hear. You’ll get sample responses for the brush-offs that aren’t really objections, the real ones that need a different approach, and a cheat sheet to keep next to your phone or inbox.
I’ll also get into something most objection-handling advice skips: how to prevent objections before they happen. A warm call after a LinkedIn connection accepts converts at 21.4%, compared to 9.6% for a cold first-touch call. That’s not a script problem. That’s a timing and context problem, and it’s fixable before you ever pick up the phone.
By the end, you’ll know how to tell a reflex from a real concern, how to respond without sounding scripted, and how to build a system with your team so every objection makes the next call easier.
What sales objection handling means in outbound
Sales objection handling is the skill of answering a prospect’s concern so the conversation keeps moving toward a next step. In outbound, that means doing it with someone who never asked to hear from you.
That distinction matters. When a lead books an inbound demo, they already have intent. They chose to show up. Your job is to remove friction. But when you’re cold calling or sending a cold email, the prospect owes you nothing. They were mid-task when you interrupted, and their default is to end the interruption fast.
Outbound objection handling starts from a deficit of trust. Every response you give has to earn the next few seconds of attention.
Brush-offs versus real objections
Most of what reps hear at the start of a cold call is a brush-off. “Not interested.” “Send me an email.” “Call me later.” These are reflexes. The prospect wants to get back to what they were doing, and they’ve learned that these phrases end most sales calls.
Real objections are different. Budget, timing, an existing tool, needing approval from someone else. These are reasons, and they come with specifics.
Here’s a simple test: if the prospect can name what they would need to change their mind, it’s a real objection. “We just renewed our contract through Q2” is a reason. “I’m not interested” from someone who hasn’t heard what you do yet is a reflex. Your response should match which one you’re dealing with.
The four moves behind every good answer
Every objection response in this article follows the same four moves. Memorize the pattern, then adapt the words to whatever you hear.
Pause and let them finish
Do not talk over the prospect. When someone says “we already use a tool for this,” your instinct is to jump in before they hang up. Fight it. A beat of silence signals that you actually heard them, and it keeps the conversation from turning into a debate.
Acknowledge without agreeing
Restate the concern in their words. You’re showing you understood, without conceding the deal is dead.
“Totally fair, you weren’t expecting this call.”
“Makes sense, switching tools is a big lift if what you have works.”
Ask one question
Turn the objection into information. One question, tied to what they just said.
Timing: “When does your current contract come up for review?”
Budget: “Is this a budget constraint for this quarter, or across the board?”
Current tool: “What’s the one thing you’d change about your current setup if you could?”
Answer and propose one next step
Give one relevant proof point that connects to their answer. Then make a small ask: a 15-minute call next week, permission to send one resource, or a specific later date. The smaller the ask, the more likely they say yes.
How to handle objections on a cold call
Cold call objections hit fast. You have seconds to respond before the prospect hangs up. The five below cover what reps hear most often. Each one includes what it usually means, a sample response built on the four moves, and when to walk away. If you need a full talk track, pair these with a tested cold call script. And if the objection comes from an assistant or office manager before you reach the decision-maker, start with how to get past the gatekeeper.
I’m not interested
This is almost always a reflex. The prospect doesn’t know what you’re offering yet, so “not interested” means “please stop talking.”
Sample response: “Totally fair, I caught you out of the blue. Would you be open to one quick question? I noticed your team just posted new AE roles, and I’m curious how you’re thinking about ramping them.” If they say no again, thank them and hang up. Repeated brush-offs are a clear signal.
Just send me an email
Agree. Then make the email worth sending.
Sample response: “Happy to. So it’s actually useful and not just another sales email, what’s the one thing that would make it worth opening? And let me confirm, is your work email the best address?” Now you have a topic and a verified email. Send a short, relevant message within the hour. For the structure of that message, see how to write a follow-up email after a cold call.
We already use a tool for this
This is a real objection. They have context, and they’re telling you they’ve already solved the problem.
Sample response: “Got it. What do you like most about your current setup? And if you could change one thing about it, what would that be?” Never attack the competitor. If their answer reveals a gap you can fill, mention it briefly and offer to send a short comparison. If they’re genuinely happy, move on.
Now is not a good time
Take it at face value and lock in a specific time.
Sample response: “No problem. Would Thursday at 10:15 work better, or is next week easier?” A vague “call me back sometime” is a brush-off. A confirmed slot on the calendar is a real next step. If they won’t commit to any time, let it go.
How did you get my number
Answer honestly. One sentence.
Sample response: “Your number is listed in a business contact database we use for outreach. If you’d prefer I remove it, I’m happy to do that right now.” If they say yes, remove it immediately. No second pitch. Respecting this request is the only move that protects your reputation.
How to handle objections in email and LinkedIn replies
Written objections give you one advantage: time to think. But you lose tone, pacing, and the ability to read hesitation. Keep replies short. Two to three sentences. Never re-pitch.
Not a priority this quarter
Ask when it would be, and commit to following up at that date.
Reply: “Understood. When would this move up the list? Happy to circle back in Q3 with a quick update on what’s changed.” Then actually set the reminder and follow up. Most reps say they will and don’t.
Too expensive
Don’t defend the price. Ask what they’re comparing against.
Reply: “Appreciate you flagging that. What are you comparing against, a competing tool or handling this in-house? I’d be curious whether the cost of your current process factors in.” Let them do the math. You don’t need to invent ROI figures.
You should talk to my colleague
This is a gift. Someone just gave you a warm path to the right person.
Reply: “Thanks for pointing me in the right direction. Would you be open to making a quick intro, or can I mention your name when I reach out?” Then contact the colleague while the context is fresh.
Please remove me
Remove them. Immediately. Confirm it in your reply.
Reply: “Done, you’ve been removed. Sorry for the interruption.” No rebuttal, no “before you go.” Every unsubscribe request you honor protects your sender reputation and keeps your domain out of spam folders. One forced reply can cost you deliverability across your entire sending infrastructure.
Objection cheat sheet
Objection | What it often means | First response | Next step |
|---|---|---|---|
Not interested | Reflex to end the interruption | “Fair enough. Would you be open to one quick question?” | Ask one question tied to a trigger you researched |
Send me an email | Wants off the phone | “Happy to. What should the email cover so it’s relevant?” | Confirm the address and send within the hour |
Call me later | Polite brush-off | “Sure. Would Thursday at 10:15 work?” | Lock a specific date and time on the call |
Already using a tool | They solved the problem already | “What do you like about it? What would you change?” | If there’s a gap, offer a short comparison |
No budget | Real constraint or a deflection | “Is that for this quarter or longer term?” | Offer to reconnect when budget opens |
Need to check with my boss | They lack authority or want cover | “Makes sense. What would help you make the case internally?” | Offer a one-pager or short brief they can forward |
Too busy | Bad timing | “Totally get it. Can I send one resource and follow up next week?” | Send something short and useful, then follow up |
Not the right person | Wrong contact | “Who on your team handles this?” | Ask for a name and permission to mention theirs |
Prevent objections before they happen
Many objections come from bad timing and zero context. The prospect has never seen your name, doesn’t know why you’re calling, and defaults to a brush-off.
One way to change that: add a LinkedIn connection request before your call step. A warm call after a LinkedIn accept connects at 21.4% versus 9.6% for a cold first-touch call (lemlist internal data). When someone has already seen your face and headline, the first few seconds of the call feel different. You get fewer “who is this?” objections and more actual conversations.
Data quality matters too. Verified phone numbers connect around 20%, while scraped lists connect around 10% (lemlist internal data). Calling the wrong person guarantees an objection you can’t overcome.
Timing calls around intent signals (a new hire, a funding round, a job change) gives you a reason to call that the prospect can verify. “I saw you just raised a Series B” is a better opener than “I’m reaching out to companies like yours.” The objection rate drops when the prospect can see why you called them specifically.
Build an objection library with your team
Individual reps get better at objection handling through repetition. Teams get better through shared data.
Start by logging every objection by type and channel. Use call statuses after each dial and reply tags in your inbox. At the end of each month, pull the most frequent objections and review the responses that worked. Update your scripts based on what you find.
Then compare connect and conversion rates by script version. The average call connect rate is 13.8%, with a median campaign at 9.1% and the top 10% of campaigns hitting 34.1% or higher (lemlist internal data). Every connected call is a chance to test your objection responses, so preparation compounds. For the full breakdown on tracking these numbers, see how to set up call tracking and analytics.
How to run objection handling in lemlist
Here’s how the workflow looks end to end.
Call from lemlist using in-app calling or the parallel dialer. After each call, log the outcome with call statuses. These feed your objection library over time.
Handle email and LinkedIn replies in the unified inbox. Every channel, every sender, one view.
Mark leads as Interested or Not interested. AI auto-marking from replies is available if you want it. The campaign stops on reply, so prospects aren’t getting a later step while you’re mid-conversation.
Add a LinkedIn invite step before the call step in your sequence. Set a condition on accepted invites so you only call warm. That’s where the 21.4% connect rate comes from.
Use the team unsubscribe list for removal requests. It covers emails, domains, phone numbers, and LinkedIn URLs, so when someone says “please remove me,” you can honor it across every channel in one action.
Final takeaway
Objections are part of outbound. The reps who handle them well are the ones who pause, ask a question, and propose a small next step instead of arguing. Build a system around it: log what you hear, review what works, and set up your sequences so fewer objections happen in the first place.