Journal

How to design notifications people don't turn off

A practical guide to deciding which notifications to send, on which channel, and how to write them so people keep them switched on.

How to design notifications people don't turn off

Every product team says the same thing about notifications: we only send the important ones. Then someone adds a weekly digest, marketing adds a re-engagement nudge, a feature launch gets its own push, and six months later people open their phone settings and switch the whole app off. Once that happens, you lose the channel for the messages that actually matter, like a failed payment or a teammate waiting on a reply.

Notifications are a design problem, not just a backend setting. They interrupt someone's day, so each one has to earn that interruption. This guide walks through how to decide what to send, where to send it, how to write it, and how to give people control so they keep notifications on instead of muting you.

Start with an inventory, not a new notification

Before you design anything, list every notification your product already sends. Include push, email, in-app banners, badges and SMS. Most teams are surprised by how long the list is and how many items nobody owns.

For each one, write down four things:

  • Trigger: what event causes it to be sent.
  • Audience: who receives it, and whether they asked for it.
  • Action: what the person is expected to do after reading it.
  • Owner: which team decides whether it keeps existing.

If you can't name a clear action, the notification is probably informational noise. If you can't name an owner, it will never get reviewed. This table becomes the source of truth for every decision below.

Sort messages by urgency and value

Not every event deserves the same channel. A simple way to sort them is to ask two questions: does this need attention soon, and does the person care about it personally?

  1. Urgent and personal (a security alert, a payment failure, a direct message): push or SMS is justified.
  2. Personal but not urgent (a comment on your file, a finished export): in-app notification and an optional push.
  3. Useful but not personal (a product update, a weekly summary): email or an in-app inbox, never push by default.
  4. Neither (we miss you, check out this feature): question whether it should exist at all.

The mistake we see most often is sending category three through the channel reserved for category one. People learn quickly that your pushes are mostly promotional, and they stop trusting the urgent ones too.

Match the channel to the moment

Each channel has a different cost to the reader. A push notification interrupts whatever they are doing. An email waits until they choose to look. An in-app badge only matters when they are already using your product.

Design for where the person is likely to be. If they are already inside the app, show the update in place, next to the thing it relates to, and don't also send a push to their phone. If several events happen within a few minutes, batch them into one message rather than five. Collaboration tools do this well: "Three new comments on Homepage v2" is far less annoying than three separate buzzes.

Respect time and context

Send non-urgent messages during the person's working hours in their own time zone. Offer a quiet hours setting, and respect the operating system's focus modes rather than trying to work around them. A notification that arrives at 2 a.m. teaches people to turn you off, no matter how useful the content is.

Write notifications that can be understood in two seconds

Most people read a notification on a lock screen, at a glance, often mid-task. That leaves room for one idea. Lead with what happened and who did it, and leave out the brand voice flourishes.

Weak: "Hey! Something new is waiting for you in your workspace."

Better: "Maya left 2 comments on Pricing page."

A few rules that help:

  • Put the most specific information first: the person, the object, the number.
  • Avoid vague teasers that force people to open the app to find out what happened.
  • Keep the title and body short enough that they aren't truncated on common screen sizes.
  • Don't use urgency words like "now" or "don't miss" unless something is actually time-sensitive.

Make the tap land in the right place

A good notification can still fail at the moment someone taps it. If it opens the app's home screen instead of the specific comment, file or order, the person has to search for it, and you have wasted their attention twice.

Deep link every notification to the exact place it refers to, with the relevant item highlighted. If the item was deleted or the person no longer has access, show a clear message explaining that, rather than a blank screen or an error. Mark the notification as read once they have seen the target, so the badge count stays honest.

Give people real control

When the only choice is all notifications or none, people choose none. Granular settings keep them subscribed to the parts they value.

  • Group settings by topic, such as mentions, billing, project activity and product news, not by technical channel.
  • Let people choose the channel per topic: push for mentions, email for billing, nothing for product news.
  • Add a mute or snooze option for a specific project or thread, reachable directly from the notification itself.
  • Set sensible defaults. Turn on only what most people need, and let them opt in to the rest.

Also be careful about when you ask for permission. Asking for push access on the very first screen, before someone understands what your product does, usually gets a "no" that is hard to reverse. Ask at a moment when the value is obvious, for example right after someone is assigned their first task, and explain in one line what they will receive.

Measure the cost, not just the clicks

Open rate alone rewards loud notifications. A message can get a high tap rate and still push people to disable notifications or uninstall the app. Track the downside alongside the upside.

  • Opt-out and mute rate per notification type.
  • Notifications sent per active user per week.
  • Time from notification to the intended action, not just to the open.
  • Support tickets or feedback mentioning too many notifications.

Review the inventory every quarter. Retire anything with a high opt-out rate and low action rate, and give each team a budget for how many notifications per week they can add. A limit forces people to argue for the messages that matter.

Conclusion

People don't turn off notifications because they dislike being informed. They turn them off because too many messages were irrelevant, badly timed or impossible to act on. Keep an inventory, match urgency to channel, write for a two-second glance, deep link to the exact item, and let people control what they receive. Do that consistently and your notifications stay switched on for the moments when they really count.

Oybek Ruziev

Designer & Framer developer · AidanCreates

Keep reading

All posts