Objection Handling Script: 12 Objections With Phone and Email Replies

Phone: "Fair enough, you don't know what I do yet. One question, and if
it's not relevant I'll let you go: how are you handling [problem] today?"

Email: "Understood, thanks for replying. So I don't waste your time later:
is [problem] not an issue for you, or just not a priority right now?"

Phone: "Sure. I'd rather send one useful thing than a brochure.
Is [specific topic] the right area, or is something else more pressing?"

Email (the one you send): "As promised on the phone: [one specific idea].
If it's relevant, would [day] work for 15 minutes?"

Phone: "Happy to. Is that 'busy this week' or 'not a priority this year'?
I'll put it in the calendar either way."

Email: "Thanks, [Name]. I'll follow up on [date]. If [problem] becomes
urgent before then, just reply here."

Phone: "Fair question. [Honest source: it's on your company site / from a
data provider]. I called because [specific reason]. Would you rather
I take you off my list, or is [topic] worth a minute?"

Email: "Sorry if the call was unexpected. I found you via [source] and
reached out because [reason]. Happy to remove you from my list, just say so."

Objection Handling for the Status Quo

Status-quo objections mean "changing sounds like work", so don't attack what they have. Help them see what staying put costs. A battle card per competitor keeps these replies sharp and accurate.

5. "We already use [Competitor]."

Phone: "Good, then you already know the problem is worth solving.
How's it working for [specific use case], where [gap] tends to show up?"

Email: "Makes sense. Teams on [Competitor] usually come to us for
[one gap], not to replace everything. Is [gap] something you run into?"

6. "We handle it in-house."

Phone: "That's common. How much of the team's week goes into it?
I ask because [what in-house usually costs: maintenance, a key person]."

Email: "Understood. If it's ever useful, I can share how teams like yours
compare the in-house cost against a tool. No pressure either way."

7. "It's not a priority right now."

Phone: "Totally fair. What is the priority this quarter? Sometimes
[problem] sits underneath it, and sometimes it really doesn't."

Email: "Thanks for being straight. When do you plan next quarter?
I'll check in then with something relevant to it."

8. "We're happy with how things are."

Phone: "Good to hear. What's working best? I ask because teams that are
happy with [process] often still hit [specific friction]. Is that true for you?"

Email: "Glad it's working. I'll leave you one idea that teams like yours
have found useful: [idea]. If that ever changes, I'm here."

Objections About Money and Authority

On a cold call, money and authority objections are usually a polite exit. Treat them as questions about value and process, not as walls.

9. "We don't have budget."

Phone: "Understood. Most teams don't budget for something they haven't
seen yet. If this solved [problem], where would the money normally come from?"

Email: "Makes sense. Budgets usually follow problems that cost money.
Is [problem] costing enough to be worth a look at planning time?"

10. "It's too expensive."

Phone: "Fair. Too expensive compared to what: another option,
or what the problem costs you today?"

Email: "Thanks for being direct. What are you comparing against?
If it's the cost of [problem], I can help you size that."

11. "I'm not the right person."

Phone: "Thanks, that helps. Is it [guess: your ops lead] or someone else?
And from where you sit, is [problem] even worth their time?"

Email: "Thanks for letting me know. Who would be best for [area]?
I'll only mention you if you're comfortable with that."

12. "I need to talk to my team."

Phone: "Of course. What will they want to know? I can send something
that answers it, so you're not carrying the pitch yourself."

Email: "Makes sense. Here's a one-page summary written for your team:
[link]. Want me to join for 15 minutes to answer questions directly?"

Practicing Your Objection Handling Script

Replies fail when you say them for the first time on a live call. Practice turns them into instinct.

1. Pick your top three. Track which objections you hear most for a week, and start there.
2. Say them out loud. Practice with a teammate playing the prospect, then swap roles.
3. Record and listen. Many reps sound defensive at first. Slow down and soften the acknowledge.
4. Know your exit. After two clear no's, thank them and ask when to check back. Our cold calling tips cover delivery in more detail.

Preparing Objection Replies for Each Account

Generic replies beat no replies. Account-specific ones are better still: "Most teams say that until volume spikes" lands harder when you know their volume just did.

Pull the reframe from research. A hire, a launch or a competitor in their stack gives you a reframe that's about them. The same research feeds your discovery call questions.

Plan the email version too. When a call ends in "send me something", give each follow-up a purpose; the follow-up email generator guide shows how.

The Edithly cold call script generator writes objection replies for each account using acknowledge, respond and ask, alongside the opener, questions, voicemail and a do-not-say list.