Practice 03.03 · Push notifications

Lead with value, not pressure

A useful push answers three questions honestly: what changed, why it matters to me, and what I can do after tapping. Urgency without evidence and promises without a destination erode trust.

Practice outcomeA review table for five messages covering the original problem, verifiable value, improved copy, and matching destination screen.

75 minutes for the revision

In plain language

Fact first, then the benefit and one next step

“Hurry, act now” creates pressure but explains no value. It is better to name the real change — a status is ready, material appeared, progress is saved — and offer one action the user will see after the tap.

What you will need

Active copyAn export of recurring and triggered pushes with the audience, send condition, and frequency.

Destination screensLinks or test deep links to verify every promise after the tap.

ReviewerThe product or content owner plus a support representative to check facts, conditions, and clarity.

Terms in plain language

When to use it

The messages are full of generic calls, fear of missing out, deposit pressure, or promises the destination screen does not confirm.

In plain language

How to verify a promise

Do not judge the copy separately from the event and the screen. A message is useful only when the fact is true and the promised result is reachable.

Campaign history

Take the five most frequent or widest-reach messages and add the send condition, the audience, and the result after the tap.

If there is no export, collect the texts from the team calendar and test notifications on a device.

The screen after the tap

Walk every deep link and compare the push title with what is actually visible on the first screen.

Without a direct link, write down the manual route and do not promise an action the user cannot reach quickly.

Complaints and opt-outs

Find the wording that was followed by more opt-outs, complaints, or “what is this message about?” questions.

Show the texts to five colleagues outside the team and ask them to predict the expected screen and action.

Rewrite the messages around real value

Collect five active messages

Start with the widest-reach, most frequent, or most complained-about messages. Add the audience, the trigger, and the destination screen.

Where to do it: In the communications audit table.
What the result looks like: “Come back now!” — inactive for 7 days — sent daily — home screen.

Name the actual change

For each push, state what really happened in the data or the product. If nothing changed, there may be no useful reason at all.

Where to do it: In the “Fact / trigger” column.
What the result looks like: The verification result is ready; material appeared in a saved topic; the application status updated.

State the personal benefit

Explain what the user can learn, continue, or check. Do not promise income, guaranteed results, or artificial urgency.

Where to do it: In the title and the first line of the new copy.
What the result looks like: “Your verification result is ready — open the status and the next step.”

Keep one clear CTA

The message must lead to one action. Several promises and calls blur the choice and mask weak value.

Where to do it: At the end of the copy and on the destination screen.
What the result looks like: One CTA — “Open the result,” not “Open, explore, and top up.”

Check the copy against the first screen

After the tap, the user must immediately see what was promised. Test the route from a closed app and after sign-in.

Where to do it: On test iOS and Android devices.
What the result looks like: The push about the result opens the verification status, not the home feed.

Practical examples

Before: urgency without a reason

“Come back now!” led to the home page. After the revision: “Your verification result is ready — open the status and the next step,” with a deep link straight to the result.

Before: a promise without the product

“Don't miss your chance” was replaced with a verifiable fact about new material in a saved topic. If the material is not live yet, the push is not sent.

The finished artifact

The “before → after → screen” table

Rewrite five real messages first. Each new wording must be backed by an event and a screen.

Original copy	Problem	New copy	What opens
Come back now!	No reason, just pressure	Your verification result is ready	Result screen
Don't miss your chance	Unverifiable promise	A new analysis in your saved topic	The new material
Top up now	Deposit pressure	Available payment methods changed	Conditions and methods
We have an update	No named benefit	You can now continue from the saved step	Saved progress
Open the app	No action	Check your updated application status	Status screen

Red flag: if the screen after the tap does not show what was promised, the copy cannot be “improved” on its own — fix the route or the product result first.

Write like a product, not an ad

The message should help the user decide, not push them to act at any cost. An unkept promise cannot be fixed with louder wording.

Copy checklist

The message is ready when someone unfamiliar with the task can predict the first screen after the tap.

A real change that has already happened is named. It is clear why the message applies to this specific user. There is one verifiable benefit and one next step. There are no income promises, deposit pressure, or unverified urgency. The first screen after the deep link confirms the push copy.

How to know the copy became more useful

Understanding

After the open, fewer users bounce to the home screen and more reach the promised screen.

Action

Completion of the specific useful action grows — not just the open rate.

Trust

Notification opt-outs, complaints, and negative reviews about pushiness do not grow.

If you cannot show the value on the first screen after the tap, do not promise it in the push.