Choose a monitored contact outside the server’s own failure domain where practical. Define who responds to urgent events and protect webhook or messaging credentials as secrets.

1. Review contact details in Basic WebHost Manager Setup. Confirm the administrative addresses and supported communication destinations are correct.
2. Open Contact Manager > Communication Type and choose which importance levels each destination receives.
3. In Notifications, review event priorities for backup failures, transport errors, disk pressure, update failures, certificate expiry and significant account changes.
4. Save the configuration and use the available test action for supported active communication types. Verify the actual destination receives it.
5. Document an escalation owner and periodically review delivery, especially after staff, mailbox or webhook changes. Keep routine notices distinguishable from urgent incidents.

Critical events should reach a responsible person through a working route, while routine notifications remain manageable. Confirm the event’s priority and destination threshold combine to permit delivery.

If alerts are missing, check recipient configuration, disabled communication types, event priority and outbound delivery logs. Contact Manager governs root-level server notifications; a reseller’s personal contact settings are a separate account configuration.

Use a destination monitored by the person or team responsible for the alert. An address that exists but is never checked is not an effective notification route. For critical infrastructure, consider whether that address remains reachable when the server itself has an email problem.

Review the notification categories and priorities in WHM. Choose settings appropriate to the services you administer and test delivery through the supported method. Record the sender identity and check filtering at the receiving mailbox.

How should I reduce notification noise?

Investigate recurring causes first. Muting a warning can hide a real condition without fixing it. Where a lower-priority notification is unnecessary, document the decision and keep critical categories assigned to an owner.

Update contacts when staff or responsibilities change. Keep an escalation route and a record of when it was last tested. If you administer a server service with our assistance, share the relevant warning and the agreed responsibility rather than forwarding an entire stream of unfiltered alerts. Remove secrets, tokens and unrelated customer information from diagnostic attachments.

Keep critical failures enabled and adjust lower-priority routing or event importance deliberately. A quiet inbox is not evidence that backups, renewals and updates are healthy.

• Investigating a failed WHM backup job
• Reading AutoSSL logs for a domain-validation failure
• Choosing a cPanel update policy and maintenance window
• Changing a WHM server hostname with DNS and certificate checks

• cPanel: Contact Manager
• cPanel: Basic Webhost Manager Setup