Most ServiceNow notification setups follow a default that emails everyone for everything and trusts users to file Outlook rules. The result is alert fatigue, missed approvals, and an inbox that no one reads. A preference design that gives users meaningful control without breaking compliance changes the relationship from adversarial to collaborative.
Distinguish mandatory from optional
Some notifications must be delivered: legal holds, security incidents involving the user, password resets, approval requests where the user is the only approver. Mark these as mandatory in the notification definition and exclude them from the preference UI. Everything else is fair game for user opt-out. Users tolerate mandatory notifications when they trust that everything else is under their control.
Group by purpose, not by table
Users do not think in terms of “incident.assignment_to” and “incident.work_note_added.” They think in terms of “things assigned to me” and “updates on things I am watching.” Build a preference taxonomy with five to seven user-facing categories and map each notification definition to one of them. Internal complexity is your problem; the user picks from a short list.
Default to digest, not real-time
For non-urgent notifications, default to a daily digest delivered at 8am local time. Real-time delivery should require an explicit user choice for each category. This single change typically reduces individual notification volume by 60 to 80 percent without losing information.
Channel preferences per category
Let users pick channel per category: in-app, email, mobile push, Teams, none. Approval requests might go to Teams while news updates go to email digest. The data model is a u_notification_preference table keyed by user, category, and channel. Notifications check this table at send time and route accordingly.
Quiet hours are non-negotiable
Outside business hours, default to in-app only for non-urgent categories. Users on call should opt in explicitly to off-hours mobile push for incident escalations. Send-anything-anytime systems are how managers stop reading their phones at all.
Respect the unsubscribe link in every email
Every notification email should have a one-click unsubscribe that lands on the preference page with the relevant category pre-highlighted. Hiding the unsubscribe link or burying it in legal text destroys trust. The few users who unsubscribe completely are signaling something useful; let them.
Audit who turned what off
Compliance will eventually ask “did this user receive the notification we required them to receive?” Log preference changes with timestamp, user, category, and old-versus-new value. The log answers the question instantly. Without it, you are reconstructing history from email server logs.
Measure and prune low-value notifications
Track open rates per notification template. Anything below 5 percent open rate over a month is a candidate for deletion or merger. Notifications that nobody reads are training users to ignore the inbox where the important ones also live.
What to do this week: tag your notifications as mandatory or optional, group the optional ones into a small set of user-facing categories, and ship a preference page in the portal.
