Channels and preferences

List every notification in one catalogue, ask before marketing, honour each person's choices and quiet hours, and send one message per event.

By Erik Bergstedt, Agent Wranglers. Updated 20 October 2026.

Required

Keep every notification type in one catalogue
Required
Define every notification type once, in code, with its category, allowed channels, default channels and urgency. Sending code accepts only types from that catalogue.
Ask before any marketing message
Required
Send marketing on a channel only after the person opted in to that channel. Keep the proof, and keep marketing out of transactional messages.
Let people choose per type and channel
Required
Let each person turn every notification type on or off per channel, and read those choices at send time.
Send one message per event
Required
Deliver each event to a person on one channel first, and move to the next channel only if they have not seen it. Never send the same news on every channel at once.
Hold messages during quiet hours
Required
Hold every non-critical push and text until the recipient's quiet hours end, in the recipient's own time zone.
Cap how many messages one person gets
Required
Set a maximum number of push and text messages per person per day, and per type per hour. Fold the overflow into a digest or the inbox.
Never text or push customers from test systems
Required
Outside production, send push and text messages only to an allow list of test devices and phone numbers. Drop every other recipient before the provider call.