Notification Design: Informing Without Annoying
How to design customer notifications: channel choice, frequency, timing, preference management and internal alerts.
Every notification spends part of your customer’s attention. That budget is limited and does not come back: a channel once labelled “always irrelevant” can no longer carry the message that genuinely matters.
Which events deserve a notification?
A simple filter: if the customer does not learn this, will they miss an action or worry?
- Deserves one: order status changed, appointment approaching, payment failed, ticket resolved, an action needs approval.
- Does not: the system was updated, a new blog post went live, “we miss you”.
- Depends: campaign messages — only with consent and only to the relevant segment.
Choosing the channel
SMS
Critical and time-sensitive. It always arrives but costs money and has little room. Verification, appointments, delivery.
Where interaction is needed. Confirm/cancel buttons, two-way conversation. Factor in the 24-hour rule and template approval.
Documents, detail, information that needs archiving. Invoices, contracts, long explanations.
In-app
Non-urgent information that should still be seen. It does not interrupt because the user is already there.
A common mistake: sending one event through three channels at once. Someone who receives the same information by SMS, email and WhatsApp has not been informed — they have been annoyed.
Timing
- Only genuinely urgent notifications should go out outside working hours.
- Bulk sends should be scheduled in the recipient’s time zone.
- If several notifications would reach the same person in quick succession, combine them into a digest.
- For reminders, a “one far, one near” pair works better than a single early one.
Preference management
The best notification policy gives the user control. Three levels are enough:
- Channel preference: email me rather than texting me.
- Type preference: I want transactional notifications, not campaigns.
- Frequency preference: a daily digest rather than instant alerts.
Opting out must be one click away and processed immediately. A hard-to-find unsubscribe link raises complaint rates directly.
Internal notifications need design too
The same discipline applies to alerts sent to your team. Notifying everyone about every new lead quickly produces a stream nobody reads. A healthier approach:
- Send the notification only to the owner.
- Send managers a digest rather than instant alerts (daily or weekly).
- Let urgency decide the channel: a ticket approaching an SLA breach deserves a phone notification; a new comment does not.
- Make notifications actionable; if clicking does not take you to the record, the job is half done.
Measurement
- Open/read rate: a decline points at content or frequency.
- Opt-out rate: the health indicator of the channel. If it rises, stop immediately.
- Post-notification action: how many clicked, and how many completed something?
- Notification-driven tickets: “what does this message mean?” requests show the wording is not understood.
Frequently asked questions
Do transactional notifications require consent?
Order, appointment and invoice notifications generally fall outside commercial message rules — but adding a promotional sentence brings them into scope. Keeping the distinction matters.
How many notifications are too many?
There is no fixed number; the opt-out rate tells you. If it rises noticeably after a campaign, you crossed the line.
Does personalising notifications really matter?
Adding a name is superficial personalisation. The real difference comes from the notification being about that person: their order, their appointment, their request.
Next step: to see how notification rules are defined, request a demo.