Push Notification Strategy: Alerts People Don't Turn Off

A good push notification strategy sends fewer, more useful messages: alerts that the user asked for, that arrive at the right moment and that help them do something they already wanted to do. People switch notifications off, or delete the app, when messages are frequent, generic or purely promotional, so the strategy is mostly about restraint, timing and relevance.

Key Takeaways

• Ask for notification permission after the user sees the value, not on first launch.
• Prioritize transactional and requested alerts (order status, bookings, replies) over promotions.
• Let users choose categories and quiet hours instead of an all-or-nothing switch.
• Send in the user's language and time zone, and keep messages short and specific.
• Measure opt-outs and uninstalls alongside opens, and cut what causes them.

What Makes People Turn Off Push Notifications?

People turn off notifications when the cost of interruption is higher than the value of the message. The most common causes are too many messages, irrelevant promotions, messages at bad times (late at night, during prayer times or work hours) and vague text like "Check out what's new!".

Both Android and iOS now ask the user for permission before an app can show notifications, and both make it easy to silence an app from the notification itself. That means every message is effectively a vote on whether your app deserves a place on the user's lock screen.

When Should an App Ask for Notification Permission?

Ask at the moment the user understands why notifications help them, typically right after an action that creates a reason to be notified. If you ask on first launch, before the user has done anything, many will simply tap "Don't allow", and on iOS you usually cannot show the system prompt again.

A better pattern:

1. Let the user explore the app without any permission request.
2. Wait for a meaningful action: placing an order, booking an appointment, following a store, joining a class.
3. Show your own short screen explaining the benefit: "Get notified when your order is out for delivery."
4. Only if they tap "Yes", trigger the system permission prompt.
5. If they decline, respect it, and offer a way to turn notifications on later in settings.

This "pre-permission" step is standard practice and tends to produce far more opt-ins than a cold system prompt.

Which Push Notifications Should You Send?

Send the notifications that save the user effort or time first, and treat marketing messages as a small, carefully earned extra. Think of three tiers:

• Transactional (always valuable): order confirmed, driver on the way, payment received, appointment tomorrow at 10:00, class schedule changed.
• Requested or personal: a reply to the user's message, a price drop on a saved item, back in stock, a new lesson from a teacher they follow.
• Promotional (use sparingly): new collections, discounts, seasonal campaigns such as Ramadan and Eid offers.

For Afghan businesses, transactional alerts are especially valuable because they reduce phone calls and WhatsApp messages asking "Where is my order?". Seasonal promotions can work well, but plan them as part of a wider campaign; our guide to Ramadan and Eid digital marketing covers timing and tone.

How Often Should You Send Push Notifications?

There is no universal number, but send transactional alerts whenever they are genuinely needed and keep promotional pushes to a level users would not notice as a pattern, often no more than one or two a week for most retail apps. Watch your own data: if opt-outs or uninstalls rise after a campaign, you sent too many or the wrong ones.

Practical frequency rules:

• Cap promotional messages per user per week in your sending tool.
• Never send the same promotion to the same person twice.
• Bundle minor updates into one message rather than several.
• Respect quiet hours in the user's local time zone; diaspora users in Europe, North America and Australia are many hours away from Kabul.
• Pause promotions for users who have not opened the app in a long time, and try email or SMS instead.

How Do You Write a Push Notification People Read?

Write it like a useful text from a person: specific, short and in the user's language. The first few words matter most because lock screens cut long text.

1. Lead with the specific fact: "Your order #2045 is out for delivery" instead of "Update on your order".
2. Use the user's chosen language, and test Dari and Pashto text on real devices so right-to-left text and mixed numbers display correctly.
3. Keep it under about 100 characters where possible.
4. Deep-link to the exact screen the message refers to, not the home screen.
5. Avoid all caps, multiple exclamation marks and fake urgency.
6. Use the person's name or saved item only when it adds clarity, not as a gimmick.

What Tools and Setup Do You Need?

Most apps send notifications through Firebase Cloud Messaging for Android (and often iOS too) and Apple Push Notification service for iOS, triggered from your own backend or a customer engagement platform. The technical setup is a small part of the work; the important part is the logic that decides who receives what and when.

Build these into your backend from the start:

• User preferences by category (orders, messages, offers) and language.
• Time zone and quiet hours per user.
• Event triggers connected to your order, booking or CRM systems.
• Logging of sends, opens, opt-outs and uninstalls.

This is where notifications overlap with automation. Connecting order systems, CRMs and messaging channels is the kind of work covered in our automation service, and it should be planned alongside the app itself. If you are still defining your first version, see what to include in an MVP app.

How Do You Measure a Push Notification Strategy?

Measure whether notifications help the business without damaging retention. Open rate alone is misleading, because an annoying message can still be opened.

Track:

• Permission opt-in rate after your pre-permission screen.
• Open rate and the action taken after opening (order completed, booking confirmed).
• Opt-out rate per message type.
• Uninstalls in the days after a campaign.
• Long-term retention of users with notifications on versus off.

Review these monthly and remove any message type that brings more opt-outs than actions. Push is one channel among several; for longer content and customers who prefer the inbox, combine it with email marketing.

Work With Sheen

Sheen builds mobile apps with notification systems designed around user preferences, languages and time zones, connected to your orders and CRM. Learn more about our mobile app development service or book a call to plan your notifications. Email info@sheen.af or call +93 784 966 018.