Twenty-minute operator check

Would you put this AI receptionist on the main number?

Mark only what you observed in a real call. The runner produces a local readiness summary and keeps unverified vendor claims out of the result.

NZ boundary: ask every vendor to prove number availability, consent handling, data location, emergency escalation, integrations, and inbound pricing. This tool does not assume those details.

Observed call controls

0 of 7 checked

Tick a control only after you observe it Intent captured. The summary records why the caller rang, without inventing missing details. Contact details confirmed. Names, phone numbers, and spelling are read back when uncertainty matters. Human escalation works. The caller can reach a person or leave a clear callback request. Failure path is useful. Silence, interruption, and an unknown answer produce a recoverable result. Handoff evidence arrives. The business receives a timestamped call record and an actionable summary. Booking is confirmed. A real slot is written and the caller receives an unambiguous confirmation. Vendor facts verified. NZ number, privacy, pricing, support, and integration answers are documented.

Readiness result

Not ready

Plain-language interpretation

Run the checklist during a live test call. Seven observed controls are required for this narrow acceptance result.

Unverified controls

All seven controls still need evidence.

Use a real edge case

Ask for an unavailable time, interrupt mid-sentence, correct a phone number, and request a human. A perfect happy path proves very little.

Keep raw evidence

Save the call timestamp, transcript or recording permission, booking record, notification, and escalation result. Grade the same inputs across vendors.

Separate product facts

Outbound usage pricing does not prove inbound pricing. Lead-source support does not prove a local NZ phone number or a specific calendar integration.