Think Build Implement Repeat
London, UK +44 7367 067226
WhatsApp FOLLOW f in X
Mobile Apps

Push Notifications People Do Not Turn Off

Last updated:

You get one chance at permission

If a user declines notification permission, re-asking is difficult and on iOS effectively impossible without sending them to Settings. Almost nobody goes to Settings.

So the timing of the ask matters more than anything else about your notification strategy. Asking at first launch, before the user knows what the app does, is the most common and most costly mistake.

Asking for notification permission on the launch screen is asking a stranger for their phone number before you have said hello.

Ask at the moment of value

Ask when the user has just done something that makes notifications obviously useful: placed an order, booked a slot, started a job, followed something.

  1. Let them use the app first — a session or two
  2. Wait for the action that creates a reason
  3. Explain in one sentence what you will send: “we will tell you when your order ships”
  4. Then trigger the system prompt

Opt-in rates on this pattern typically run two to three times higher than asking at launch, and the users who opt in actually want what you send.

What to send

  • Something about them: their order, their job, their booking, their message
  • Time-sensitive information they would want interrupted for
  • A change in state they are waiting on

What not to send: marketing dressed as an update, engagement nudges because usage dipped, anything sent because a weekly campaign was scheduled. Users cannot tell in advance which notifications are which, so one bad one costs you all of them.

Categories, so it is not all or nothing

Let people choose what they receive: order updates yes, promotions no. Without categories the only control a user has is the switch that turns everything off, and they will use it.

  • Transactional — almost always wanted
  • Reminders — wanted if genuinely useful
  • Social — wanted if the app is social
  • Marketing — off by default, always

Offering the choice also improves the numbers: users who can decline promotions keep transactional notifications on, and the transactional ones are the valuable ones.

Timing and frequency

Respect time zones — a notification at 3am is uninstalled by breakfast. Respect quiet hours. Batch anything that does not need to arrive immediately.

TypeReasonable frequency
Order or job statusAs it happens
RemindersOnce, plus one follow-up at most
DigestDaily or weekly, user's choice
PromotionsRarely, and only opted in

Measure what happens after the tap

Open rate is the obvious metric and the misleading one. Track the disable rate and the uninstall rate after each campaign type — those are the costs, and they are permanent.

A notification with a 20% open rate and a 2% disable rate is losing you future reach every time it sends. That trade is almost never worth it, and it is invisible if you only look at opens.

Frequently asked questions

What opt-in rate should we expect?

Asking at the right moment, 50–70% is achievable. Asking at launch, 20–40% and a worse-quality audience.

Can we send notifications from a website?

On Android, yes. On iOS, only for a site added to the home screen, and opt-in rates are lower.

Should notifications be personalised?

Personal in the sense of being about the user's own activity, yes. Inserting a first name into a marketing message is not the same thing and users notice.

What if someone declines?

Respect it and use email or in-app messages instead. Nagging via in-app prompts is worse than the lost channel.

Keep reading

Considering an app for your business?

Tell us how often a customer would open it. That one answer usually settles whether you need an app or a much cheaper mobile site.

Book a free 30-minute call Get a project estimate WhatsApp us

Related services

What we build for problems like this one

Mobile App DevelopmentCustom Software DevelopmentWeb Development