# Lead with value, not pressure

- **Canonical URL:** https://playbook.affpartners.io/en/practices/push-value/index.html
- **Markdown version:** https://playbook.affpartners.io/en/practices/push-value/index.md
- **Module:** Push notifications
- **Time:** 75 minutes for the revision

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.

## Outcome

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

## 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 copy:** An export of recurring and triggered pushes with the audience, send condition, and frequency.
- **Destination screens:** Links or test deep links to verify every promise after the tap.
- **Reviewer:** The product or content owner plus a support representative to check facts, conditions, and clarity.

## Terms in plain language

- **Push notification — A short app message shown outside the app:** Definition: It appears on the device and can return a user to one specific useful action. It is sent only when the user has granted notification permission. Example: A message about a new item in a saved topic opens that item through a deep link.
- **Analytics event — A record of a specific user action:** Definition: The app sends an event when a user opens a screen, taps a button, or completes an action. Example: registration_started and registration_completed reveal how many people abandon registration.
- **Deep link — A link to a specific app screen:** Definition: After a tap, the user lands in the promised journey rather than on the home screen. Example: A push about a saved lesson opens that lesson directly.
- **CTA — The main action offered to the user:** Definition: A CTA is a button or link with a clear next step and expected outcome. Example: “Continue registration” is clearer than “Next”.

## 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.

## 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**
  - **Source:** Take the five most frequent or widest-reach messages and add the send condition, the audience, and the result after the tap.
  - **If access is unavailable:** If there is no export, collect the texts from the team calendar and test notifications on a device.
- **The screen after the tap**
  - **Source:** Walk every deep link and compare the push title with what is actually visible on the first screen.
  - **If access is unavailable:** Without a direct link, write down the manual route and do not promise an action the user cannot reach quickly.
- **Complaints and opt-outs**
  - **Source:** Find the wording that was followed by more opt-outs, complaints, or “what is this message about?” questions.
  - **If access is unavailable:** 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

1. **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.
   - **Example:** “Come back now!” — inactive for 7 days — sent daily — home screen.
2. **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.
   - **Example:** The verification result is ready; material appeared in a saved topic; the application status updated.
3. **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.
   - **Example:** “Your verification result is ready — open the status and the next step.”
4. **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.
   - **Example:** One CTA — “Open the result,” not “Open, explore, and top up.”
5. **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.
   - **Example:** 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.

## 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.

## Safety and constraints: 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.

## Key rule

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

---

- [HTML version](https://playbook.affpartners.io/en/practices/push-value/index.html)
- [All practices](https://playbook.affpartners.io/en/)