Create the ledger before departure
List four areas: core billing, optional products and usage, workspace or connected-resource access, and outstanding agency work. Assign an owner and expected evidence to each. This original framework is not a claim that one HighLevel control can perform every step. It helps prevent a broad cancelled summary from concealing an active extra or an unfinished client handoff.
Use explicit effective dates
Record when the request was received and when each change takes effect. Some actions may be immediate while others are scheduled. Preserve the source of the observation and any remaining uncertainty. Do not assume a refund, export, transfer or deletion is included simply because the client stops buying the plan; those require their own applicable agreement, product capability and authority.
A fictional completed-and-pending example
A fictional client’s core subscription is scheduled to end on Friday, one add-on is already cancelled and final usage is not yet reconciled. The ledger should say exactly that. The agency can explain what is complete without claiming the whole exit is finished. Keep private account references in an approved system and share only the necessary summary with the appropriate client contact.
Finish with a useful handoff
Confirm the client knows what remains accessible, what stops and which open item still has an owner. Retain records needed for legitimate reconciliation according to the applicable policy; do not collect everything indefinitely just in case. If a provider must clarify an unresolved resource or charge, ask that narrow question. A clean exit is supported by specific results, not merely the absence of an active subscription on one screen. Give each unresolved exit item a named owner and a next action. That lets the agency communicate completed work now without pretending the remaining billing, resource or service dependency has already disappeared.
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
- Resold add-on cancellation — Merchant documentation · help.gohighlevel.com · Merchant-controlled · checked 2026-09-27
- Subaccount bulk actions and history — Merchant documentation · help.gohighlevel.com · Merchant-controlled · checked 2026-09-27