RECEPTIONIST TRIAL SHEET
Sayora | 6 September 2026
https://sayora.ai/ai-receptionist/#trial-checklist

Free to copy and adapt for any provider. Suggested acceptance checks,
not a certification, performance benchmark or record of completed tests.

SET UP A FAIR COMPARISON

Business/task being tested:
Provider and plan:
Product version or test date:
Tester:
Business brief and rules supplied (save a copy):
Connected calendar/integrations and test number:
Required outcome and person responsible for follow-up:
Expected monthly calls/minutes:
Quoted first-month / recurring / peak-month cost:
Unresolved charges or feature questions:

Use the same brief and scenarios for both finalists. Use invented caller
details and a test calendar. Do not put real customer information in a
shared sheet. Write the expected outcome before calling.

SIX CORE CHECKS

1. ORDINARY ENQUIRY
Ask about an opening time, service or rule supplied in the brief.
Pass condition: the answer agrees with that information and the enquiry
record gives the team the details it needs.

2. MISSING ANSWER
Ask for a price or policy that is absent from the brief.
Pass condition: no invented answer or promise; the question and usable
callback details reach the team.

3. APPOINTMENT REQUEST
Ask for an allowed slot, then an unavailable slot.
Pass condition: a confirmed booking exists in the correct calendar and
respects the rules. If booking is unsupported or fails, the caller and
team understand that it is a request awaiting confirmation.

4. CORRECTION
Change a name, callback number or preferred time partway through.
Pass condition: the final summary and any booking use the corrected value.

5. REQUEST FOR A PERSON
Ask to speak to a member of staff. Test an unanswered transfer if supported.
Pass condition: a supported transfer reaches the right person, or the
fallback is clearly explained and recorded. A callback is not a transfer.
Sayora currently supports inbound answering, with no live call transfer.

6. USABLE HANDOFF
Give the resulting message to whoever would handle the enquiry.
Pass condition: they know who called, what they need, what was promised,
what remains unconfirmed and who must take the next action.

RECORD ONE COPY OF THIS BLOCK PER ATTEMPT

Scenario and attempt number:
Date/time:
Exact information/rules supplied:
Expected answer/action:
What actually happened:
Recording/transcript reference (keep private):
Summary/calendar/transfer result:
Pass / fail / not supported / not tested:
Caller told what was confirmed or still pending:
Person responsible for the next action:
Staff repair time:
Correction made:
Retest date and result:

ADD THE HARD CASES YOUR BUSINESS NEEDS

Repeat important scenarios with an interruption, a changed date, an
unfamiliar name, background noise or a missing detail. Check overlapping
calls and disconnected integrations where the provider supports testing
them. Mark anything you could not test as untested.

Estate agency: distinguish a viewing request from a confirmed viewing.
Who maintains property information and who approves the appointment?

Dealership: distinguish a vehicle enquiry, test-drive request and service
question. Who checks stock and who owns the follow-up? Do not assume a
connection to the dealership's systems unless it is configured and tested.

DECIDE BEFORE DIVERTING CUSTOMER CALLS

Essential tasks passed:
Essential tasks failed or untested:
Known limits accepted by the business:
Who checks new enquiries and when:
How to stop diversion and return to the previous arrangement:
Owner's decision and date:

Fix and retest essential failures before expanding use. A small trial
supports conclusions about the calls tested, not a general accuracy or
uptime percentage. Keep failures in the record alongside successful calls.