A polished greeting is only one part of reception. A useful evaluation follows the caller’s request through the answer, any booking or transfer, and the record your staff receive.
Download the blank call-test scorecard. Run the same scenarios with each service you are considering. The scenarios below are a testing method, not published customer results or vendor performance benchmarks.
Prepare a small set of known answers
Write down your approved hours, services, service area, booking rules, and transfer destinations. Use test contact details and a calendar your team has designated for evaluation. Tell any staff receiving test transfers what to expect.
For each call, record the date, configuration, language, request, and expected next step. Change one configuration issue at a time so a repeat test can show whether the change helped.
Run these reception scenarios
| Scenario | What to try | Evidence to review |
|---|---|---|
| Routine question | Ask about an approved service and opening hours | The answer agrees with your current business information |
| Unknown answer | Ask for a price or service you have not configured | The receptionist acknowledges the limit and captures or routes the request |
| New enquiry | Give a name, callback number, and service request | Staff receive the correct contact details and reason for calling |
| Booking | Request a supported appointment type | A confirmed result exists in the connected provider before the caller is told it is booked |
| No available time | Request a time outside the calendar’s availability | No appointment is invented; preferences are captured for an approved next step |
| Transfer answered | Ask for a configured staff destination | The intended person receives the call and the caller understands the handoff |
| Transfer unanswered | Make the destination unavailable during the test | The caller receives the configured fallback and staff get a usable message |
| Returning caller | Ask a follow-up using a test contact | Any available history is relevant and does not replace confirmation of the current request |
| Bilingual enquiry | Repeat an approved request in each language you serve | The request, names, dates, and next step remain accurate |
| SMS reply | Request information by text using a designated test number | Consent, destination, requested content, and opt-out handling match your configuration |
Score the evidence honestly
Use pass, needs work, unresolved, or not applicable for each scenario. An unavailable recording or missing provider receipt is unresolved. Do not count it as a pass simply because a summary says the action happened.
Keep caller experience and business records as separate observations. An appointment may exist even if the caller heard a confusing confirmation. A courteous conversation may still leave the wrong callback number. Both observations help your team choose the next fix.
Compare the work left for staff
Count the requests your team still needs to clarify, re-enter, or return. Review whether messages include the details that matter for your industry, rather than rewarding a longer summary by itself. See a legal intake example for a practical way to define those details.
Compare the same coverage window and usage unit when assessing price. Dialbox uses monthly AI-handled inbound call pools; other services may quote minutes, calls, staff seats, or a combination. Your own call mix is the useful denominator.
Repeat before expanding coverage
Retest changed business information, new appointment types, staff destinations, and languages. Start with a coverage window your team can supervise, then review real reception records before expanding.
For Dialbox, use the connected-calendar booking guide, bilingual answering guidance, and reception Playbooks. Test the coverage and languages your business actually uses.
