The only four numbers that matter

Every AI receptionist vendor has an ROI calculator, and every one of them is rigged in the same direction. So let's do this differently: here is the bare formula, where to find each input in your own systems, and the honest list of ways this math gets fudged. Bring your skepticism.

The four inputs:

  1. Missed calls per week. Not estimated — counted. Your carrier portal, VoIP dashboard, or Google Business Profile call history logs every missed and abandoned call. Count after-hours calls and rings-no-answer separately; you'll want both.
  2. Booking rate. Of the calls you do answer, what share become an appointment or job? Your front desk knows this number even if your software doesn't. For most service businesses it sits somewhere between 20% and 60% depending on how much price-shopping your industry attracts.
  3. Average ticket. Straight from your POS or practice management system. Use the median if a few whale jobs skew your average.
  4. Repeat factor. If a new customer typically comes back — a dental patient, an HVAC maintenance plan — a first booking is worth more than one ticket. Use a conservative multiplier or skip it entirely; the math should survive without it.

The break-even line

ARF's receptionist tier is $997 a month, flat, unlimited calls. So the break-even question is simply: how many recovered bookings pay for that?

Two worked examples — and to be clear, these are hypothetical illustrations, not client results:

Now run your own: missed calls per month × your booking rate = recoverable bookings. If that number is comfortably above your break-even line, the decision is arithmetic. If it's below, an AI receptionist is the wrong product for you right now — and you should know that before a sales call, not after.

What ROI calculations get wrong

Four fudges to watch for, in any vendor's math including ours:

Counting every missed call as a lost sale. Some missed callers ring back. Some were spam. Some were existing customers with a quick question. That's exactly why the formula multiplies by your booking rate instead of assuming 100% — and why you should count abandoned-to-voicemail calls separately from short hang-ups.

Ignoring the after-hours share. If 80% of your missed calls happen while your desk is staffed, your problem might be staffing or phone-tree friction, not coverage — and the cheaper fix might be operational. The audit tells you which problem you actually have.

Speed-to-answer hand-waving. Answering fast genuinely matters in lead-driven industries — but a vendor quoting a precise universal percentage for it is making it up. Directionally true, precisely unknowable. Treat speed as upside, not as a line item.

Double-counting repeat callers. The same customer missed three times is one lost booking, not three. Dedupe by number before you multiply.

Run your own 5-minute audit

The full version of this is its own post, but the short loop: export last month's call log, count after-hours calls and abandons, dedupe by caller, multiply by your booking rate and ticket. Ten minutes, one spreadsheet, and you'll know your exposure number to within a sane range.

Then — only if the number justifies it — test the other side of the equation. Call our demo line at 1-877-640-3761 and talk to Avery, the same AI that would be answering your phone. Judge the experience like a customer would. If she wouldn't keep your callers on the line, the rest of the math is moot.

The reversal

If you're losing thousands a month to missed calls or fumbled intake, and the only thing standing between you and fixing it is "I don't have time to build it" — the build is the problem, not the platform.

ARF's 30-day Pilot reverses the risk. We build the agent on your script, integrate it with your existing booking or case-management system, plug in CopyForge for content and SalesForge for outreach, layer in the agentic C-suite, and run the whole stack for 30 days.

If you don't see the operational impact inside the first month, you walk. No contract trap, no integration mess to unwind. Instead of "buy the platform and figure out the rest," it's "let ARF run for 30 days and only commit if the math is obvious." That's the reversal. The first 25 customers in the BIB case-study program get the entire stack at half price for the first three months.

Start the 30-day Pilot → See Pilot pricing

About the author — Rick Jenkins is the founder of AI Revenue Forge. ARF builds vertical-specific AI virtual receptionists for service businesses in HVAC, dental, medspa, real estate, home health, credit repair, and pawn shops. Headquartered in Charlotte, NC. Part of Jenkins Worldwide Enterprises.