Explain the outcome, not just the button
Write a plain-language route stating how a client requests cancellation, what confirmation to expect and when access or billing changes. Do not describe a survey or contact form as completed cancellation if another action is required. The client should understand what remains active without having to interpret an internal retention label or ask several people the same question.
A specific product boundary
HighLevel’s documented custom cancellation flow can redirect a client to an external page without completing cancellation inside the platform. That distinction needs explicit review if the feature is used. Our editorial recommendation is to keep the exit route clear and accessible, not to hide it or present a deflection as success. Applicable cancellation obligations require separate professional assessment where necessary.
Rehearse with synthetic information
Walk through the configured route using the available safe preview or an authorized non-production case. Check the wording at every decision point: request, offer, confirmation and effective date. Do not create actual charges or cancellations merely to gather screenshots. A preview can validate presentation, but it does not by itself establish that a live client subscription changed or that an external handoff was completed.
Keep proof of the final result
Record the specific subscription, confirmed status and effective time in the approved private system. Inspect extras and unfinished service work separately. If the client leaves an external flow before confirmation, report the real state rather than assuming intent caused cancellation. A respectful exit process is part of operating a dependable service; it should not rely on confusion or unnecessary friction to preserve a recurring payment. Ask a reviewer to identify the exact point where cancellation becomes confirmed. If the page only records a request or sends the client elsewhere, label that intermediate result honestly and explain the remaining step.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- Custom SaaS cancellation flow — Merchant documentation · help.gohighlevel.com · Merchant-controlled · checked 2026-09-27