Suspending and terminating reseller accounts (the right way)

Suspending and terminating client accounts is the unglamorous side of running a reseller hosting business. Done well, it protects your resources, recovers payments, and minimizes churn. Done poorly, it creates legal exposure, lost data complaints, and reputational damage. This article covers when to suspend, how to suspend cleanly, and the difference between suspension and termination.

Suspension vs. termination: know the difference

  • Suspension is reversible. The account, files, databases, and email all stay on disk — the website just stops serving and the client can't log in. Used for: non-payment, AUP violations under investigation, abuse complaints under review.
  • Termination is destructive. The account, all files, all databases, all email are deleted from the server. Cannot be undone (only restored from a backup). Used for: confirmed AUP violations, long-overdue accounts after notice, customer cancellation requests.

Always suspend first. Termination is the last step, days or weeks later.

Reasons to suspend

Non-payment

By far the most common. If you use WHMCS, automation handles this. Recommended timeline:

  • Day 0: invoice due
  • Day 1, 3, 7: payment reminders
  • Day 7-10: account suspended (with notice)
  • Day 30-45: account terminated (with notice)

AUP / Terms of Service violation

Phishing pages, malware distribution, copyright complaints, spam abuse. Suspend immediately when you have evidence; investigate before terminating. Document what you saw.

Resource abuse

An account hammering CPU/memory and impacting neighbors. First contact the customer; suspend only if they don't respond within 24-48 hours.

Customer cancellation

The customer asks to cancel. Suspend their account 1 day after their paid period ends, give them 7-14 days to download data, then terminate.

How to suspend in WHM

  1. WHM → Account Functions → Manage Account Suspension.
  2. Pick the account from the dropdown.
  3. Optionally enter a Reason — this shows in the account's notes and on the suspension page visitors see.
  4. Click Suspend.

The website now shows a default "Account Suspended" page. The client can't log in to cPanel. Email is paused (queued, not bounced — mail will deliver after unsuspension).

Customize the suspension page

The default page is bland and doesn't direct the customer to do anything. Customize it:

  1. WHM → Server Configuration → Statistics Software Configuration — OR — on newer cPanel: Server Configuration → Tweak Settings → Default Domain Suspension Page
  2. Provide your own URL or HTML to display.

Recommended message structure:

  • Branded header (it's the customer's site visitors who see this, not just the customer)
  • "This site is temporarily unavailable due to a billing or compliance issue."
  • Contact information for the site owner to reach you (NOT a public phone number unless you want unsolicited calls)
  • An estimated resolution timeline

WHMCS automated suspension

WHMCS can suspend automatically based on payment status:

  1. WHMCS Admin → System Settings → Automation Settings.
  2. Find the Suspension Settings section.
  3. Enable Suspend Overdue Services, set the days threshold (we recommend 7-10 days), and write the email template that goes to the customer.
  4. Save.

From now on, accounts that go 7+ days overdue are auto-suspended via WHMCS ↔ cPanel API integration. The cron job runs daily.

Terminate the account

After your timeline expires (30+ days overdue, or AUP violation confirmed):

  1. Take a final backup — in case the customer reappears in the next month asking for their data.
    • WHM → Backup → Backup Configuration — verify the account is included in nightly backups
    • OR generate a manual full backup: Account Functions → Generate/Modify a Full Backup for an Account
  2. WHM → Account Functions → Terminate Accounts.
  3. Pick the account, confirm.

The account is gone. Files, databases, email, DNS — all deleted from disk. Backups remain per your retention policy.

Data retention after termination

Decide your retention policy and document it before you ever need it:

  • Standard: 30 days of backups available on request after termination, then deleted.
  • Generous: 90 days. Better customer perception, more storage cost.
  • Strict: No restoration after termination. Cleanest legally; harder for "I changed my mind" cases.

Whichever you pick, put it in your AUP/TOS so customers can't claim surprise.

Refunds after suspension/termination

  • Suspension for non-payment: no refund (they didn't pay).
  • Suspension for AUP violation: no refund. Document the violation in case they dispute the charge.
  • Customer cancellation mid-period: your call — many resellers prorate, others don't. Be consistent.
  • Mistaken suspension on your part: credit them for the downtime, plus a token gesture (a free month, a tier upgrade for a month). Resellers' worst customers come from feeling wronged.

Communication templates

Pre-write three emails so you're not crafting them in the heat of the moment:

Pre-suspension warning (Day 5)

"Hi NAME, your invoice INV### was due DATE and remains unpaid. Your account will be suspended in 2 days if not paid. Pay now: [link]. Reply to this email if there's a billing issue."

Suspension notice (Day 7)

"Hi NAME, your account has been suspended due to non-payment. Your data is preserved. Pay your invoice [link] and reply to this email; we'll restore service within 1 business hour."

Pre-termination warning (Day 25)

"Hi NAME, this is the final notice before account termination on DATE. After termination, restoration is not guaranteed. To avoid termination, pay your invoice now: [link]."

Tone: professional, factual, no judgement. The goal is to recover payment, not punish the customer.

  • reseller, suspension, termination, WHM, WHMCS
  • 0 Utilizadores acharam útil
Esta resposta foi útil?

Artigos Relacionados

Setting up private nameservers for white-label reseller hosting

If you're running a white-label reseller hosting business on ipxcore, your clients should never...

Creating hosting packages in WHM

A "package" in WHM is a template that defines what every cPanel account created from it can do:...

Resource limits and overselling: avoiding disasters as a reseller

"Overselling" gets thrown around as a dirty word in hosting, but every reseller does it to some...

Migrating accounts between WHM servers

Whether you're moving a single client from your old reseller plan to your new ipxcore one,...

Onboarding your first reseller client: end-to-end workflow

Selling your first reseller hosting account is exciting. Onboarding it badly is how new resellers...