The design decision
Rescheduling can fail halfway through if the original appointment is cancelled before the replacement is secured. Define the safe order of operations and how the receptionist explains uncertainty. The caller should know whether the original remains valid, a new booking is confirmed or staff need to resolve a partial change.
Workflow and information contract
Follow the practice approved identity check and locate the authorised appointment. Confirm the requested change and retrieve suitable alternatives under the existing appointment rules. Use a supported atomic reschedule operation where available; otherwise document the practice-approved sequence and recovery. Read back the final confirmed state rather than assuming both operations succeeded.
Acceptance 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 and human handoff
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.
Prepare a VoiceAvo implementation review
Use this guide to prepare a specific VoiceAvo implementation review, not as a promise that every described action is enabled in every account. Confirm the selected telephony provider, supported integration, staff responsibilities and failure path before activation. Begin with synthetic records and approved test destinations. Keep a dated record of expected and actual results, and approve production use only after the business owner has reviewed the evidence. For this workflow, bring the following information: identity result, original booking, permitted change, replacement slot, final confirmed state and recovery owner.
Use a repeatable acceptance checklist
Open the workflow acceptance kit and review the implementation checklist. These are scenarios to run, not claimed product test results.