Quiet hours that still allow fraud and account alerts
Silence should feel respectful, not reckless. A practical way to classify which notifications may break quiet hours.
Quiet hours fail when every team invents its own exception. They also fail when security alerts are trapped behind the same silence as promotional tips.
We recommend three classes: must break silence (account takeover, payment failure that blocks access), may delay until morning (feature tips, digests), and batch only (non-urgent marketing). Write the classes into a one-page policy your CRM and product owners both sign.
Review the list quarterly. Product launches tend to sneak promotional alerts into the “urgent” bucket. Timing analytics makes that drift visible before users mute you entirely.