An AI receptionist is software that answers a business's calls, asks qualifying questions, books appointments, and hands off to a person when a conversation goes past its script. Disclosure: Mirastart builds them, so read this like a contractor's guide to hiring a contractor. The category is growing fast and its marketing has outrun plain explanations of where these systems fail.
First: three situations where you shouldn't buy one yet
- You don't know what your team actually says on the calls you're trying to automate. If nobody has listened to a week of real calls and written down the common questions, the answers, and where a human takes over, there's nothing yet to build the system around - and a vendor who doesn't ask for this first is guessing.
- Your call volume is genuinely low. A handful of calls a day at odd hours might be better solved by a cheaper answering service or a well-set-up voicemail-to-text flow than by standing up and paying for a full AI system.
- You can't commit to a real escalation path. An AI receptionist that has nowhere reliable to hand off an angry caller or a genuine emergency isn't saving you a problem - it's delaying one and making it worse.
What "AI receptionist" actually covers
The label gets used for very different products, and the differences matter more than any feature list. Some tools only transcribe a voicemail and text it to you. Some answer the call, ask a few qualifying questions, and text a lead notification. Fewer actually book directly into your calendar, confirm the appointment, and hand off live to a person when the conversation goes somewhere the script can't follow. Ask a vendor to demonstrate the exact call flow on your actual services, not a generic demo script - the gap between the pitch and the product usually shows up in the first minute.
Whether the caller is told
A caller should be told they're talking to a system, plainly, near the start of the call. It costs nothing, it's the position that ages well as disclosure rules for AI voice and chat interactions keep tightening across states, and it's simply what an honest business does. A system built to sound indistinguishable from a person on purpose is optimizing for the wrong thing - the goal is a caller who gets a fast, correct answer and knows exactly what they're talking to.
The ownership questions
| Ask | A good answer | A warning sign |
|---|---|---|
| Who owns the phone number? | You do, and it's portable if you leave | It's provisioned on our platform and doesn't transfer |
| Who owns the call data and transcripts? | You do, exportable on request | Vague, or 'we retain that' |
| Where does a booked appointment actually live? | Your calendar or CRM, as the source of truth | A dashboard only their platform can read |
| How is it priced? | A clear flat fee or a stated per-minute rate up front | Pricing revealed only after a sales call |
| What's the contract length and the exit? | Month-to-month, or a stated term with a stated penalty | Locked in for a year, discussed only after you're sold |
| What happens when the system doesn't understand the caller? | A defined, fast handoff to a person | It keeps guessing or the call just ends |
Recording and consent aren't optional reading
North Carolina is a one-party consent state for recording calls (N.C. Gen. Stat. § 15A-287) - your business, as a party to the call, can legally record without announcing it. That's the legal floor, not the bar to build to. A meaningful share of your callers are placed from, or live in, states that require every party's consent, and a business serving customers beyond North Carolina should default to a brief recording notice regardless of what the home state technically allows. Ask any vendor plainly how their system handles consent, and don't accept "that's on you" as the full answer - if they're building the call flow, they're part of that decision.
Pricing models, honestly
Three structures cover most of the market: a flat monthly fee regardless of volume, a per-minute or per-call rate that scales with usage, and a per-booked-appointment fee that ties cost to outcome. Each is defensible; each has a failure mode. Flat fees are predictable but can get thin if your call volume spikes seasonally. Per-minute pricing punishes exactly the busy month you were hoping the system would help you handle. Per-appointment pricing aligns incentives well but makes it worth asking what counts as a booking and whether cancellations get refunded. There's no universally right structure - there's only the one that matches how your call volume actually behaves, which is worth knowing before you're quoted a plan.
The integration question
An AI receptionist that doesn't talk to your calendar and your CRM turns into one more inbox someone has to check by hand, which defeats the point. Before signing, confirm the system writes directly into the tools you already run rather than into a separate dashboard nobody opens after week one. If it can't integrate cleanly, that should be flagged during scoping - not discovered a month in, after the team has quietly stopped trusting it.
Sources
- N.C. Gen. Stat. § 15A-287, Interception and disclosure of wire, oral, or electronic communications prohibited - North Carolina's one-party rule: interception is an offense only when done "without the consent of at least one party to the communication."
- California Penal Code § 632 - An all-party-consent state: recording a confidential communication requires the consent of all parties.
- California Business and Professions Code § 17941 (bot disclosure) - A state bot-disclosure statute - one example of the AI-interaction disclosure rules tightening across states.
- Federal Communications Commission, Declaratory Ruling FCC 24-17, CG Docket No. 23-362 (released February 8, 2024) - AI-generated voices count as "artificial" under the TCPA; any outbound calling the system does needs prior express consent.