Guide
Handle Cancel Requests in Support: A Voluntary Exit Playbook
When a customer emails or chats “cancel my account,” support becomes the cancel flow. The job is to verify the requester, capture why they are leaving with the same reason codes you use in-product, execute the subscription change in Stripe, and confirm access and billing timing in writing.
Hub: assisted cancellation support. Reason list alignment: SaaS cancellation reasons.
Last updated October 23, 2026
Suggested steps
- Verify account ownership (logged-in ticket, billing email match, or admin policy)
- Ask one structured reason question — same labels as your in-app survey
- Offer a save only when policy allows and fit is plausible — not as a gate
- Process cancel in Stripe (immediate vs period end per your policy)
- Send confirmation with final charge and access end date
Macros without traps
Canned replies should link to self-serve billing when appropriate — subscription billing page for SaaS — and must not hide that cancel is available. When save offers are wrong for the segment, follow when to skip retention offers.
Stripe actions
Document which Dashboard or API path reps use so timing matches self-serve. Reference: scheduled cancellation timing and final billing after cancellation.
Reduce “email to cancel” volume
Clear in-app exit flows deflect tickets while keeping assisted paths for edge cases.