One card per objection: the move, the words, and the number that backs it. Every stat is from their own CallRail log or Carolina's recorded demos. Aligned with the proposal's FAQ — nothing here contradicts what they've read.
About the AI
Our customers are old-school contractors — they'll hate talking to AI
The move: they already talk to a robot — the one that loses them
"Your callers already deal with a machine — the phone menu. And they hate it enough that 805 of them hung up on it without reaching anyone. Carolina removes the robot experience: no menu, no 'press 2', a voice that answers on the first ring and knows bollards from casters. Most callers don't have a philosophical reaction — they just notice somebody finally answered."
Backing: 805 menu hang-ups (15%) in their own log · demo calls are contractors-style callers, unedited.
What if she makes something up — a price, a stock count, a spec?
The move: her #1 rule is she never guesses — make accuracy YOUR strength
"That's the first rule she's built on: she never states a price, a stock level, or a delivery date she doesn't have. You heard it on the stock-check demo — asked how many are on the shelf, she says she can't see live counts and the team confirms the exact number same day. An unknown becomes a captured lead, never a guess. Frankly, she's more disciplined about that than most humans on a busy day."
Backing: play demo ⑥ (the shelf-count moment) · pricing always routes to the team · anti-fabrication is her hardest-enforced rule.
I've heard AI phone calls — they're terrible
The move: don't argue — play the recording
"Fair — most are. That's why we didn't bring a slide deck about AI, we brought seven recorded calls on your actual product lines. Pick any one of them. If it sounds like the AI calls you've heard, this is a short meeting."
Backing: the player on the proposal — ① the asphalt catch and ⑦ the angry-customer recovery are the two strongest.
Is she perfect? What happens when she gets something wrong?
The move: honesty beats bravado — and the process is the answer
"No — and anyone who tells you theirs is perfect is lying to you. Here's what's true: she never invents answers, every change we make is tested in simulation before it touches your line, every version is saved so a change can be rolled back in seconds, and the tuning never stops — every call she takes gets reviewed and she gets sharper. You're not buying a finished robot; you're buying a phone line that improves every month instead of staying a menu forever."
Backing: versioned config + instant rollback + simulation-tested changes (Implementation tab) · ongoing tuning included in the price.
About the money
$1,200 a month is a lot
The move: shrink it to $40/day, then anchor to their own quote value
"It's about $40 a day — and your own numbers say an average closed call is worth $291. She pays for herself if she saves four calls a month out of the 2,214 your current system lost. For comparison: a receptionist runs $38–55K a year, answers one call at a time, and goes home at five. Carolina answers every call at once, at 2am, on Christmas."
Backing: $291 avg closed/call · $1,093 avg quote · 41% lost — all from their CallRail log · no setup fee.
We need to think about it / not a priority right now
The move: price the delay in their own numbers
"Totally fine — just price the wait with your own data: about 92 callers a month don't reach a person. Your answered calls average $291 in closed business each. Even if the lost ones were worth a fraction of that, the leak costs more per month than Carolina does — and it's been running for two years. If the decision needs time, start where there's zero risk: turn her on nights-and-weekends only. Daytime stays exactly as it is, and she catches the 600 calls a year that go to voicemail today."
Backing: 2,214 lost ÷ 24 months ≈ 92/month · $291 avg closed per answered call (their blended figure — don't invent a close rate for lost calls, let the comparison speak) · after-hours pilot = zero daytime risk.
Couldn't we just build this ourselves? We own the data
The move: agree — then price the two years
"You could — the platforms are public. What you'd be rebuilding is the two years of your own call data distilled into her product knowledge, the de-escalation behavior, the testing rig that checks every change before it goes live, and the months of tuning that got her to what you just heard. Meanwhile the 41% keeps leaking every week you're building. We already paid that cost — that's what the flat fee buys."
Backing: trained on 897 real Source 4 calls · 59K+ chars of behavioral rules · aligned with the proposal FAQ answer.
About operations
We already have a phone menu that routes calls
The move: the menu is the leak, not the fix
"The menu is where 805 of your callers gave up — 15% of everything that rang. A menu screens callers out; Carolina routes the same departments by just… asking, like a person. Same routing outcome, none of the hang-ups."
Backing: 805 menu hang-ups · full department routing is included (sales, logistics, support, billing).
My team answers the phone fine during the day
The move: don't fight the team — take the calls nobody answers
"Keep it that way. Start Carolina where your team isn't: after hours and overflow. 23% of your calls come in outside business hours — the biggest share before 8am, contractors calling before they're on site — and today every one hits voicemail. Ring-through rules mean your people take first ring 8-to-5 and Carolina catches everything else. If she earns more, you expand her; if not, she's still catching 600 calls a year you currently lose."
Backing: 23% after-hours · ~600/yr to voicemail · ring-through/overflow is a standard Phase 2 option.
Integration sounds like a six-month IT project
The move: day one is a call-forward, everything else is optional
"Day one is your carrier forwarding the number — your PBX, extensions, everything stays untouched, and leads hit your inbox the second a call ends. CRM push and live inventory lookups are Phase 2, after she's proven herself, and they're read-only connections your IT signs off on. Nothing about going live requires a project plan."
Backing: Phase 2 section on the proposal's Implementation tab · go-live in days, not months.
What if it goes down mid-day?
The move: compare to the status quo, then show the net
"If Carolina's ever unavailable, calls fail over cleanly to your team or voicemail — exactly where 100% of your calls go today. The platform is monitored around the clock and runs on SOC 2 audited infrastructure. Worst case is your current system; every other case is better."
Backing: failover + monitoring on the Implementation tab · SOC 2 Type II / HIPAA / GDPR infrastructure, independently audited.
And if we want out?
The move: make leaving trivially easy — it closes deals
"No contract, no lock-in, no cancellation process. The forwarding reverts in minutes and you're back to exactly what you have today. We keep you by being worth $40 a day, not by a clause."
Backing: month-to-month · rollback instant · stated verbatim in the proposal.