Guide
An AI receptionist demo checklist you can actually fail
Use the same test calls for each provider and inspect the resulting records.
Bring a small, fictional business brief
Give the demonstrator your service area, opening hours, two job types, a dispatch fee policy and a test calendar. Use invented contact details. The goal is to see what happens when the conversation departs from a polished sales script.
Write down your non-negotiable rules before the demo. For example: the agent may offer an estimate appointment but may not quote repair costs. A provider should be able to show where that rule is configured and how you change it.
Run these six calls
| Test | What the caller does | Evidence to inspect |
|---|---|---|
| Routine request | Asks for an available estimate slot | Correct contact, job type, time zone and appointment status |
| Outside service area | Gives an excluded ZIP code | No appointment promised; explanation matches your policy |
| Correction | Changes address after initially providing it | Final record contains the corrected address, not two competing values |
| Existing customer | Wants to move an appointment | Identity and record handling follow your process; no duplicate job |
| Human handoff | Asks for a person who does not answer | Documented fallback and a visible task for follow-up |
| Integration failure | Vendor disables the test calendar connection | No false booking confirmation; retry or exception is visible |
Do not award points because an answer sounds confident. Mark each row pass, fail, or not demonstrated and retain the corresponding test record. An untested feature is not a pass.
Separate critical failures from preferences
Invented prices, false booking confirmations and lost escalation requests are launch blockers. A voice you find slightly formal is a preference. Mixing both into a five-star score hides the problems that matter most.
Ask the vendor to repeat a failed test after changing the configuration. Record what changed and whether the same change could affect another job type. If the fix depends on custom engineering, get an owner and delivery date before treating it as available.
Leave with a decision record
Save the plan quoted, included usage, six results, unresolved questions and the exact integration demonstrated. Assign an employee to own configuration updates. Use the pilot plan before routing real customers and the buyer guide to select a shortlist.
This scorecard is our proposed evaluation method, not the result of completed product tests. Print this page to use it during a demo.
Prepared by Contractor Software HQ. Documentation research and editorial guidance; not a hands-on product test. Prices and features change — verify on the vendor's site before you buy.