Push Notifications and In-App Messaging Without Getting Muted

A Permission Is a Loan, Not a Licence

When somebody allows notifications they are making a bet that you will use it for things that matter to them. The bet is settled within a handful of messages, and the outcome is almost always permanent — people who disable notifications rarely turn them back on, and people who delete an app because of them never return.

This makes push unusual among marketing channels. There is no gradual decline you can arrest; there is a threshold, and once someone crosses it your access to them ends silently and without feedback.

Ask at the Right Moment

The single most common mistake is requesting permission on first launch, before the person knows what the app is for. At that moment they have no reason to say yes, so most of them say no, and on most platforms that answer is difficult to reverse.

Ask when the value is obvious instead: after somebody has placed an order and would want delivery updates, after they have followed something they would want to hear about, after they have completed the action the notification would support. The permission rate at that moment is dramatically higher because the request finally makes sense.

Explain Before the System Dialogue

Show your own brief screen first, saying what you will send and roughly how often, with an option to decline that costs nothing. People who say no to your screen are not asked the system question, which preserves the ability to ask them again later. People who say yes arrive at the system prompt already convinced.

Three Kinds of Message, Three Sets of Rules

Transactional messages are the ones the user is waiting for: the order shipped, the ride arrived, the payment failed. These are almost always welcome and should never be batched or delayed for marketing convenience.

Triggered messages respond to something the person did or did not do — an abandoned basket, a saved item back in stock, an unfinished setup. These work well when the connection to their own behaviour is obvious. Broadcast messages go to everybody because the company has something to say, and they are where most permissions are lost.

The Test Before You Send a Broadcast

Ask whether this message is useful to the person receiving it or only to you. A sale that genuinely affects something they were looking at passes. A generic announcement about a brand milestone does not. If a message cannot pass that test, it belongs in the app, not on the lock screen.

In-App Messaging Is Where Most of This Belongs

In-app messages reach people who have already chosen to open the app, which means they cost nothing in goodwill. Anything informational, promotional or exploratory belongs here: new features, tips, offers, surveys.

Reserve push for things that are time-sensitive or that the person is actively waiting for. Treating the two as interchangeable is how apps end up interrupting people to say something that could have waited until the next visit.

Frequency, Timing and Quiet Hours

There is no universal correct frequency, but there is a reliable signal: watch the opt-out rate as you increase volume and stop before it moves. Most teams discover the ceiling is lower than they assumed, and that the messages beyond it produce short-term clicks and long-term losses.

Respect the clock. Send in the recipient’s own time zone, avoid the night entirely unless the message is genuinely urgent, and cap the number of messages any individual can receive in a day across all your campaigns — the cap has to be global, or three teams will each stay within their own limit and collectively be intolerable.

Let People Choose Categories

The alternative to someone disabling everything is letting them disable some of it. Category-level preferences — order updates yes, promotions no — keep the channel you actually need open. Making that setting easy to find looks like an invitation to lose reach and is in practice the thing that preserves it.

Write for a Locked Screen

A notification is read in about a second, out of context, next to messages from real people. It has to make sense on its own: the specific thing, and what it means for the reader. Cleverness reads as noise at that size, and a message that requires the app to be understood has already failed.

Get the destination right too. A notification about one item that opens the home screen forces the person to go looking for what you just told them about, and that small betrayal is remembered next time you ask for their attention.

Personalisation That Is Actually Useful

Inserting a first name is not personalisation. Useful personalisation is relevance: this specific item you looked at, this class you booked, this document you left unfinished. That kind of message is welcome because it refers to something the person already cares about.

It also has to be right. A recommendation based on a misread signal is worse than no message, because it demonstrates that the app understands the user less well than it claims to. Where the data is thin, say less rather than guessing.

Measure the Cost, Not Just the Click

Open rate is a flattering metric because it only counts the people who are still listening. The number that matters is what each campaign costs you in permissions: how many people disabled notifications, muted the app, or uninstalled in the days after it went out.

Report those alongside the clicks, and judge campaigns on both. A message with a strong open rate and a spike in opt-outs is not a success; it is a withdrawal from an account you cannot top up. That is the same discipline we argue for in our guide to analytics that answer business questions.

Retention Is the Real Objective

Notifications exist to bring people back to something worth returning to. If the underlying experience does not reward the return, more messages simply accelerate the churn, which is the argument set out in our guide to mobile app retention.

Consent Is a Legal Question as Well

Platform permission is not the same as consent to market. Rules vary by jurisdiction, and marketing messages generally carry obligations that transactional ones do not — a lawful basis, a record of it, and a straightforward way to withdraw. Keep the two categories separate in your own system rather than deciding later what a message was.

Store the timestamp and the context of each permission, and honour a withdrawal everywhere at once rather than per channel. Where the requirement is genuinely unclear for your market, that is a question for a lawyer rather than a marketing judgement call.

Build It Into the Product, Not the Campaign Calendar

The strongest notification programmes are mostly automated and mostly triggered by user behaviour, with a small amount of editorial on top. That is the opposite of how they are usually run, which is a weekly meeting deciding what to send.

Design the triggered set once — the ones tied to the moments that genuinely matter in your product — and then leave them alone while they compound. If you want that designed alongside the product rather than added afterwards, our mobile team treats messaging as part of the app architecture, because retrofitting it is where most of the damage happens.