The design decision
Class bookings involve a specific session, capacity and often a membership entitlement. The assistant must distinguish a class name from a particular occurrence and should not assume that an available place is available to every caller. Define how eligibility and waitlists are checked before enabling automated changes.
Workflow and information contract
Confirm the gym location, class, date and member identity using the approved process. Check the relevant entitlement and remaining capacity. Request one reservation, then read back the confirmed session and any business-approved arrival instructions. When the class is full, offer only the supported waitlist or alternative-session process.
Acceptance 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 and human handoff
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.
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: member verification result, class occurrence, eligibility result, available capacity, reservation ID and next action.
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.