Blog / AI answering
AI receptionist for small business: what to test before forwarding calls
An AI receptionist should answer from approved business information, disclose that it is AI, respect recording choices, and confirm an appointment only after the booking system accepts it. Test those behaviors on a real call before forwarding customer traffic.
Start with the calls you actually receive
List five common questions: services offered, service area, opening hours, price approach, and appointment availability. Then list the questions that require judgment. A service business may give a fixed price for a defined job, a range for variable work, and no price until an inspection for an unfamiliar problem. The assistant needs to distinguish these cases.
Use your own approved answers as the test reference. A fluent answer is not evidence that the information is correct. If a caller asks about work you do not offer, the assistant should explain the limit rather than add a service to its answer.
Make AI identification and recording choices audible
The caller should hear which business they reached and that they are speaking with an AI assistant. If the call will be recorded or retained as a transcript for owner review, the assistant should ask permission before that recording or retention begins. A notice alone does not demonstrate an affirmative answer.
Test yes, no, silence, an unclear response, and a later withdrawal. Inspect the actual provider records as well as the conversation. If the platform cannot provide a verified non-recorded alternative, it should explain the limitation and give a human contact option. Do not describe a consent script as a legal guarantee for every jurisdiction.
Check answers and booking results separately
Ask a question whose answer is deliberately missing. The correct result is an honest follow-up request, not a confident guess. Next, request a slot that is already occupied. The assistant must recheck availability and offer another option, rather than treating its first suggestion as a reservation.
Compare the calendar entry with the spoken details: customer name, callback number, service, address, date, timezone, and arrival window. A booking is confirmed only when the server returns a successful result. A tool timeout should leave the status uncertain until reconciled, not create a second appointment automatically.
Test the handoff before relying on it
Try an urgent request after hours with the owner unavailable. The assistant should follow an approved escalation path, state when no technician has accepted, and avoid promising an arrival time. Immediate danger needs emergency services; a business answering agent should not imply that it provides emergency response.
Also test a wrong number, unsupported language, poor audio, and a caller asking for a person. Give the owner a short review queue of unresolved questions, with access restricted to their business. Review failures before expanding the routing.
Where Zephaux stands today
Zephaux currently provides a configuration workspace and an illustrative Test Lab. Live AI call answering remains in development. The Test Lab can help explore scenarios, but does not prove phone routing, consent handling, or a real appointment. Check the Trust Hub before treating any planned capability as available.