What goes wrong with AI receptionists?

The technology is rarely the problem people expect it to be. Voices are good and transcription is decent on a clean line.

What fails is the setup around it, which is unglamorous and therefore skipped.

The exception is a genuinely bad phone line, which no configuration fixes.

A thin brief. An assistant told almost nothing hands over constantly, and the business concludes the technology does not work.

No obvious path to a person. A caller who asks for somebody and gets another question becomes an angry caller within two sentences.

A long greeting. Past ten seconds, people talk over it, and the call starts with both parties out of step.

Names and addresses transcribed wrong. Unusual words on a compressed line are where speech recognition is weakest, and reading details back is the defense.

A stale brief. Prices change, a service is dropped, and the assistant keeps confidently saying last year's answer.

Nobody reading transcripts. Every problem above is visible in week one and most go unnoticed for months because nobody looks.

Here's how one small failure spreads. Say you run a chiropractic office, and in March you stopped opening on Saturdays. You blocked Saturdays in the calendar but didn't touch the brief, which still said: "We're open Saturdays from 9 to 1."

For two months nothing looked wrong. The assistant never booked a Saturday, because the calendar had no slots. But when callers asked about weekend hours, it told them what the brief said. Fourteen people heard that you were open Saturdays, and three of them came by without an appointment and found a locked door.

You found out from a one-star review. Every one of those fourteen calls was sitting in your transcripts with the wrong sentence in plain view, and a search for "Saturday" would have caught it in March. A stale brief is dangerous because the calendar and the brief are separate sources, and updating one leaves the other confidently out of date.

The six failures on this page all live in the setup. A few others live in the plumbing around it, and they're worth a monthly check because they fail silently.

Forwarding can switch itself off. A new SIM, a phone upgrade, a plan change or a carrier migration can reset conditional forwarding without telling you, and your calls go back to ringing out. Carriers also sometimes re-enable voicemail after account changes, which then beats the forward to every call.

Calendar connections expire. Change your Google or Microsoft password, or tighten your security settings, and the link may quietly lapse, leaving the assistant unable to see availability or write bookings.

People change too. The on-call number may still belong to someone who left, or the transfer target may be away on leave.

The defense is a test call on the first of every month from a phone that isn't yours. Let it ring through, ask to book something, and ask for a person. In five minutes you've tested forwarding, the calendar and the transfer path, and found any break before a customer does.

Every call arrives as a transcript and a short summary, which makes five of those six failures visible rather than theoretical.

You write the brief and change it whenever you like, so the fix for most of them is typing rather than support tickets.

GreetKeeper is new and publishes no success-rate figures, because we have measured none and would rather describe the failure modes honestly.