Objection handling – 12 common objections with answers
“Not interested,” “too expensive,” “we already use a tool” – most objections repeat. This collection gives you three answer variants per objection: short for the call, calm for email, casual for LinkedIn. The goal isn't to “win” the objection but to secure the next small step.
12 templates in this collection
Copy them all or save as Markdown.
1. “Not interested”
The classic. Often a reflex, not a real no. Acknowledge first, then ask a clarifying question.
Understood. Quick question: is {{topic}} simply not relevant for you, or just not a priority right now? Depending on that, a short chat now or in four weeks makes more sense.
Hi {{contact.firstname}}, thanks for the quick reply. So I don't keep emailing you unnecessarily: is {{topic}} simply not relevant at {{company.name}} – or just not a priority right now? If the latter, I'll reach out again in {{timeframe}}. Best, {{owner.firstname}}
All good, {{contact.firstname}}. Quick check: is {{topic}} fully off the table on your end, or just not top of the list right now?
First rejection = clarifying question. Second clear rejection = end politely, don't push.
2. “We don't have a need”
I hear that often – usually because the topic seems internally covered. What teams typically only spot when they look closer is {{specific_pain}}. Worth a 15-minute look for you?
Hi {{contact.firstname}}, understood – {{topic}} sounds well-covered on your end. One thought to take with you: what comparable teams typically only notice on closer inspection is {{specific_pain}}. If that becomes a topic, just let me know. Best, {{owner.firstname}}
Understood, {{contact.firstname}}. One question: how do you currently handle {{sub_area}}? Asking because that's where many teams have the ugly gaps.
3. “We don't have budget right now”
Got it. So we don't drift into theory: is it about budget for this quarter or generally for {{year+1}}? For many, the call is most useful precisely while budget is being planned – not after.
Hi {{contact.firstname}}, thanks for being upfront. Two quick points: 1. With most customers, ROI hit within {{timeframe}}, so it was more a prioritization than a budget question. 2. If this becomes relevant for {{year+1}}, the conversation now usually pays off because it lands cleanly in planning. Want to lock in 15 minutes for that? Best, {{owner.firstname}}
Makes sense, {{contact.firstname}}. Question: are you in budget conversations for {{year+1}} right now? That's exactly the phase where a short chat tends to be most valuable.
“No budget” is often a timing issue. Move the meeting into the planning window instead of pitching now.
4. “We already have a tool / vendor for that”
Great, then the basics are in place. So I don't double-call you: which tool are you using? We tend to extend most setups rather than replace them – usually where {{gap}} shows up.
Hi {{contact.firstname}}, good to know {{topic}} is already in place. We typically come in where existing tools hit limits around {{gap_1}} or {{gap_2}}. If that's a point on your end – 15 minutes is enough to size it up. Best, {{owner.firstname}}
Nice, {{contact.firstname}}. Quick curiosity: which setup are you running for {{topic}}? We tend to complement most stacks specifically around {{gap}}.
5. “Send me an email”
Classic brush-off. Don't argue – secure the email and keep the next step open.
Happy to. So it doesn't disappear in your inbox: which address works best – and is it okay if I follow up briefly mid next week?As discussed – {{topic}} in 4 sentences Hi {{contact.firstname}}, as promised on the call – here it is in 4 sentences: 1. {{benefit_1}} 2. {{benefit_2}} 3. {{benefit_3}} 4. Reference: {{reference}} Does a 15-minute slot make sense? Proposal: {{date_1}} or {{date_2}}. Best, {{owner.firstname}}
Always lock in a concrete next step in the same breath. No meeting = no pressure, but keep a door open.
6. “I don't have time right now”
All good, not in detail right now. I just want to check whether the topic is even relevant for you. If yes, we lock 15 minutes – does {{date_1}} at 10:00 or {{date_2}} at 14:00 work better?
Hi {{contact.firstname}}, short and honest: you're busy. So nothing to read here, just a question: 15 minutes on {{date_1}} or {{date_2}} to clarify whether {{topic}} makes sense at {{company.name}} – yes or no? Best, {{owner.firstname}}
Understood, {{contact.firstname}}. Then just 1 question: is {{topic}} a “maybe in 4 weeks” – or a “not this year”? Both are fine, I'll work with it.
7. “I'm not the right person for this”
Thanks for the heads-up – who's most likely responsible for {{topic}} at {{company.name}}? And – if possible – could you connect me directly or share the extension?
Hi {{contact.firstname}}, thanks for the quick reply. Could you tell me who's most likely responsible for {{topic}} at {{company.name}}? I'll reach out there directly and take you off the list. Best, {{owner.firstname}}
Thanks, {{contact.firstname}}! Who typically owns {{topic}} on your end? Then I won't go through your desk.
No pitch, just secure routing. Whoever helps you forward, helps you twice.
8. “Are you an AI?” (for AI calls)
Yes, I'm the phone assistant for {{company.name}}. I'm calling on behalf of {{owner.firstname}} and just want to clarify whether a 15-minute meeting on {{topic}} makes sense for you. If you'd rather speak with {{owner.firstname}} directly, I'm happy to forward you or have them reach out via email.
Don't dodge. Transparency builds more trust than any pitch.
9. “How does data protection / GDPR work for this?”
Fair question. Briefly: we process data inside the EU, a DPA is standard, and it's strictly about business contact data. I'll happily send you the exact framework in writing – in the meeting I can also walk through {{specific_requirement}}.
Quick note on data protection – {{company.name}} Hi {{contact.firstname}}, on your GDPR question: • Hosting: EU • DPA per Art. 28 GDPR is standard and signed before contract start • Data processed: B2B business contact data only • Subprocessors openly documented Happy to send detailed docs ahead of a call. Which address works? Best, {{owner.firstname}}
10. “Send me some materials”
Happy to – so it isn't generic, two quick questions: is it more about {{part_a}} or {{part_b}} for you? Then I'll send you exactly the two pages that matter for you and follow up briefly in {{timeframe}}.
As promised: {{topic}} – just the essentials Hi {{contact.firstname}}, attached – kept deliberately short – the points most likely relevant for {{company.name}}: • {{benefit_1}} • {{benefit_2}} • {{benefit_3}} {{resource_link}} Shall we do 15 minutes after a quick read? Proposal: {{date_1}} or {{date_2}}. Best, {{owner.firstname}}
Materials alone rarely convert. Always pair with a concrete next step.
11. “Call me back in {{timeframe}}”
Will do. So I'm not calling blindly: what would actually be different in {{timeframe}} that makes the meeting worthwhile? The better I understand that, the more targeted we can get.
As discussed – quick reminder on {{topic}} Hi {{contact.firstname}}, as discussed {{timeframe}} ago, briefly circling back on {{topic}}. Is now the better moment for 15 minutes? Proposal: {{date_1}} or {{date_2}}. Best, {{owner.firstname}}
Agreed callbacks are gold – but only when you back them with concrete value, not just “following up”.
12. “We're doing this in-house”
Makes sense, many teams start that way. From experience: who keeps it current long term – {{maintenance_1}}, {{maintenance_2}} and {{maintenance_3}}? That's where it tips for many. Worth a 15-minute comparison?
Hi {{contact.firstname}}, in-house solutions are often the fastest answer – and usually the most expensive over time. What typically catches up with teams after 6–12 months: • {{maintenance_1}} • {{maintenance_2}} • {{maintenance_3}} If that could become a point: 15 minutes of comparison often makes the difference. Best, {{owner.firstname}}
Interesting, {{contact.firstname}}. How are you covering {{maintenance_1}} and {{maintenance_2}} long term? That's exactly where many in-house setups stumble.
5 rules for clean objection handling
- Acknowledge first, then ask a clarifying question – never counter-argue immediately.
- Maximum one hook per response. Better short questions than long explanations.
- On the second clear rejection: smaller next step instead of repetition.
- On the third clear rejection or audibly annoyed: end politely.
- Document every objection in the CRM – patterns are only visible to those who see them.
How to implement this in HubSpot
Store the top objections as snippets in HubSpot (Sales tools → Snippets) using shortcuts like #obj-budget, #obj-tool, #obj-time. On calls and in emails, sales reps can insert the right answer in seconds. Outreach Master adds the objection responses automatically in AI calls and LinkedIn sequences, so multichannel steps stay consistent.
FAQ on objection handling
Further resources
HubSpot is already there. Now you need the clean outreach process.
Combine email, LinkedIn and AI calls into one documented workflow.
Book a demo