Writing Push Notifications That Don't Get Ignored

CleverTap's 2018 research put the average US smartphone user at 46 push notifications a day. The figure is old and it is US-only, so treat it as an order of magnitude rather than a measurement, but the order of magnitude is the point. Most of those are dismissed within a second. A growing number trigger a permanent opt-out from the app that sent one too many irrelevant messages.

Writing effective push notification copy is a discipline that sits at the intersection of UX writing, marketing copy, and behavioural psychology. Here's how to do it well.

The Four-Second Rule

You have approximately four seconds (the time it takes for a lock-screen notification to appear and disappear) to get a user's attention and communicate enough value for them to tap. Everything about push copy should be optimised for that window.

Your notification needs to do three things in that window: 1. Signal who it's from: the app name or sender 2. Communicate what happened: the triggering event 3. Make tapping feel worth it: a clear reason to open

Title vs Body: Two Jobs

Push notifications have two distinct text fields and they serve different purposes.

Title: Identifies the source and signals urgency level. Usually 30 to 50 characters. Should work as a standalone.

Body: Provides context, detail, and the reason to tap. Usually 60 to 120 characters. Assumes the user has already read the title.

The title should answer in 3 words: what happened? The body should answer: why does it matter to me?

The Personalisation Ladder

Generic notifications get ignored. Personalised ones get tapped. Here's a hierarchy of personalisation effectiveness:

Level 1: Name-only personalisation

"Hi [username], your order shipped!" is better than nothing, but name-only personalisation has become the baseline. Users expect it and no longer find it compelling on its own.

Level 2: Context personalisation

"Your order #[order_id] just left the warehouse, estimated delivery: Thursday." The user can immediately relate this to a real action they took.

Level 3: Behaviour-based personalisation

"You've been using [app_name] for 30 days. Here's what you've accomplished." This refers to user history and actions. Highest open rates consistently.

Urgency Without Manipulation

Urgency works, but only when it's real. "LAST CHANCE" notifications followed by the same offer tomorrow train users to stop believing your urgency signals.

Real urgency: "Your trial ends tonight at midnight. Save your work to keep access." Manufactured urgency: "Act now! This deal won't last!" (it will)

Use time-based copy when there's a genuine constraint. Otherwise, lead with value.

What to Avoid

• Vague triggers: "Something happened in your account". Users will not tap to find out what
• All caps: Reads as shouting; increases dismiss rate
• Guilt-trip copy: "Did you forget about us?" Condescending and trust-damaging
• Duplicate copy: Title and body saying the same thing wastes the body field
• Emoji overuse: One emoji max, used to signal tone not fill space

Channel-Appropriate Tone

Push notifications are not email subject lines. They're closer to a tap on the shoulder from a trusted colleague. The tone should be: - Conversational but efficient: no corporate language - Present tense: "Your transfer is ready" not "Your transfer has been completed" - Direct: no preamble, no "we wanted to let you know"

Testing Notification Copy

Notification A/B testing has a real cost: version B reaches real users who might miss something important. Keep that in mind when designing tests.

Metrics to track: - Open rate: Did they tap? - Conversion rate: Did they complete the prompted action? - Opt-out rate: Did this batch trigger unsubscribes?

A high open rate with a low conversion rate means the copy was misleading. A low open rate with a high conversion rate means you're reaching the right audience but your copy needs work.