Ten questions to ask before choosing an AI receptionist

1–2. When does it answer, and can you keep your number?

Ask whether the receptionist covers every call, selected hours, overflow after a ring delay, or a customer-chosen combination. Get the schedule and ring behavior in writing.

Then confirm whether callers keep using the existing number. If the provider uses forwarding, ask who configures it, which carrier features are required, whether the business line and AI ring simultaneously, and how to turn forwarding off.

3–4. What does the caller hear, and what is retained?

Require a real sample of the greeting and voice. Confirm whether each location or line can use its own business name, greeting, hours, and instructions. Ask whether callers are told they are speaking with AI and whether that disclosure can be configured to match legal and business requirements.

Separate transcription from recording. Ask what is retained, who can access it, how long it remains available, and how sensitive information is handled.

5–7. How does it qualify, transfer, and handle urgent calls?

A provider should show how qualification questions change by business, service, and situation. Avoid a generic script that collects many details but cannot determine a useful next step.

For transfers, ask whether the system can call one person or several, how the recipient knows why the call is arriving, and what happens if the first person declines, reaches voicemail, or never answers. Urgent rules should be explicit, tested, and limited: an AI receptionist is not emergency dispatch.

8–10. Which appointment, language, and pricing promises are real today?

Ask the provider to name the booking tools that work in production—not integrations on a future roadmap. Test booking, rescheduling, cancellation, conflicting availability, and the fallback when a calendar cannot be reached.

For languages, distinguish the administrative interface from the languages the receptionist can reliably understand and speak. For pricing, request the included calls or minutes, overage unit and price, setup fees, minimum term, cancellation terms, and any carrier or integration fees.

Run a ten-scenario launch test

Do not approve the workflow from a polished demo alone. Call the real forwarded number and record the expected and observed result for each scenario.

1. Routine call during staffed hours.
2. Routine call after hours.
3. Caller outside the service area.
4. Caller uses configured urgent language.
5. Caller asks for a human immediately.
6. Primary escalation contact answers.
7. Nobody answers the escalation.
8. Caller requests, changes, and cancels an appointment.
9. Calendar or booking connection is unavailable.
10. Caller asks an unsupported or sensitive question.

A passing result is not “the conversation sounded natural.” It is that the caller reached the approved next step and the team received an accurate, usable record of what happened.