AI Receptionist Checklist

Most launch problems aren’t caused by the system getting something wrong — they’re caused by nobody testing the paths customers actually use before going live.

Business information

Company name and approved greeting confirmed. Business hours confirmed. Service areas documented. Services offered documented. Services not offered documented.

Lead intake

New sales path defined. Existing customer path defined. Commercial and residential paths defined if different. Required customer information listed. Qualification questions approved. Disqualification rules approved.

Knowledge boundaries

Approved pricing language documented. Financing language documented. Warranty language documented. Technical questions requiring human review listed. Unknown answer behavior tested.

Phone handling

Main number routing tested. Overflow behavior tested. After hours behavior tested. Transfers tested. Failed transfers tested.

Scheduling

Correct calendars connected. Appointment duration verified. Availability rules verified. Service area checked before booking. Rescheduling tested. Confirmation messages reviewed.

Notifications and records

Qualified lead alerts tested. Urgent alerts tested. CRM or database record creation tested. Conversation summaries reviewed.

Launch quality

At least twenty scenarios completed. Employees know how to report an error. Daily review scheduled for launch week. Owner assigned for ongoing updates.

A system that answers correctly once has been demonstrated. A system that’s been tested against its failure paths — wrong numbers, failed transfers, questions it doesn’t know — has been launched.