Send push notifications that earn their interruption

Design alerts around timely customer decisions, with useful destinations and manageable preferences.

A phone showing one discreet notification beside a train window.

A push notification asks for attention outside the app. That makes it valuable for a changed appointment and expensive for an ordinary announcement. Before adding notifications, decide which event creates a useful action for the recipient and how long that action remains relevant. The business's desire to bring people back is not, by itself, a customer benefit.

Define an event and a recipient

An equipment workshop might notify a customer that a repair is ready for collection. The message should identify the item without revealing unnecessary details on a locked phone, then open the collection instructions. A generic message saying there is an update forces extra searching. Distinguish operational alerts from offers and let customers manage the categories separately where appropriate. Android's documentation explains that notification access depends on user permission and can be revoked. Build the essential service experience so a customer can still discover status when alerts are unavailable.

Handle time and repetition carefully

An appointment reminder sent after the appointment has moved is worse than silence. Define what happens when events change, a customer has multiple devices, or several updates arrive close together. A single current summary may be more useful than a chain of conflicting notices. For businesses serving multiple Australian states, use the appointment's intended local time and make the location clear. Consider quiet periods for optional messages. A transactional event can still be disruptive, so allow reasonable customer preferences without making the underlying information disappear.

Review the experience after tapping

Test a notification from a locked phone, an already open app and a signed-out session. Confirm that the relevant item appears and that an expired action explains what changed. Ask testers to distinguish a notification from a completed transaction; tapping a message should not silently approve a costly change. Evaluate success through the customer task, such as successful collection or fewer missed preparation steps. Opening a notification is only an intermediate event. Also watch opt-outs and support complaints, which may reveal that frequency or relevance has become a problem.

  • What decision becomes easier because this message arrives now?
  • Can the message reveal private information on a shared or locked device?
  • Where does an expired or already completed notification take the customer?
  • Can the customer manage optional messages without losing access to service updates?

Further reading

Discuss your software project with 110s

Related Insight