What a push has to do in a glance
The push notifications guide describes the format plainly: a title and a line or two, with an optional image, and a deep link that decides where a tap lands. Everything a person needs to decide whether to tap has to fit in what they see before they swipe it away, and they see it at a moment chosen by the app rather than by them. That makes a push closer to a headline than to an email. An email's subject line, as the newsletter design and copy guide explains, competes in an inbox the person opened on purpose; a push interrupts whatever they were doing.
The words carry more weight than in most channels for a second reason. Every push that a person finds useless teaches them to ignore the next one, and some of them will go further and turn notifications off. The push opt-in rateShare of app users shown the notification permission prompt who allowed notifications. the guide describes is earned once and then spent a little with every message, so a badly written push costs more than its own wasted send: it shrinks the audience for every push after it.
Three things make a push worth reading. It is about something that changed for this person, not about the app's wish to be opened. It names the thing rather than gesturing at it. And it tells the truth about what a tap will show. The steps below build those three in, in the order a writer meets them.
The platform rules are few, and this page states only the ones the push guide states. Apple's App Store Review Guidelines say that push notifications must not be required for an app to function and must not be used for marketing unless the person has opted in to receive it. Firebase's documentation describes Cloud Messaging for push, with event-based triggers, as most engagement tools also work. Character limits, truncation lengths, emoji behaviour and rich-media specifications vary by device and setting and are not given here; the preview step replaces them. Everything else on this page is writing practice.
Before you start
Gather four things. First, the trigger: the event or rule that will send this push, and the list of people it can reach, from whoever owns the journey. A push without a clear trigger is a broadcast, and the guide explains why broadcasts should be the minority. Second, the screen the tap will open, with the item or filter it loads, and the fallback for a person who is signed out or whose item has gone. Third, the topic the push belongs to in the app's notification settings, so a person who does not want this kind of message can turn off this kind alone. Fourth, devices: at least one of each platform, with notifications shown on the lock screen, in the notification centre and as a banner, and with any setting that hides previews switched on for one test.
Decide in advance what the push is for, in one action: reorder, reply, book, collect, return to a saved item. That action, measured after the tap, is how the wording will be judged in the last step. If nobody can name it, the push is not ready to write.
The steps
Name the trigger and the person it is for
Write one sentence that says why this person is getting this push now, in their words rather than the team's: "my order is on its way", "the jacket I saved is back", "someone replied to my question". The SMS and WhatsApp automation guide asks for the same sentence before any message is automated, because a message that cannot pass it is an interruption with no reason. If the honest sentence is "the app wants me back", the push needs a better trigger, not better words.
Write the change first
Put what changed for this person at the start of the title, where it is seen even if nothing else is. This is the inverted pyramid applied to the smallest message an app sends: the conclusion first, the supporting detail next, background last or not at all. "Your order is out for delivery" beats "Great news from the kitchen!" because a person who reads only the opening words already has the point. Write the title so it stands alone, and treat the body line as the second most useful fact.
Name the specific thing
Replace category words with the person's own nouns: the dish they order, the item they saved, the person who replied, the class they booked. Specificity is what makes a push read as information rather than marketing, and it is what the app knows that a generic campaign does not. The writing for the web guide makes the same case for pages: specific examples persuade where adjectives do not. If the data to name the thing is not available at send time, fix the data before polishing the words.
Say what the tap will show
A person taps because the push promised something, so say what that is: "see where it is", "open your basket", "read the reply". This is the push's call to actionThe prompt that tells a reader the one action to take next, such as a button or link., and it rarely needs to be a separate phrase; often the title already implies it. What matters is that the promise is concrete enough to be checked against the screen that opens. Avoid promises the app cannot keep for every recipient, such as a price that varies by location.
Match the deep link to that screen
The deep link has to land on exactly the screen the words promised, with the item loaded. The push guide is direct that a push opening the home screen throws away most of its value, and that links need designed fallbacks for signed-out people, missing items and renamed screens. The deep links and app analytics guide explains how links carry campaign parameters into the app, so the analytics can tell which push produced the session, and the deep link test works through every case before a send.
Label offers as offers
If the push is promotional, say so in the words: name the offer, its condition and when it ends, and never dress a discount up as an account update. Apple's review guidelines say push must not be used for marketing unless the person has opted in to receive it, as the push guide states, so a promotional push should only reach people who chose promotional messages, and its wording should not blur the line. Avoid false urgency: a countdown that resets or a "final chance" that returns next week buys one tap and loses trust.
Cut everything else
Read the draft and remove anything that does not help the person decide whether to tap: the app's name repeated in the title when the operating system already shows it, greetings, exclamation marks, filler adjectives, and a second idea. One push carries one message. If two things changed, send the more important one, or wait and send the pair as one summary in the in-app inbox. A good test is to read the title alone and ask whether it still makes sense; then read the body alone and ask whether it adds anything.
Preview on real devices and lock screens
Send the draft to test devices on each platform and look at it where people will: the lock screen, the notification centre, a banner over another app, and a device with notification previews hidden. Check what is cut off, whether the change still leads after the cut, whether the image adds or distracts, and how the push reads in dark mode and at a larger text size. This step replaces any character rule, because what shows depends on the device and its settings, and a preview is the only reliable check. The mobile message send QA checklist puts this preview beside the consent, cap and deep link checks to tick before any push goes out.
Check the timing rules
Confirm the push respects the rules the push guide sets as system rules rather than campaign settings: local time for each recipient, quiet hoursThe hours when promotional texts, WhatsApp messages and push notifications are held for the recipient's daytime, set by law in places and courtesy elsewhere. that hold non-urgent messages until morning, the shared frequency cap across every team that sends, and a priority order in which transactional messages pass and promotional ones wait. Check that the push belongs to the right topic in the notification settings, so a person can turn off this kind of message without losing order updates. Where a person also gets texts, the comparison of SMS and push explains why the same message should not go out on both.
Test wording against the action after the tap
Run an A/B testControlled comparison of two variants. of the new wording against the old inside the holdout structure the push guide describes: random groups for each version and a group that gets nothing. Judge each version on the action the push exists for, measured after the tap, and on its costs: disables, topic opt-outs and uninstalls in the following days. Opens and click-through (CTRShare of impressions that result in a click.) show which line drew attention; the CTR calculator helps compare them, but a push that is opened more and changes nothing has not won. Read the results as the push guide advises, against the holdout, before rolling the winner out.
A worked comparison of the habits above, using the kinds of pushes most apps send. The right-hand column is a pattern, not a template; the specific nouns come from your own data.
| Job | Weak push | Stronger push | What changed |
|---|---|---|---|
| Order update | "Update on your order!" | "Your order is out for delivery. See where it is." | The change leads; the tap is promised |
| Saved item | "Don't miss out!" | "The green rain jacket you saved is back in your size." | The specific thing is named |
| Social activity | "You have new activity" | "Sam replied to your question about repotting." | Person and subject named |
| Reminder | "We miss you!" | "Your Thursday class starts at the usual time. Check in early." | A reason, not a feeling |
| Promotion | "Exclusive deal just for you!!!" | "Offer: free delivery on orders this weekend." | Labelled as an offer, condition stated |
A takeaway app rewrites its order pushes (illustrative)
Spindrel Takeaway rewrites its reorder push
Spindrel Takeaway, an invented takeaway ordering app, sends a Friday reorder push to customers who have ordered at least 3 times and allowed promotional notifications, about 18,000 people a week. The old push reads "Don't miss out! Order now" and opens the home screen. The team rewrites it as "Your usual chicken katsu is a tap away. Open your basket", pulling the dish from each customer's most frequent order, and deep-links it to a basket with that dish already added. It previews both versions on 4 devices and finds that on one phone with previews hidden only "Spindrel" shows, which it accepts. The test runs for 4 weeks: 8,000 people get the old wording, 8,000 the new, and 2,000 get nothing. The old wording's open rate is 6.1% and the new one's 7.4%, but the reorder rate tells the real story: 9.0% of the holdout reorder on a Friday anyway, 9.3% of the old-wording group and 11.2% of the new-wording group. Disables are 0.6% a week for the old push and 0.3% for the new. Spindrel keeps the new wording and drops the old push for customers whose usual dish is no longer on the menu.
The same craft applies to alerts a person asked for, which the back-in-stock and price-drop alerts tutorial builds for email; the mobile messaging hub sets push beside in-app messages and SMS.
If disables keep rising after the wording is fixed, the cause may sit elsewhere in the programme, and the guide to why users turn off app notifications checks the shared cap, broadcasts, topics, quiet hours and routes alongside the copy.
Common mistakes
- Writing the push before naming the trigger. Without a reason this person gets this message now, the push is a broadcast in disguise. Write the one-sentence reason first.
- Leading with the brand or a greeting. The opening words are the only ones everyone sees. Put the change there.
- Category words instead of the thing. "New items" and "an update" tell the person nothing. Name the dish, the item, the person, the time.
- A promise the link does not keep. A push that says "open your basket" and opens the home screen trains people not to tap. Match the deep link to the words and test it.
- Promotions dressed as news. An offer written like an account update breaks trust and blurs the opt-in Apple's guidelines require for marketing pushes. Label offers as offers.
- Trusting a character count over a device. What shows depends on the device and its settings. Preview on real devices and lock screens.
- Judging wording on opens. A more curious line can raise opens and change nothing. Judge on the action after the tap, against a holdout, and count disables as a cost.
