You'll hear the same seven objections on repeat. They feel like seven different conversations, but they're really one question wearing seven masks: "Is this safe and worth it for me, specifically?" Here's each objection, what it actually means, and a tested response. Memorize these and the call stops surprising you.
1. "What if it makes something up?" (accuracy)
Means: "Who's liable when it's wrong in front of my customer?" Response: "It only speaks from what you give it — your services, hours, FAQs. Out of scope, it confirms, defers, or hands off to a human. Want to try to break it right now?" Then demo the graceful failure. (Full breakdown in the hallucination doc.)
2. "It's too expensive." (price)
Means: "I don't yet see the return." Price is only an objection in the absence of value. Response: Go back to the missed-call math. "You said you miss maybe 15 calls a week after hours, and a job's worth ~$400. That's a few thousand a month walking out the door. This is a fraction of one recovered job." Never discount first — re-anchor on the cost of doing nothing.
3. "We already tried a chatbot / IVR and it sucked." (skepticism)
Means: "I've been burned and I don't believe the demo." This is actually a good sign — they have budget and intent, just scar tissue. Response: "Yeah, the old phone trees and bolt-on bots were rough. The difference is this holds a real conversation and hands off the second it's unsure — let me show you a call and you tell me if it sounds like the thing you tried." Then let the demo disprove the prior. Acknowledge the burn; don't argue it.
4. "I need to think about it." (stall)
Means: there's an unspoken objection, or no urgency, or no authority. Response: "Totally fair — usually 'think about it' means one of three things: it's a money question, a 'will it actually work for us' question, or you're not the only decision-maker. Which is closest?" Smoke out the real objection instead of letting the deal drift into the follow-up graveyard.
5. "Will it work for my specific business?" (fit doubt)
Means: "Your generic demo doesn't prove it handles my calls." Response: Don't reassure — show. "Let's set it up to handle your three most common call types. Pull up the last few voicemails you got and we'll run those exact scenarios." Specificity beats promises.
6. "What about my customers' data / compliance?" (risk, regulated verticals)
Means: "Could this get me sued or fined?" (Real in legal, healthcare, finance.) Response: Name the guardrails plainly — data handling, scoping, hand-off, and any relevant compliance posture. If you don't know the answer for their regulation, say so and follow up. Bluffing compliance is how you lose the deal and the referral.
7. "Can't I just build this myself?" (DIY)
Means: "Why pay you?" Response: "You absolutely could — Vapi and Bland are right there. The question is whether you want to spend your nights tuning endpointing and escalation logic or running your business. We've already made the mistakes; you get the result in a week." Sell the time and the avoided mistakes, not the secret sauce.
The pattern underneath
Notice the through-line: almost every response either (a) re-anchors on the cost of inaction, or (b) replaces a promise with a live demonstration. Those are your two universal tools. When a new objection shows up that isn't on this list, reach for one of those two — make doing nothing feel expensive, or show the thing working — and you'll handle 90% of what any call throws at you.
Print this. Read it before every call until it's reflex. The deals aren't lost to the objections; they're lost to being surprised by them.