Suspending a reseller and understanding customer impact

Confirm the authorised scope and reason, preserve relevant evidence and record each account’s current suspension state. Arrange a customer communication plan and avoid exposing private billing or security details in public pages.

1. Open View Reseller Usage and Manage Account Status, select the exact reseller and review their account list.
2. Determine whether the reseller’s own main account must also be suspended. The interface provides a separate checkbox for that inclusion.
3. Use the suspension action only for the approved scope. Do not confuse it with the nearby termination action, which removes data.
4. Verify the resulting state of affected accounts and retain the original per-account state record for later recovery.
5. After the underlying issue is resolved, restore only the accounts authorised to resume. Review previously suspended customers before using a broad unsuspend action.

The selected accounts should be suspended without deletion, and the incident record should identify which customers were affected and why. Verify essential recovery access remains available to the administrator.

If only one account is abusive, a targeted account or mail restriction may be more appropriate than reseller-wide interruption. If a broad unsuspend would reactivate independently suspended customers, handle them individually with the server administrator.

No. Suspension and termination are different operations. Read the chosen action carefully and keep a verified backup regardless of the intended temporary restriction.

• Finding the owner, package and resource usage of a WHM account
• Terminating a hosting account after a verified handover
• Customising a WHM suspension page without exposing customer data
• Suspending a cPanel account in WHM

• cPanel: View Reseller Usage And Manage Account Status
• cPanel: What Happens When You Suspend An Account