Push Notifications Done Right: Permission, Frequency and the Rules for Small Businesses

The short answer

Push notifications are short messages your app can show on a customer's lock screen. They work when three things are true: the customer has chosen to receive them, the message is useful to that person, and you send them sparingly. Ask for permission at a meaningful moment rather than on first launch, separate service messages from marketing, and treat promotional pushes as marketing under UK and EU privacy rules.

What a push notification is (and is not)

A push notification is a message delivered through Apple's or Google's notification services to an app installed on a device. It is different from:

• An in-app message, which is shown only while the app is open.
• An email or SMS, which uses a different channel and different consent records.
• A notification badge, the small count on the app icon.

Because pushes appear on the lock screen, they are powerful — and easy to overuse. The quickest way to lose a customer's attention is to send them things they did not want.

Permission: the operating system rules

iPhone

On iOS, an app must request authorisation before it can show alerts, play sounds or set badges. Apple's User Notifications documentation describes this process. Customers see a system prompt once; if they decline, they must later change the setting themselves in the Settings app.

iOS also supports "provisional" authorisation, which delivers notifications quietly to Notification Centre so the customer can decide later whether to keep them. It can be useful for low-urgency updates.

Android

From Android 13, apps must request the POST_NOTIFICATIONS runtime permission before showing notifications, as described on the Android Developers site. Earlier versions granted notifications by default. Android also uses notification channels, which let customers switch off categories — such as "Offers" — while keeping others, such as "Booking updates".

What this means in practice

• You only get one good chance at the system prompt on iPhone. Do not waste it.
• Some customers will decline. Your app must still work, and critical information must be available elsewhere.

Asking at the right moment

The common mistake is asking for notification permission the instant the app opens, before the customer understands why. A better pattern:

1. Wait for a relevant moment. For example, right after a customer books an appointment: "Would you like a reminder the day before?"
2. Explain the benefit in your own screen first. A short in-app explanation ("We'll only send booking reminders and collection updates") before triggering the system prompt.
3. Let them say "not now". If they skip your explanation screen, do not trigger the system prompt yet.
4. Offer preferences. A notifications settings screen where customers choose categories.

Apple's Human Interface Guidelines include guidance on requesting permissions in context.

Service messages vs marketing messages

This distinction matters both for customer trust and for compliance.

Service messages relate to something the customer asked for:

• Appointment reminders and changes.
• Order confirmations, dispatch and collection notices.
• Daycare check-in and pick-up updates.
• Account security alerts.

Marketing messages promote something:

• Offers and discounts.
• New products or services.
• "We miss you" re-engagement messages.
• Events and promotions.

Some messages sit in between — "your loyalty reward expires on Friday" is closely linked to the customer's account but also encourages a purchase. When in doubt, treat it as marketing.

The rules

• Apple's App Review Guidelines state that push notifications must not be required for the app to function, and must not be used for promotions or direct marketing unless customers have explicitly opted in, with an opt-out available in the app.
• UK PECR regulates electronic marketing communications, and UK GDPR governs the personal data involved. The ICO publishes guidance on direct marketing and electronic communications.
• In the EU, the GDPR applies together with national rules implementing the ePrivacy Directive.

In practice: get a clear, separate opt-in for marketing notifications, record it, let customers withdraw it easily in the app, and keep service notifications in their own category. This article is general information, not legal advice.

Frequency: how much is too much?

We will not quote a magic number, because the right frequency depends on your business and your customers. Some principles:

• Service messages: send when needed and not more. One reminder the day before and one on the day is often enough for an appointment.
• Marketing messages: fewer than you think. If you would not interrupt a customer in person to say it, do not push it.
• Quiet hours: avoid late evenings and early mornings in the customer's time zone.
• Watch the signals: opt-out rates, notification settings changes and uninstalls tell you when you have gone too far. Measure these with privacy-respecting analytics.

Segmentation: send fewer, better messages

Segmentation means sending a message only to customers it is relevant to. Simple, useful segments for small businesses:

• By location — only customers of the branch that has availability.
• By service history — only clients due a rebooking.
• By preference — only customers who opted into offers.
• By pet, vehicle or membership — only owners of a specific type of pet, customers with a particular vehicle, members of a particular class.

Segmentation uses personal data, so it must be explained in your privacy notice and kept proportionate. Avoid sensitive inferences.

Writing a good notification

• Lead with the useful bit. "Bella is ready for collection" beats "Update from your groomer".
• Be specific. Include dates, times and names.
• Keep it short. Lock screens truncate long text.
• Link to the right screen. Tapping should open the booking, order or update, not the home screen.
• Avoid fake urgency. "Last chance!" every week teaches customers to ignore you.

The technical side, briefly

Apptavio builds production apps with React Native, Expo and TypeScript. Expo provides a push notification service that works with Apple Push Notification service (APNs) and Firebase Cloud Messaging (FCM) for Android, described in the Expo documentation. A typical setup includes:

• Registering devices and storing push tokens securely against the customer's account.
• Notification categories or channels for service and marketing messages.
• A server or admin tool to schedule and target messages.
• Logs of what was sent, to whom and when.
• Handling of expired tokens and opt-outs.

Delivery is not guaranteed: devices can be offline, notifications can be disabled, and operating systems may throttle delivery. Important information should always be available in the app too.

Checklist

• Have you listed your service and marketing notification types separately?
• Do you ask for permission in context, after explaining the benefit?
• Can customers manage categories in the app?
• Is marketing opt-in recorded and easy to withdraw?
• Does the app work fully for customers who decline?
• Have you set quiet hours and a frequency limit?
• Is your privacy notice up to date?

See it in your own app

Apptavio can prepare a free, personalised, interactive app concept from your existing website, including how notification preferences and updates could look for your business. It runs in a browser and the notifications are simulated, but it helps you decide what you want before development. A person reviews every concept before it is sent, and there is no obligation.