Refunded or archived accounts are torn down cleanly

When a signup is refunded, archived or deleted, the CRM sub-account it created is deleted too — idempotently, so a second attempt is not an error.

What it is

deleteSubAccountLocation calls the agency delete endpoint, defaulting to also removing the associated telephony account. A 404 is treated as success so teardown can be re-run safely.

Also called: delete sub-account · cancel signup · clean up after refund

See it
Refunded or archived accounts are torn down cleanly
Area
Integrations
Group
GoHighLevel
System
GoHighLevel
Solves
2 named problems
01Signup is refunded, archived or deleted.
02The location id is passed to deleteSubAccountLocation.
03The delete runs with deleteTwilioAccount defaulting to true.
An admin 'Delete account' confirmation listing what will be removed, including the CRM sub-account. Sample data — no customer information appears here.
How it works
  1. 1Signup is refunded, archived or deleted.
  2. 2The location id is passed to deleteSubAccountLocation.
  3. 3The delete runs with deleteTwilioAccount defaulting to true.
  4. 4404 (already gone) returns ok so callers can treat teardown as idempotent.
Why we built it

The header states the driver — 'used when a signup is refunded/archived/deleted so it doesn't bloat the agency' — and the idempotency choice: 'Returns ok even if the location is already gone (404) so callers can treat teardown as idempotent.'

The problem
  • Abandoned signups left orphaned CRM sub-accounts behind.
  • Re-running cleanup used to error on an already-deleted location.
Sound familiar?
What you get
No orphaned sub-accounts after refunds.
Cleanup can be safely retried.

See it on your own jobs

Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.

or keep browsing features →