Give alerts a clear purpose and identity, handle changed appointments and distinguish message acceptance from customer action.
A customer receives three reminders about an appointment they have already rescheduled. Another customer misses an important update because notifications are disabled. Sending more alerts does not solve either problem: the application needs to know which event matters, whether it is still current and what happens when an alert is not seen.
For a Nepal business commissioning a mobile app, notifications should be part of a complete customer workflow. Define their purpose before designing a bell icon or requesting permission. A useful alert has relevant timing, accurate context and an action the user can understand.
Begin with an event rather than a marketing schedule
A hypothetical Butwal appliance-service business wants to remind customers about confirmed appointments. A reminder should refer to the current appointment record, not simply a phone number copied into a campaign list. If the appointment changes, the reminder plan needs to change with it.
Separate essential service communication from optional promotions in the product requirements. Describe what each message is for and how users can manage preferences. Do not treat installing an app as proof that every customer wants every kind of alert.
Illustrative planning scene with conceptual software screens; not real staff or client evidence.
| Requirement |
Question to answer |
| Event and recipient |
Which current record makes this alert relevant? |
| Timing and expiry |
When is it useful and when is it stale? |
| Permission and preference |
What happens if alerts are unavailable? |
| Destination and identity |
Which record opens and how are repeats handled? |
Ask for permission in a meaningful context
Android’s official documentation says Android 13 and higher use a runtime permission for non-exempt notifications. The exact user experience depends on the app and platform conditions. Ask the developer to show how the actual target devices behave, including a denied request.
A sensible product conversation explains the benefit when the user has a reason to understand it. For example, after an appointment is confirmed, the app can explain what a reminder does. Keep the ordinary appointment view usable when notification permission is unavailable; permission handling should not masquerade as a completed business action.
Suggested decision flow. Review the actual software behaviour and approval rules before implementation.
Give each intended reminder a stable identity
Suppose appointment A-071 is scheduled for a hypothetical 20 November 2026 at 14:00 Nepal time. The business plans one reminder at 12:00 that day. On 19 November, the customer moves the appointment to 21 November at 15:00. The suggested workflow cancels or supersedes the old reminder and plans the replacement for 21 November at 13:00.
Nepal time. Invented two-hour reminder policy, not an actual appointment or delivery promise.
This is an invented two-hour reminder policy, not a recommendation for every business or an actual service appointment. The important requirement is that an obsolete event should not remain actionable just because an old alert was queued. Check the latest appointment state before sending and again when the customer opens it.
Conceptual illustration of the underlying decision; no measured outcomes or exact figures represented.
Do not confuse a send request with customer awareness
Firebase’s official Cloud Messaging documentation explains that accepting a message request does not establish delivery to the device. It also documents message lifespan controls for messages that cannot be delivered immediately. Those controls help define expiry; they do not prove that a customer saw or acted on a message.
In a hypothetical test of ten reminder events, eight requests are accepted by the messaging service and two fail before acceptance. Of the eight accepted events, the test records three notification opens and leaves five without an observed open. These categories describe the test’s recorded evidence only.
HYPOTHETICAL / ten intended reminder events. Nested groups are not additive across rows. No observed open does not prove the alert was unseen.
Do not label all eight as “customers notified successfully” or the five as “customers who ignored us”. An open is not proof of attendance, and absence of an open is not proof that an alert was never seen. State which events the implementation can actually observe.
Hypothetical workflow dashboard; not a live WorkSphere screenshot. Nepal time, 2026. Conceptual app state, not a WorkSphere or live device screenshot.
Make the destination useful and discreet
An appointment alert should lead to the relevant current record after the app applies its normal access checks. Avoid including unnecessary personal, financial or service details in lock-screen text. A generic alert can invite the customer to open the app for the details they are authorised to see.
Plan what happens if the appointment has been cancelled, the user is signed out or the record is no longer available. A stale alert should explain the current situation rather than opening an unrelated page. Define any alternative communication route the business needs, without silently sending extra messages through another channel.
Illustrative review scene; any screen shown is conceptual, not a live product screenshot.
Test the exceptions as part of the app brief
Test permission denied, permission later disabled, rescheduling, cancellation, an offline device and a repeated event. Include the expected business result for each case. The goal is one coherent reminder policy, not simply proof that a demonstration phone can display an alert.
If an app connects CRM, service tasks or HR scheduling, identify which system owns the appointment and who resolves conflicting changes. Any proposed WorkSphere integration needs actual verification. Notification software should support the current business record rather than create a separate version of the truth.
Android Notification Runtime Permission
Firebase Set the Lifespan of a Message