Run a focused release acceptance check
Verify the customer journey and recovery path before treating an update as ready.
- A disposable test workflow and a recent verified backup.
Step-by-step walkthrough
- 01
Record the running release, known changes, backup location, and rollback procedure. Confirm that rollback remains valid after any new live writes.
- 02
Test a visitor message, an authorized staff reply, a private note, and an attachment. Confirm the private note stays out of the visitor view.
- 03
Convert a disposable chat to a ticket, inspect its reference and history, and exercise the intended close or reopen workflow.
- 04
Test onboarding and recovery emails in owned mailboxes. For every enabled channel or AI provider, record a real delivery test or explicitly mark it untested.
- 05
Review representative desktop and physical mobile journeys. Check keyboard behavior, scrolling, uploads, and roles rather than assuming a successful homepage check covers them.
- 06
Confirm backup verification, alert delivery, and the external availability check. Keep a list of unresolved blockers with an owner for each.
Expected result
A bounded acceptance record with explicit remaining limitations.
Important details
A passing HTTP readiness endpoint is one signal, not a complete security, recovery, or commercial launch signoff.
Need help with this workflow? Contact the team and include this guide’s title.