Real Gym Scenarios
Known workflow improvements
Which risky staff workflows have been clarified or strengthened in this documentation?
Question
Which risky staff workflows have been clarified or strengthened in this documentation?
Steps
- Invalid appointment, class, calendar, trial, and trial-session date windows are blocked before saving.
- Trial-based class bookings now require class trial support, active/scheduled trial status, valid trial date window, and remaining session allowance.
- Checkout collection, payment links, hosted checkout, and terminal collection now reject amounts above checkout total/invoice balance and reject zero-balance invoices.
- Invoice send now gives customers a signed self-serve invoice page with PDF download instead of a relative staff/API PDF path.
- Class scheduling form numbers such as repeat count, reservation limit, and waitlist capacity are normalized before hitting the API, and the API also accepts numeric form strings safely.
- Class create, edit, and duplicate drawers now expose the class level field consistently; edit can also clear the saved level by choosing No level.
- The Person Profile Activity Feed composer now follows the same provider-readiness rule as CRM Inbox: Email, SMS, and WhatsApp are disabled until a connected provider and sender exist, and the send method also blocks unconfigured outbound channels.
- Person Profile invoice delivery actions now use the same provider-readiness checks: Email, SMS, and WhatsApp are disabled and guarded until a connected provider and sender exist.
- Person Profile payment-link Send link now uses the same engagement provider-readiness checks before marking the payment link sent.
- Person Profile payment-link rows now include Copy link so staff can share generated payment URLs manually without requiring outbound messaging providers.
- This help center records these rules in the matching page/scenario sections so staff understand the operational reason, not only the button behavior.
Correct outcome
These items are no longer treated as assumptions; staff can see the expected behavior, disabled state, and correct follow-up action in the help center.