Notifications that do not annoy your users
How to plan app notifications people welcome, covering useful versus promotional messages, timing, user choice and earning permission.
A notification is an interruption. You are reaching into someone's pocket and asking for their attention, often while they are doing something else entirely. Do that well and you are helpful. Do it carelessly and they will mute you, or delete the app.
The businesses that get this right tend to send fewer notifications than they could, and make each one count.
Useful or promotional?
Every notification falls roughly into one of two groups.
Useful notifications tell the person something about their own activity that they would want to know now:
- "Your coffee is ready at the counter."
- "Reminder: physio appointment tomorrow at 9:15 am."
- "Your plumber is about 20 minutes away."
- "Your order has been delivered."
Promotional notifications serve the business first:
- "We miss you! Come back for 10% off."
- "New autumn menu out now."
- "Have you tried our premium plan?"
There is a simple test. Would the person be glad to have received this, or would they feel sold to? Would they have gone looking for this information themselves? A "your table is ready" message passes easily. A "we miss you" message does not.
That does not mean you can never promote anything. It means promotion should be rare, clearly relevant, and something the person agreed to. Marketing messages are also covered by spam and privacy rules in Australia, including requirements around consent and unsubscribing, so check the official guidance before you plan a campaign.
Earn the permission first
On most phones, an app has to ask before it can send notifications. Many apps ask the moment they are first opened, before the person has any idea what the notifications would contain. The sensible answer to an unexplained request is "no".
A better approach:
- Wait for a moment where the benefit is obvious. Just after a first booking: "Would you like a reminder the day before?"
- Explain in your own words first. A short screen saying what you will send and how often, before the system prompt appears.
- Be specific. "We will only notify you about your bookings" is far more convincing than "Stay up to date".
- Accept a no gracefully. The app should still work. Fall back on email or text for anything essential, such as a booking confirmation.
Once someone has declined the system prompt, getting them to reverse it means sending them into their phone's settings. You effectively get one good chance, so do not spend it on the welcome screen.
Let people choose what they get
"All or nothing" is a poor offer. Someone who wants appointment reminders but not special offers will, if forced to choose, turn everything off.
Give people a simple settings screen with separate switches. For a gym app that might be:
- Booking confirmations and reminders
- Class changes and cancellations
- Waitlist spots opening up
- News and offers
Turn the first three on by default, since they relate to things the person has actively done. Leave "News and offers" off until they opt in.
Keep the list short and the screen easy to find. A person who cannot quieten your app will silence it at the system level, and then you have lost every category at once.
Timing and frequency
A good message at a bad time is a bad message.
- Respect the clock. Nothing non urgent late at night or early in the morning. Remember your customers may be in different time zones.
- Match the lead time to the task. A reminder for a dental appointment is useful the day before and perhaps an hour ahead. A reminder to collect a takeaway order is useful within minutes.
- Bundle where you can. Three messages in ten minutes feel like spam. One summary is calmer.
- Stop when it stops being relevant. A "running late?" prompt after the person has already checked in is just noise.
Frequency is a matter of judgement, and when in doubt, send less. Nobody has ever deleted an app for notifying them too rarely.
Writing the message itself
Most people read a notification on a lock screen in a second or two and never tap it. The message has to make sense on its own.
- Lead with the point. "Your order is ready" beats "Hi Sam, great news from the team".
- Include the key detail. Time, place, amount. "Appointment tomorrow, 9:15 am, at the Main Street clinic."
- Mind what is private. Lock screens can be seen by others. A health clinic should think carefully before naming the type of appointment.
- Send people to the right place. Tapping should open the relevant booking or order, not the app's home screen.
Plan your notifications on one page
Before anything is built, list every notification the app will ever send. It is a surprisingly revealing exercise. For each one, write down:
- What triggers it?
- Who receives it?
- What exactly does it say?
- When is it sent, and are there hours it should be held back?
- Which settings switch controls it?
- What happens when the person taps it?
- Would the person thank you for it?
If the answer to the last question is no, cut it or move it to email, where it can wait politely until the reader is ready. What remains will be a short list of messages people actually value. That is the list to build, and it is the reason they will leave your notifications switched on.