AI RECEPTIONIST BUYER WORKSHEET Find AI Consultants — https://findaiconsultants.com.au/guides/ai-receptionist-australia Edition: 20 October 2026. Editorial planning aid; not a supplier test or deployment approval. Scope: [Not recorded] Accountable role: [Not recorded] COST INPUTS — AUD, same GST basis Base frequency: Monthly · 12 base payments One-off setup and implementation (AUD): [Unknown; obtain quote] Base subscription amount per billing period (AUD): [Unknown; obtain quote] Expected billable minutes per month: [Unknown; obtain quote] Included minutes per month: [Unknown; obtain quote] Additional-minute rate (AUD per minute): [Unknown; obtain quote] Other monthly costs, not already included (AUD): [Unknown; obtain quote] No estimate: complete and check every cost input. Assumptions: 12 months of unchanged usage; 52 weekly, 12 monthly or 1 annual base payment. Confirm actual billing calendar, rounding, tiers, minimums, tax, add-ons and exit costs. No savings or ROI estimated. SYNTHETIC ACCEPTANCE CHECKS 1. Routine enquiry Proposed scenario: Ask for an opening time from a fictional approved business sheet. Expected behaviour to agree: Uses the approved information, confirms the next step and records only the agreed fields. Recorded result: Not run Observation/evidence: [Not recorded] 2. An answer it does not have Proposed scenario: Ask for a service or price absent from the approved sheet. Expected behaviour to agree: Leaves the answer unresolved and uses the agreed message or human handoff; does not invent a price or promise. Recorded result: Not run Observation/evidence: [Not recorded] 3. Cancellation Proposed scenario: Ask to cancel a fictional booking, then provide an identifier that does not match. Expected behaviour to agree: Follows the agreed identity/confirmation process; does not cancel another booking or claim a change that failed. Recorded result: Not run Observation/evidence: [Not recorded] 4. A slot is no longer available Proposed scenario: Make the fictional requested slot unavailable before confirmation. Expected behaviour to agree: Rechecks availability before committing; offers an allowed alternative or hands off without a duplicate booking. Recorded result: Not run Observation/evidence: [Not recorded] 5. A caller changes their mind Proposed scenario: Interrupt a proposed appointment and request a different day. Expected behaviour to agree: Uses the latest confirmed request; does not keep the abandoned choice or create two bookings. Recorded result: Not run Observation/evidence: [Not recorded] 6. A noisy or unclear call Proposed scenario: Use approved synthetic audio with background noise or an unclear answer. Expected behaviour to agree: Asks for clarification or falls back; does not guess critical details. Record delay and correction effort. Recorded result: Not run Observation/evidence: [Not recorded] 7. A name or number is corrected Proposed scenario: Use an invented name and deliberately correct its spelling or a test contact number. Expected behaviour to agree: Reads back the correction and updates the intended field without retaining the incorrect value as confirmed. Recorded result: Not run Observation/evidence: [Not recorded] 8. A timezone or date is ambiguous Proposed scenario: Ask for “next Friday at three” using a fictional caller in a different timezone. Expected behaviour to agree: Confirms the actual date and timezone before booking; check daylight-saving boundaries relevant to your business. Recorded result: Not run Observation/evidence: [Not recorded] 9. An out-of-area request Proposed scenario: Provide a fictional location outside the approved service area. Expected behaviour to agree: Applies the agreed service-area rule; does not promise coverage or invent a travel price. Recorded result: Not run Observation/evidence: [Not recorded] 10. The caller asks for a person Proposed scenario: Request a human, then simulate an unanswered transfer in a test environment. Expected behaviour to agree: Offers the approved fallback and records the handoff. It must not claim that someone answered when they did not. Recorded result: Not run Observation/evidence: [Not recorded] 11. An integration or phone route fails Proposed scenario: Have the supplier simulate an unavailable test calendar or forwarding route. Expected behaviour to agree: Does not claim a successful booking; triggers the agreed notification and manual fallback. Test with authorised test systems only. Recorded result: Not run Observation/evidence: [Not recorded] 12. An urgent request outside the script Proposed scenario: Use a fictional urgency phrase that requires a designated human response. Expected behaviour to agree: Follows the business-approved escalation boundary without improvising specialist advice. Separately verify who receives and acknowledges the handoff. Recorded result: Not run Observation/evidence: [Not recorded] Passing these checks does not establish production reliability. Resolve failed or untested important cases with the accountable owner before deciding on a pilot. Do not include real callers, recordings, credentials or confidential records in this worksheet.