We run one. It answers inbound calls, works out what the caller wants, and books meetings into the calendar without anyone touching it. Here is an honest account of where that works and where it does not.
Why this is usually the best first deployment
For a small firm, a missed call is not a small thing. In advisory work the first conversation is the entire funnel — someone who reaches voicemail frequently does not call back, and you never learn they existed. The same is true for a home services business at four in the afternoon with every technician on a job.
The economics are unusually clear. You do not need an efficiency argument or a productivity study. You need to know how many calls currently go unanswered.
That number is almost always higher than owners think, because the ones you never hear about are invisible by definition.
What it does well
Never misses. No lunch break, no simultaneous calls problem, no five-thirty on a Friday.
Consistent qualification. It asks the same questions every time. Humans do not, particularly when busy.
Booking directly. Reading real availability and writing a real appointment removes the callback loop that loses people.
Structured records. Every call produces a consistent note. For a business where lead source matters, that data is worth as much as the bookings.
Where it fails
Genuine complexity. A caller with an unusual situation that does not fit the expected shapes gets handled worse than a human would handle it. Not catastrophically — but noticeably.
Emotional situations. A distressed or angry caller needs a person. Any system that cannot recognise this and hand over is badly designed.
Accents, noise, poor lines. Better than it was, still imperfect. Your callers are often outdoors, in vehicles, or on a forecourt.
Anything requiring memory of a relationship. A caller who has spoken to you three times does not want to start from scratch, and most deployments do not carry that context.
The design decisions that matter
Make handover easy and obvious. The system should offer a person early rather than defending its own competence. Systems that trap callers in loops do more damage than voicemail.
Say what it is. We do not pretend it is a person. Callers are generally fine with it and would not be fine with discovering they had been misled.
Restrict what it can do. Ours books meetings. It cannot quote, commit to anything, or discuss a live transaction.
Review the transcripts weekly. This is the part that gets dropped after a month, and it is the part that catches the failures.
The honest verdict
For a business losing calls, this pays back faster than anything else we run — the value is in calls that would otherwise have vanished, not in efficiency.
For a business whose calls are complex, relationship-heavy or emotionally charged, it is a poor first choice. Use it for overflow and out-of-hours instead, where the alternative is not a person but nothing at all.
More on our other systems in What Running AI Agents Inside an Advisory Firm Actually Taught Us.