Customising a WHM suspension page without exposing customer data

Save the current template and confirm whether you are editing root-owned or reseller-owned pages. Prepare a lightweight design that remains readable without external scripts or images.

1. Open Web Template Editor and select the suspension template tab. Do not accidentally replace the default website or connection-error template.
2. Write a neutral status message and a valid support link. Exclude invoice balances, personal details, incident accusations and internal server information.
3. Use the supported asset locations or documented template URL handling. Keep dependencies minimal so the message still appears when the customer account itself is suspended.
4. Preview the template, save it and test with an authorised disposable suspended account. Check both HTTP and HTTPS behaviour where applicable.
5. Verify the template applies to the intended owner scope and keep the original copy for recovery.

The page should display reliably for the intended suspended accounts and direct the owner to support without implying that every visitor can resolve the suspension.

If the wrong page appears, check account ownership, redirects and the relevant template scope. Use Revert or restore the saved template when necessary. Do not manually patch vendor files or place private account data inside a shared page.

Keep detailed reasons in authorised support and account records. A public page can be viewed by anyone and should not disclose a customer’s billing or security circumstances.

• Suspending a reseller and understanding customer impact
• Applying reseller contact details and branding without changing server ownership
• Finding the owner, package and resource usage of a WHM account
• Restoring a WHM bandwidth allowance without resetting usage

• cPanel: Web Template Editor
• cPanel: Customization