The five objections you'll hear (and how to handle them)

Key takeaway: Every objection is the same shape — "I'm afraid the change will cost me." Your job isn't to argue. Your job is to remove the fear.

"It's too expensive"

The instinct: justify the price. The right move: reframe the cost.

"OK fair — what number would feel right? £30 a month?"

Them: "Maybe £30."

"Cool. So at £30 a month over a year, that's £360. You told me one missed roof job is £15k. So we're arguing about £360 vs £15k. The price isn't really the question — the question is whether it works. Want to test it?"

If they're a genuine "I literally don't have the cash" — get them on the £49 starter and tell them to upgrade later. Don't burn the prospect.

"I already have a receptionist"

"That's brilliant — most of our customers do. We don't replace receptionists. We answer the calls when they're busy. Or after hours. Or when ten calls hit at once. Last week we answered six simultaneous calls for a roofer in Cardiff during a storm — his receptionist could only take one. The other five would've gone to voicemail."

Then pivot:

"What time does she finish? 5pm? OK so any call coming in at 6pm tonight goes to voicemail. That's where Foan picks up."

"AI will scare my customers"

"Totally fair. So we always tell callers it's AI if they ask. We never lie. What's interesting — most callers don't ask, because the voice is good enough that they don't notice. But the few that ask, we say 'yes, I'm an AI assistant for [business name].' Most just laugh and carry on. We had a kitchen remodeller worried about this — she ran it for a month and didn't get a single complaint."

Then offer:

"You can always listen to your call recordings — every call is logged with the transcript. If anyone's spooked, you'd know within an hour."

"I'll think about it"

This is a soft no. Don't push.

"Of course — what specifically do you want to think about? If it's the price, I get it. If it's whether the demo was real, you can run it again any time. If you want me to come back next week, I'll come back next week. What helps?"

The goal is to surface the real objection. Sometimes it's "I want to ask my partner." Sometimes "I don't trust this." Sometimes "I'm in the middle of something." You can only solve real objections, not vague ones.

If they genuinely just need time:

"No worries. I'll text you the link. Run the demo when you've got a quiet five minutes. If you want me to walk you through setup tomorrow morning, I'm around. Sound good?"

Then actually text them.

"Just send me an email"

"Done. What's the best email? [Get it.] Sending right now. Reading the email takes a minute, and the demo at the top takes thirty seconds. Could you read it tonight? I'll follow up tomorrow morning."

You're getting them to commit to a time. "Sending the email" without a deadline is dead. "I'll follow up tomorrow morning" is a soft commitment.

The email itself:

Subject: 30-second demo for [Business name]

Hey [Name],

Thanks for the chat. The demo on your own site:

foan.me/r/[your-code]/demo/[their-domain.com]

You'll talk to a Foan AI receptionist trained on your website. Run it
once. If it doesn't make you grin, ignore me.

If you want it on your number:

foan.me/r/[your-code]?ref=[your-code]

Speak tomorrow.

[Your name]

The objection-behind-the-objection

Most "I'll think about it" / "send me an email" objections are really one of:

• "I don't trust you yet." — Solved by running the demo on their actual site, in front of them.
• "I don't trust the product yet." — Solved by emailing them three case studies. We'll provide these in your dashboard.
• "I don't have authority." — Ask: "Who else needs to be in on this?"

The script doesn't change. The demo does the work. Your job is to make the demo happen.

What never works

• Cutting the price unilaterally. Don't say "I'll get you 20% off." We don't.
• Lying about features. We can't transfer to a human (yet). Don't say we can.
• Promising a custom integration. The platform is the platform.
• Calling repeatedly. Two follow-ups max, then move on.