{
  "name": "VoiceAvo workflow acceptance kit",
  "version": "2026-09-06",
  "notice": "These are planning scenarios to execute, not completed product tests. Use synthetic records and approved test destinations. No live calls are initiated by this file.",
  "cases": [
    {
      "id": "VA-001",
      "workflow": "Outbound Voice API Integration: Request to Result",
      "guide": "https://voiceavo.com/resources/outbound-voice-api-integration",
      "test_and_expected_result": "In a test environment, submit one authorised notification and simulate an accepted request followed by a no-answer event. The business record should remain unconfirmed. Repeat the callback without creating a second follow-up. Finally, simulate the intended recipient acknowledging the message and verify that only this event marks the business objective complete.",
      "limits": "Do not assume that this guide describes a public VoiceAvo calling endpoint. Ask for the currently supported API contract and a demonstration of the exact workflow. Recipient authorisation, destination restrictions, provider limits and human escalation belong in the implementation review before a production number is used.",
      "required_fields": "request identifier, destination, purpose, contact window, provider call identifier and business acknowledgement"
    },
    {
      "id": "VA-002",
      "workflow": "Voice API Webhooks: Events You Can Safely Process",
      "guide": "https://voiceavo.com/resources/voice-api-webhooks",
      "test_and_expected_result": "Deliver the same signed test event twice and check that only one business action occurs. Send a terminal call event before an earlier ringing event; the record must not revert to ringing. Alter a signed field and confirm rejection. Repeat the checks through the actual public reverse proxy used in production.",
      "limits": "Webhook verification depends on the provider, request body and public URL. Do not invent a universal signature formula or trust an event simply because it contains a familiar call identifier. Keep a separate administrative path for replaying failed valid events without exposing that capability to unauthenticated callers.",
      "required_fields": "event identifier, event type, signature result, provider time, received time and processing outcome"
    },
    {
      "id": "VA-003",
      "workflow": "Voice API Call Status Tracking Without False Success",
      "guide": "https://voiceavo.com/resources/voice-api-call-status-tracking",
      "test_and_expected_result": "Run four fixtures: no answer, voicemail, human answer without completion, and human answer with a verified action. All four should have different dispositions even where the carrier reports a completed call. Test a transfer that rings but is never answered and verify that the original enquiry remains unresolved.",
      "limits": "Provider status names are not interchangeable across platforms. Document the mapping for the selected carrier instead of relying on a generic status label. Avoid comparing completion rates between suppliers until each metric uses the same business definition and the same denominator.",
      "required_fields": "business request ID, call leg IDs, transport state, conversation disposition, action confirmation and owner"
    },
    {
      "id": "VA-004",
      "workflow": "Voice API CRM Integration: A Clean Call Handoff",
      "guide": "https://voiceavo.com/resources/voice-api-crm-integration",
      "test_and_expected_result": "Use a shared phone number attached to two test contacts. The workflow should request an approved disambiguating detail or create a review task, not update both records. Simulate a CRM timeout after a successful write and replay the operation. The final record should contain one update and one next action.",
      "limits": "Keep lead scoring, eligibility decisions and unsupported inferences out of the conversation summary. Do not record an assumed budget, preference or identity as a confirmed fact. Integration availability, writable fields and permissions must be confirmed for the actual CRM and VoiceAvo configuration.",
      "required_fields": "contact match method, confirmed fields, call reference, update identifier, next action and responsible team"
    },
    {
      "id": "VA-005",
      "workflow": "Voice API Authentication and Access Boundaries",
      "guide": "https://voiceavo.com/resources/voice-api-authentication-security",
      "test_and_expected_result": "Attempt a test call request using a valid user session from a different tenant. It should fail before a provider request is made. Rotate a test credential and verify that the old value no longer works. Inspect application, proxy and monitoring logs to confirm that neither credential appears in plain text.",
      "limits": "No single checklist establishes that a deployment is secure. This guide defines review questions, not a security certification. The exact permission model, key format and verification method must follow the current provider documentation and the application architecture used for your account.",
      "required_fields": "credential owner, permitted actions, tenant boundary, destination policy, rotation date and audit reference"
    },
    {
      "id": "VA-006",
      "workflow": "Voice API Retry Handling Without Duplicate Calls",
      "guide": "https://voiceavo.com/resources/voice-api-retry-handling",
      "test_and_expected_result": "Simulate a provider accepting a request while the client connection times out. The retry path should discover or reconcile the existing call rather than create another one. Test a confirmed temporary error separately. Check that a later opt-out prevents any pending business retry even if the technical queue still contains the request.",
      "limits": "An unanswered call is not automatically permission to redial indefinitely. Define attempt caps, expiry and a human follow-up path. Provider idempotency behaviour differs, so verify its actual scope and retention before relying on it to prevent duplicate business actions.",
      "required_fields": "operation ID, attempt number, uncertain-result flag, reconciliation result, expiry and suppression status"
    },
    {
      "id": "VA-007",
      "workflow": "Voice API Rate Limits and Queue Planning",
      "guide": "https://voiceavo.com/resources/voice-api-rate-limits",
      "test_and_expected_result": "Use a controlled batch that exceeds the configured test throughput without contacting real recipients. Verify that requests remain identifiable, deadlines are enforced and the application reports queued rather than completed work. Reduce capacity during the test and check whether the oldest eligible request is handled according to the documented queue policy.",
      "limits": "Do not publish a universal calls-per-second allowance or imply that a plan has unlimited concurrency. Limits depend on the provider, account and configuration. A larger queue is not a substitute for permission to contact recipients or for testing the staffing capacity needed for human transfers.",
      "required_fields": "arrival rate, provider limit, active calls, queue age, request deadline and transfer capacity"
    },
    {
      "id": "VA-008",
      "workflow": "Outbound Call Scheduling APIs and Local-Time Windows",
      "guide": "https://voiceavo.com/resources/outbound-call-scheduling-api",
      "test_and_expected_result": "Create test requests around a daylight-saving transition and near midnight in two zones. Confirm that the local promise still matches the queued timestamp. Change the contact preference before dispatch; the old job should not proceed. Simulate a delayed worker and verify that an expired window becomes a review item rather than an immediate call.",
      "limits": "Local-time scheduling is not a substitute for jurisdiction-specific communication rules. Have the responsible team set the permitted windows and recipient permissions. Avoid inferring location solely from a phone prefix, because the person using that number may be travelling or living elsewhere.",
      "required_fields": "requested local window, named time zone, execution timestamp, preference version, expiry and dispatch decision"
    },
    {
      "id": "VA-009",
      "workflow": "A Voice API Sandbox Test Plan",
      "guide": "https://voiceavo.com/resources/voice-api-testing-sandbox",
      "test_and_expected_result": "Run the same fixture set twice and verify identical business outcomes without duplicate records. Point the integration at a deliberately unavailable test service and confirm a controlled fallback. Before any authorised live test, confirm the destination allowlist and inspect the request log for production identifiers that should never have entered the sandbox.",
      "limits": "A provider sandbox may not reproduce production latency, number availability or audio behaviour. Label those limitations in the acceptance report. Do not claim that passing synthetic tests proves every language, carrier route or customer scenario; those require their own measured evidence.",
      "required_fields": "environment, test run ID, synthetic contact, expected event sequence, actual result and evidence layer"
    },
    {
      "id": "VA-010",
      "workflow": "Voice API Call Cost Monitoring by Business Outcome",
      "guide": "https://voiceavo.com/resources/voice-api-call-cost-monitoring",
      "test_and_expected_result": "Model a call that transfers to staff and creates a second billable leg. Verify that both legs remain visible without counting the business request twice. Introduce a delayed cost update and check reconciliation. Test zero completed outcomes: the report should say the outcome metric is unavailable rather than divide by zero.",
      "limits": "This is an accounting design guide, not a VoiceAvo price quote or a claim of savings. Use the rates in your actual agreements and include human review effort. A lower transport bill is not an improvement when it is accompanied by more unresolved calls.",
      "required_fields": "call leg, usage quantity, unit, currency, estimated versus final amount and verified outcome"
    },
    {
      "id": "VA-011",
      "workflow": "Multilingual AI Receptionists for Small Businesses",
      "guide": "https://voiceavo.com/resources/multilingual-ai-receptionist-small-business",
      "test_and_expected_result": "Ask fluent reviewers to call with the same request in each selected language. Compare captured dates, names, requested services and handoff notes, not just how natural the voice sounds. Include an unsupported language and a caller who switches midway. Both cases should reach a clear fallback without an invented answer.",
      "limits": "Available voices and languages depend on the provider and configuration. Confirm the actual supported combination before advertising it to customers. Do not describe every multilingual interaction as real-time translation or imply that all languages have equal tested accuracy.",
      "required_fields": "priority language, supported intent, approved answer source, confirmed fields, language reviewer and fallback owner"
    },
    {
      "id": "VA-012",
      "workflow": "AI Receptionist Language Switching During a Call",
      "guide": "https://voiceavo.com/resources/ai-receptionist-language-switching",
      "test_and_expected_result": "Start a booking enquiry in one supported language, supply a date in another and return to the first for confirmation. The final appointment request should contain one consistent date and one customer record. Include a phrase that resembles a language change but is actually a product name; the agent should not switch without adequate reason.",
      "limits": "Language detection is not identity verification and should not be used to infer nationality or personal background. When confidence remains low, offer the configured human or message-taking path. A smooth voice transition alone is not proof that the underlying request survived correctly.",
      "required_fields": "current language, explicit preference, preserved fields, confirmation status, switch event and handoff language"
    },
    {
      "id": "VA-013",
      "workflow": "AI Receptionists for International Customer Enquiries",
      "guide": "https://voiceavo.com/resources/ai-receptionist-international-customers",
      "test_and_expected_result": "Provide a date that could be interpreted in two common numeric orders and verify that the receptionist clarifies it. Test a caller booking for a location in a different time zone. Supply an international callback number with a leading zero and confirm that the stored number follows the approved validation rules.",
      "limits": "Do not infer legal eligibility, residency or language ability from a telephone prefix or accent. International service availability is a business decision that must come from approved information. Translation should not create promises about delivery, coverage or availability that are absent from the source policy.",
      "required_fields": "service location, unambiguous date, relevant time zone, validated callback number and unresolved policy question"
    },
    {
      "id": "VA-014",
      "workflow": "Bilingual AI Receptionist: A Two-Language Acceptance Plan",
      "guide": "https://voiceavo.com/resources/bilingual-ai-receptionist",
      "test_and_expected_result": "Run paired tests for a new booking, a cancellation, a question outside scope and a request for a human. Compare whether the same next action occurs in both languages. Change one business fact and verify that both language paths use the new information before the release is approved.",
      "limits": "Equivalent outcomes do not require word-for-word identical scripts. Allow natural language while preserving the operational meaning. Do not call a service bilingual merely because it can play two greetings; test understanding, field capture, confirmation and human transfer in both languages.",
      "required_fields": "language pair, shared intent, translated policy version, reviewer, expected action and outcome parity"
    },
    {
      "id": "VA-015",
      "workflow": "Multilingual Call Routing to the Right Team",
      "guide": "https://voiceavo.com/resources/multilingual-call-routing",
      "test_and_expected_result": "Test a supported language during the relevant team working hours and again after that queue closes. Simulate a transfer destination that rings without answering. Verify that the caller is not trapped in a loop and that the unresolved request is assigned to an owner with its language preference preserved.",
      "limits": "A language label should guide service, not determine customer eligibility or priority without an explicit lawful business policy. Do not advertise a staffed language queue until its hours, fallback and actual staffing have been verified by the organisation.",
      "required_fields": "language preference, intent, destination queue, availability check, transfer result and fallback owner"
    },
    {
      "id": "VA-016",
      "workflow": "Evaluating AI Receptionist Accent Recognition",
      "guide": "https://voiceavo.com/resources/ai-receptionist-accent-recognition",
      "test_and_expected_result": "Use the same appointment task across several consenting speakers and include uncommon names, letters that sound similar and a noisy line. The acceptance check is whether the final confirmed details are correct or safely escalated. A fluent but wrong confirmation must be counted as a failure, not a partially successful conversation.",
      "limits": "Do not infer ethnicity, nationality or personal attributes from an accent. Avoid publishing unsupported accuracy percentages. Report the size, conditions and limits of the actual evaluation, and keep an accessible human alternative when repeated clarification does not resolve the request.",
      "required_fields": "task-critical fields, consented test case, audio conditions, clarification count, confirmed record and fallback result"
    },
    {
      "id": "VA-017",
      "workflow": "Multilingual Voicemail and Message Capture",
      "guide": "https://voiceavo.com/resources/multilingual-voicemail-assistant",
      "test_and_expected_result": "Leave a message with an unclear surname and an ambiguous time. The system should seek clarification where the interaction allows it, or mark the uncertainty instead of inventing a correction. Test a request that sounds urgent and confirm that the approved escalation instruction is used rather than an ordinary callback promise.",
      "limits": "Message capture is not emergency handling, a confirmed appointment or proof that a staff member has reviewed the request. Establish retention, access and deletion rules for audio and transcripts. Verify the languages actually supported by the chosen transcription and voice configuration.",
      "required_fields": "caller-provided name, callback detail, original language, reason, uncertainty marker and assigned inbox"
    },
    {
      "id": "VA-018",
      "workflow": "Checking AI Receptionist Translation Quality",
      "guide": "https://voiceavo.com/resources/ai-receptionist-translation-quality",
      "test_and_expected_result": "Test a policy with a conditional exception and a date. Ask the same question using indirect wording in the target language. Check that the answer preserves the condition and does not simplify away the exception. Repeat with a product name that resembles an ordinary word and verify consistent treatment.",
      "limits": "Translation review should not be presented as legal review of a contract or clinical interpretation. Escalate when exact wording is necessary and the approved translation is missing. Record which languages and policy versions were tested instead of asserting universal translation accuracy.",
      "required_fields": "source policy, glossary term, translated answer, meaning-critical condition, reviewer and version"
    },
    {
      "id": "VA-019",
      "workflow": "Gym Lead Qualification with an AI Voice Workflow",
      "guide": "https://voiceavo.com/resources/gym-ai-lead-qualification",
      "test_and_expected_result": "Test a caller who wants a tour but declines to discuss fitness goals. The workflow should still offer an appropriate visit or staff callback. Include an existing member asking about a class and verify that they are not treated as a new sales lead or placed into an unrelated marketing sequence.",
      "limits": "A receptionist should not infer health conditions, financial capacity or willingness to buy from the caller voice. Do not ask for sensitive health information merely to qualify a lead. Membership suitability and special arrangements remain with authorised gym staff.",
      "required_fields": "stated interest, location, visit preference, follow-up permission, existing-member flag and next owner"
    },
    {
      "id": "VA-020",
      "workflow": "Gym Trial Booking by Voice: From Enquiry to Confirmation",
      "guide": "https://voiceavo.com/resources/gym-trial-booking-voice-assistant",
      "test_and_expected_result": "Offer the last available trial slot to two simultaneous test enquiries. Only one should receive a confirmed reservation. Simulate a timeout after the booking is created and verify that reconciliation does not create a duplicate. Include a caller who changes location midway and check that availability is looked up again.",
      "limits": "Do not invent a free-trial offer or guarantee entry where eligibility has not been verified. Any waivers, age requirements or special access arrangements must come from approved gym policy and be handled by the appropriate staff or booking process.",
      "required_fields": "location, trial type, policy version, chosen slot, booking identifier and confirmation state"
    },
    {
      "id": "VA-021",
      "workflow": "Automating Gym Membership Enquiries Without Misquoting",
      "guide": "https://voiceavo.com/resources/gym-membership-enquiry-automation",
      "test_and_expected_result": "Ask about an expired promotion and then request an exception to the current offer. The receptionist should state that the promotion cannot be confirmed and route the exception to staff. Test a caller asking whether one membership covers another location and verify that the answer follows the actual access policy.",
      "limits": "Do not take payment details, promise contract changes or state cancellation rights from an unreviewed script. This guide does not provide consumer-law advice or a gym price schedule. The business must supply approved terms and a reliable process for account-specific decisions.",
      "required_fields": "location, membership option, current terms reference, requested information, proposed follow-up and staff owner"
    },
    {
      "id": "VA-022",
      "workflow": "Gym Missed-Call Follow-Up: A Controlled Callback Process",
      "guide": "https://voiceavo.com/resources/gym-missed-call-follow-up",
      "test_and_expected_result": "Test a missed call from an existing member who only needs opening hours. It should not become a new prospect campaign. Simulate a caller asking not to be contacted again and verify that pending retries stop. Test a wrong number and confirm that the record is corrected rather than repeatedly retried.",
      "limits": "A missed call does not automatically authorise unrelated marketing. Keep callback purpose narrow and have the responsible team define applicable permission rules. Do not measure success solely by how many return calls were placed; measure whether the original request was resolved.",
      "required_fields": "original call reference, known intent, permitted callback window, attempt outcome, preference and resolution"
    },
    {
      "id": "VA-023",
      "workflow": "Gym Class Booking Through a Phone Assistant",
      "guide": "https://voiceavo.com/resources/gym-class-booking-phone-assistant",
      "test_and_expected_result": "Test two sessions with the same class name on the same day. The workflow should confirm the intended time rather than choose one silently. Try a booking without the required entitlement and verify a controlled staff handoff. Cancel a test reservation and check that the capacity update occurs exactly once.",
      "limits": "The assistant should not give exercise suitability advice or override staff restrictions. Avoid inventing a waitlist place, attendance guarantee or late-cancellation charge. These details must come from the live booking rules and approved policy.",
      "required_fields": "member verification result, class occurrence, eligibility result, available capacity, reservation ID and next action"
    },
    {
      "id": "VA-024",
      "workflow": "Personal Training Consultation Booking: Safe Intake",
      "guide": "https://voiceavo.com/resources/personal-training-consultation-booking",
      "test_and_expected_result": "Test a request for rehabilitation advice during a booking call. The workflow should avoid answering clinically and offer an appropriate staff conversation under the gym rules. Include a consultation requiring a longer duration and verify that the assistant does not book an ordinary tour slot by mistake.",
      "limits": "Do not collect detailed medical history through an unapproved voice intake or make claims about treatment, results or suitability. The availability and qualifications of staff are business facts that must be verified, not inferred from a generic service description.",
      "required_fields": "consultation type, location, required duration, assigned professional, confirmed slot and requested accommodation"
    },
    {
      "id": "VA-025",
      "workflow": "Gym Membership Renewal Calls with Clear Boundaries",
      "guide": "https://voiceavo.com/resources/gym-membership-renewal-calls",
      "test_and_expected_result": "Test a member who says they already renewed. The workflow should check or escalate the discrepancy rather than repeat the sales script. Include a caller requesting cancellation and verify that the request reaches the correct owner. Simulate an account update failure and confirm that no success message is given.",
      "limits": "Do not infer agreement from silence or a casual acknowledgement. Avoid collecting card data in a workflow not designed and approved for payment handling. Contract changes, exceptional pricing and disputed balances belong with authorised staff and the approved account process.",
      "required_fields": "member reference, renewal status, reminder purpose, contact permission, requested action and confirmed account outcome"
    },
    {
      "id": "VA-026",
      "workflow": "A Gym AI Sales Agent Script That Respects the Caller",
      "guide": "https://voiceavo.com/resources/gym-ai-sales-agent-script",
      "test_and_expected_result": "Use three role-play callers: someone comparing options, someone who only asks for opening hours and someone who says no to follow-up. The script should serve each request without forcing qualification questions. Ask about an unavailable discount and verify that the assistant does not improvise an offer to keep the conversation moving.",
      "limits": "Do not impersonate a human member of staff, invent scarcity or promise fitness results. A caller declining a visit or marketing follow-up should not be challenged repeatedly. Record only confirmed preferences, and let staff handle negotiation, complaints and unusual membership circumstances.",
      "required_fields": "approved greeting, caller goal, confirmed information, offered next step, preference and handoff condition"
    },
    {
      "id": "VA-027",
      "workflow": "AI Inbound Call Routing with a Clear Fallback",
      "guide": "https://voiceavo.com/resources/ai-inbound-call-routing",
      "test_and_expected_result": "Test a caller who names a department incorrectly but describes the right service. The routing should follow the confirmed intent, not a keyword alone. Simulate an unavailable destination and verify that the system does not loop through the same queue. Include an explicit request for a person early in the call.",
      "limits": "Do not treat every ambiguous request as a reason to continue questioning indefinitely. Set a limit and a human route. Routing rules should come from the business and should not infer customer value or eligibility from voice, accent or personal characteristics.",
      "required_fields": "confirmed intent, route rule, available destination, transfer acceptance, context supplied and unresolved owner"
    },
    {
      "id": "VA-028",
      "workflow": "After-Hours AI Receptionist: Promises the Business Can Keep",
      "guide": "https://voiceavo.com/resources/after-hours-ai-receptionist",
      "test_and_expected_result": "Test just before closing, just after closing and during a configured holiday. Ask for a same-night visit that the business does not offer; the assistant must not promise dispatch. Simulate a callback queue failure and verify that the caller receives an honest alternative rather than a false confirmation.",
      "limits": "Do not describe an automated phone line as round-the-clock staffed support unless that is true. Emergency instructions and guaranteed response times require explicit business approval. This guide is a planning framework, not a claim about VoiceAvo uptime or a service-level agreement.",
      "required_fields": "location hours, holiday rule, caller intent, permitted after-hours action, callback expectation and team owner"
    },
    {
      "id": "VA-029",
      "workflow": "AI Call Overflow Handling During Busy Periods",
      "guide": "https://voiceavo.com/resources/ai-call-overflow-handling",
      "test_and_expected_result": "Simulate a busy queue with a mixture of routine questions and requests requiring staff authority. Verify that routine answers use current information while unresolved work returns with context. Remove the overflow condition during a call and check that the caller is not abruptly rerouted or duplicated in two queues.",
      "limits": "Overflow is not proof of additional human capacity. Do not promise immediate staff access when the same team is already unavailable. Track abandoned and unresolved overflow calls separately so an apparently lower queue time does not hide worse customer outcomes.",
      "required_fields": "overflow trigger, original call reference, handled intent, staff-required reason, follow-up record and return condition"
    },
    {
      "id": "VA-030",
      "workflow": "AI Phone Answering for a Small Business",
      "guide": "https://voiceavo.com/resources/ai-phone-answering-small-business",
      "test_and_expected_result": "Call with a question whose answer changed recently, such as a holiday closure. Verify that the updated fact appears in the response. Ask for an unsupported service and ensure the assistant says so rather than inventing availability. Test message delivery when the normal inbox or integration is unavailable.",
      "limits": "Do not equate an answered call with a satisfied customer. Keep a human contact option and a process for correcting information quickly. Confirm the actual voice, telephony and integration configuration before promising customers a particular automated action.",
      "required_fields": "approved knowledge owner, supported intent, answer version, caller-confirmed detail, next action and unresolved list"
    },
    {
      "id": "VA-031",
      "workflow": "Home Services Call Intake Without False Dispatch Promises",
      "guide": "https://voiceavo.com/resources/ai-home-services-call-intake",
      "test_and_expected_result": "Test an address outside the normal coverage area and a caller asking for immediate attendance. The assistant should not promise service merely because a slot appears free. Simulate a dispatch-system rejection after details are collected; the result must remain an enquiry awaiting staff review.",
      "limits": "The assistant should not provide unsafe repair instructions, assess hazards or invent an emergency response. Use the business-approved safety and escalation wording. Quotes, diagnosis and dispatch commitments require the appropriate authority and a confirmed downstream action.",
      "required_fields": "service request, validated address, coverage result, access detail, scheduling state and responsible dispatcher"
    },
    {
      "id": "VA-032",
      "workflow": "AI Customer Service Human Handoff That Preserves Context",
      "guide": "https://voiceavo.com/resources/ai-customer-service-human-handoff",
      "test_and_expected_result": "Ask for a human at the start of the call, after a failed action and during an ambiguous request. All three should follow the documented rule. Simulate an unanswered transfer and check that the caller is offered a genuine alternative. Inspect the staff summary for invented facts or unnecessary sensitive information.",
      "limits": "Do not make callers argue with the assistant to reach a person. Handoff summaries should identify uncertainty rather than conceal it. Staffing availability and callback expectations must reflect the business operation, not an optimistic default in the script.",
      "required_fields": "handoff reason, confirmed summary, destination, acceptance event, fallback choice and staff ownership"
    },
    {
      "id": "VA-033",
      "workflow": "AI Missed-Call Recovery Without Inflated Conversion Claims",
      "guide": "https://voiceavo.com/resources/ai-missed-call-recovery",
      "test_and_expected_result": "Use fixtures for a duplicate missed-call event, a wrong number, a caller who has already resolved the issue and someone who declines contact. The process should avoid duplicate callbacks and unnecessary follow-up. Check that a completed callback without a resolved request remains an unresolved business outcome.",
      "limits": "Do not claim recovered revenue from call counts alone. Permission for service callbacks and permission for promotional contact may differ. Keep the callback within its approved purpose and make suppression or preference changes effective before pending attempts are dispatched.",
      "required_fields": "original event, existing case, contact permission, callback outcome, verified resolution and suppression update"
    },
    {
      "id": "VA-034",
      "workflow": "AI Call Summaries and Ticket Creation",
      "guide": "https://voiceavo.com/resources/ai-call-summary-ticket-creation",
      "test_and_expected_result": "Use a caller who is unsure of an order number and describes a suspected cause. The ticket should mark the number as unconfirmed and the cause as the caller report, not a finding. Simulate a helpdesk timeout after creation and verify that retry reconciliation does not produce duplicate tickets.",
      "limits": "A generated summary is not a verbatim transcript or an independent verification of the caller account. Set access and retention rules for both. Do not let the assistant change case priority, issue refunds or close complaints unless the business has explicitly authorised those actions.",
      "required_fields": "caller request, confirmed identifier, uncertainty, attempted action, helpdesk acknowledgement and next owner"
    },
    {
      "id": "VA-035",
      "workflow": "AI Patient Appointment Booking: Administrative Scope",
      "guide": "https://voiceavo.com/resources/ai-patient-appointment-booking",
      "test_and_expected_result": "Test a routine booking, an unclear appointment category, a calendar outage and a caller describing a concern outside administrative scope. The workflow should confirm only bookings accepted by the scheduling system and should use the approved escalation route for the other cases without inventing clinical advice.",
      "limits": "This guide is not medical advice, emergency triage guidance or a declaration that a product meets healthcare privacy requirements. The practice must approve the workflow, access controls, data handling and escalation instructions before any patient information or live calls are used.",
      "required_fields": "approved appointment category, identity-check result, calendar availability, location, booking ID and staff escalation"
    },
    {
      "id": "VA-036",
      "workflow": "Clinic Calendar Integration for an AI Receptionist",
      "guide": "https://voiceavo.com/resources/ai-clinic-calendar-integration",
      "test_and_expected_result": "Simulate a slot becoming unavailable between lookup and confirmation. The receptionist should offer a verified alternative or staff follow-up rather than claim success. Test a category with a different duration and a clinician-specific restriction. Ensure that unrelated patient names or appointment details never appear in the spoken response.",
      "limits": "Do not advertise compatibility with a clinical system merely because it has an API. Confirm the permitted integration, access model and tested functions for the actual deployment. Administrative scheduling rules must come from the practice and must not be used as a substitute for clinical judgement.",
      "required_fields": "appointment category, calendar permission, required duration, slot version, confirmation ID and exception owner"
    },
    {
      "id": "VA-037",
      "workflow": "Patient Appointment Rescheduling Without Losing the Original",
      "guide": "https://voiceavo.com/resources/ai-patient-appointment-rescheduling",
      "test_and_expected_result": "Simulate the replacement booking failing after the reschedule begins. Verify that the original appointment is preserved or that a clearly owned exception is created under the agreed recovery process. Test a caller changing clinician or appointment category, which may need staff approval rather than a simple time change.",
      "limits": "The assistant should not override clinical scheduling restrictions, erase the original appointment casually or promise a replacement without system confirmation. This is an administrative design guide; the practice decides which appointments may be changed automatically and which require staff review.",
      "required_fields": "identity result, original booking, permitted change, replacement slot, final confirmed state and recovery owner"
    },
    {
      "id": "VA-038",
      "workflow": "Patient Appointment Reminders with Minimal Disclosure",
      "guide": "https://voiceavo.com/resources/ai-patient-appointment-reminders",
      "test_and_expected_result": "Test a shared phone, voicemail, a wrong-number response and an appointment changed after the reminder was queued. Verify that sensitive details are not disclosed outside the approved flow and that stale reminders are suppressed. A connected call without the intended acknowledgement should not count as a confirmed patient response.",
      "limits": "Do not infer permission from the mere presence of a phone number in a record. The practice must determine lawful communication, privacy and retention rules. This page provides administrative test questions, not legal advice or a claim that VoiceAvo is certified for a particular healthcare environment.",
      "required_fields": "appointment reference, approved contact preference, disclosure level, reminder version, delivery state and verified response"
    },
    {
      "id": "VA-039",
      "workflow": "Clinic Waitlist Calls: Offer a Slot Without Overbooking",
      "guide": "https://voiceavo.com/resources/ai-clinic-waitlist-calls",
      "test_and_expected_result": "Offer one synthetic cancellation slot to the permitted test sequence and simulate two near-simultaneous acceptances. Only one appointment should be confirmed. Test an expired offer and an unavailable recipient. Verify that the assistant does not select the next patient based on an improvised judgement about medical urgency.",
      "limits": "The practice owns waitlist ordering, clinical priority and eligibility. Do not disclose other patients, claim a held slot when none exists or imply that accepting a call changes clinical priority. Escalate uncertain selection or booking conflicts to authorised staff.",
      "required_fields": "authorised waitlist entry, offer expiry, current slot state, recipient response, booking confirmation and staff exception"
    },
    {
      "id": "VA-040",
      "workflow": "Human Escalation for an Administrative Medical Receptionist",
      "guide": "https://voiceavo.com/resources/ai-medical-receptionist-human-escalation",
      "test_and_expected_result": "Test a routine appointment question, an explicit request for a clinician and a caller whose request is unclear. Confirm that the workflow does not diagnose, reassure clinically or decide that care can wait. Simulate an unavailable staff line and verify the exact practice-approved fallback is used.",
      "limits": "This page does not define emergency triage or medical escalation criteria. Those must be approved by qualified practice leadership and relevant advisers. The receptionist should never claim to replace emergency services, clinical judgement or an available professional where the organisation cannot provide one.",
      "required_fields": "role boundary, approved trigger, permitted context, destination acceptance, fallback instruction and responsible practice team"
    },
    {
      "id": "VA-041",
      "workflow": "Privacy Questions for AI Patient Scheduling",
      "guide": "https://voiceavo.com/resources/ai-patient-scheduling-privacy",
      "test_and_expected_result": "Trace one synthetic appointment request through the call record, transcript, summary, calendar and support logs. Verify that access is limited to the intended roles and that unnecessary information is not copied into notifications. Test the agreed deletion or retention procedure on the synthetic record and document any system that retains a separate copy.",
      "limits": "This checklist is not a legal opinion or a statement of HIPAA, GDPR or other regulatory compliance. Requirements depend on the organisation, jurisdiction, providers and agreements. Do not process live patient information until the responsible practice has approved the actual data flow and safeguards.",
      "required_fields": "data element, purpose, processor, access role, retention rule, deletion path and approving owner"
    },
    {
      "id": "VA-042",
      "workflow": "Dental Appointment Intake for Administrative Requests",
      "guide": "https://voiceavo.com/resources/ai-dental-appointment-intake",
      "test_and_expected_result": "Test a new-patient enquiry, an existing appointment change and a caller asking for treatment advice. The first two should follow the approved administrative rules; the advice request should reach the practice-defined professional route. Simulate a scheduling failure and verify that no appointment is promised without confirmation.",
      "limits": "Do not recommend treatment, interpret symptoms or make guarantees about fees, insurance coverage or urgent availability. These are practice-specific and may require professional review. The workflow should make it easy to speak with staff and should use only the practice approved instructions outside routine administration.",
      "required_fields": "new or existing patient status, approved request category, location, booking state, necessary details and staff route"
    },
    {
      "id": "VA-043",
      "workflow": "AI Voice vs IVR Cost: Compare the Same Workload",
      "guide": "https://voiceavo.com/resources/ai-voice-vs-ivr-cost",
      "test_and_expected_result": "Build two scenarios with identical demand and success definitions. Increase the unresolved-call rate in one scenario and check that the added staff work affects the comparison. Model a month with lower volume so fixed fees become visible. Keep any unmeasured cost labelled as an estimate rather than filling it with an invented benchmark.",
      "limits": "This guide does not claim that AI voice is always cheaper than IVR or provide a price quote. A low unit price can be offset by integration effort or unresolved calls. Use actual agreements and measured pilot results before making a purchasing decision.",
      "required_fields": "shared workload, completion definition, fixed cost, variable cost, staff follow-up and sensitivity assumption"
    },
    {
      "id": "VA-044",
      "workflow": "Migrating from IVR to AI Voice Without a Blind Cutover",
      "guide": "https://voiceavo.com/resources/ivr-to-ai-voice-migration",
      "test_and_expected_result": "Simulate the conversational service being unavailable during the pilot. Calls should reach the documented fallback without a dead end. Test a caller who uses keypad input and one who asks for a human. Verify that reporting can distinguish the old route, pilot route and any fallback so results are not blended.",
      "limits": "Do not remove a working emergency, accessibility or specialist route merely to simplify the new design. The business must approve every routing change and the rollback conditions. A fluent demo is not evidence that the entire current phone estate can be replaced safely.",
      "required_fields": "current route, pilot intent, fallback destination, rollback trigger, matched metric and expansion decision"
    },
    {
      "id": "VA-045",
      "workflow": "AI Voice Agent or Phone Menu: Choose by Task",
      "guide": "https://voiceavo.com/resources/ai-voice-agent-vs-phone-menu",
      "test_and_expected_result": "Test a simple department selection and a multi-part service enquiry in both designs. Use the same task wording and comparable participants. A shorter call should count as better only when the caller reaches the right result. Include a caller who cannot or does not want to use the preferred interaction mode.",
      "limits": "Do not create a deliberately poor IVR example to make a conversational demonstration look superior. Compare a reasonably designed alternative and document its strengths. The final choice should reflect actual callers, maintenance capacity and the business tolerance for interpretation errors.",
      "required_fields": "caller task, interaction steps, interpretation need, alternative mode, routing result and unresolved reason"
    },
    {
      "id": "VA-046",
      "workflow": "Conversational IVR vs Traditional IVR: Define the Terms",
      "guide": "https://voiceavo.com/resources/conversational-ivr-vs-traditional-ivr",
      "test_and_expected_result": "Give both systems an ambiguous request that needs one clarifying question, followed by a simple known request. Verify whether each reaches the correct action and how it handles uncertainty. Test the same unavailable integration to ensure neither system claims a result that its backend did not confirm.",
      "limits": "Product categories overlap and supplier terminology varies. Avoid universal claims about what all traditional or conversational systems can do. Ask each provider to demonstrate the specific interaction, integration and fallback capabilities required by your organisation.",
      "required_fields": "input mode, ambiguity handling, action permissions, workflow flexibility, confirmed outcome and provider evidence"
    },
    {
      "id": "VA-047",
      "workflow": "AI Voice Agent Accuracy Testing by Completed Task",
      "guide": "https://voiceavo.com/resources/ai-voice-agent-accuracy-testing",
      "test_and_expected_result": "Use a case where the assistant produces a fluent answer but changes the appointment date. It must fail the task check. Include a legitimate staff escalation and record it separately rather than calling it a successful automated completion. Repeat a fixed set after a configuration change and compare the actual case-level differences.",
      "limits": "Do not advertise an accuracy percentage without its sample size, task definition and test conditions. A small internal test is not an independent benchmark. Avoid tuning on the final evaluation set and then presenting the resulting score as performance on unseen requests.",
      "required_fields": "case ID, expected intent, critical fields, permitted action, actual result, escalation class and evaluation split"
    },
    {
      "id": "VA-048",
      "workflow": "Testing AI Voice Agent Latency Across the Whole Call",
      "guide": "https://voiceavo.com/resources/ai-voice-agent-latency-testing",
      "test_and_expected_result": "Compare a simple information question with a calendar lookup and a human transfer. Add a controlled backend delay and verify that the assistant does not falsely announce completion while waiting. Include overlapping speech and a short pause within the caller sentence to test whether response timing causes interruptions or truncation.",
      "limits": "Do not quote a universal latency guarantee from a local simulation or a different provider route. State the hardware, services, network and test conditions actually measured. A slightly longer but accurate confirmed action can be better than a fast answer that leaves the request unresolved.",
      "required_fields": "connection time, end-of-turn time, first audio, action duration, delay distribution and caller interruption result"
    },
    {
      "id": "VA-049",
      "workflow": "An AI Voice Agent Pilot Checklist with Stop Conditions",
      "guide": "https://voiceavo.com/resources/ai-voice-agent-pilot-checklist",
      "test_and_expected_result": "Before launch, simulate the most important stop condition, such as repeated booking errors or an unavailable handoff. Confirm that the team can disable the pilot route and restore the prior service. Run a request outside the pilot scope and check that the assistant uses the agreed boundary instead of expanding its own role.",
      "limits": "A pilot result should be reported as a pilot result, not a universal guarantee. Do not expand to additional languages, industries or high-consequence tasks without separate acceptance evidence. Keep responsibility for live operations with the business and its designated staff.",
      "required_fields": "pilot owner, allowed intent, acceptance case, stop condition, fallback route, configuration version and review decision"
    },
    {
      "id": "VA-050",
      "workflow": "Call Containment vs Resolution: Avoid a Misleading Metric",
      "guide": "https://voiceavo.com/resources/ai-call-containment-vs-resolution",
      "test_and_expected_result": "Create three test calls: one ends after a wrong answer, one reaches a person and one completes a confirmed booking automatically. Only the third is an automated resolution. The second may still be a successful service outcome. The first must remain a failure even though it never left the automated channel.",
      "limits": "Do not use containment alone to justify reducing support access or to claim customer satisfaction. Outcome definitions should be set before the evaluation and applied consistently. Report the denominator and exclusions, particularly calls that disconnect before the assistant understands the request.",
      "required_fields": "intent, verified outcome evidence, transfer result, abandonment point, unresolved reason and reporting denominator"
    }
  ]
}