Pushlane Subscription App Push Copy Library

Push notification copy for subscription apps has to do more than earn a tap. It must match the customer's current lifecycle state, make one useful promise and open a destination that can keep that promise.

The examples below are original templates, not observed winning campaigns. Adapt them to your product, offer, store rules and voice. Do not paste a deadline, benefit or account claim until the triggering data proves it is true.

Use this library to draft faster, then test the complete flow: trigger, exclusions, copy, deep link, fallback, localization and exit event.

Apply five rules before choosing a template

Apple describes a notification as timely, high-value information that people can understand at a glance. Its Human Interface Guidelines for notifications are a better baseline than a generic list of power words.

For subscription moments:

1. Name the customer value. Lead with the task, access or problem the person recognizes.
2. State only verified facts. A billing issue is not an expiration. Auto-renew off is not lost access.
3. Give one next action. The tap should open that exact screen.
4. Let the title and body divide the work. The title establishes the moment; the body explains the benefit or action.
5. Stop when the state changes. Copy cannot rescue a stale flow.

Keep placeholders limited to stored, reviewed attributes. Pushlane resolves notification variables at send time and can use an inline fallback. The notification template documentation explains the supported syntax.

Trial activation copy

These messages help the user experience the product before the trial ends. Trigger them from an incomplete value step, not merely from elapsed time.

First useful action

Your first plan is ready

Complete today's setup and see what premium changes for you.

Resume an unfinished setup

Pick up where you left off

Finish {{ next_step | your setup }} to unlock your first useful result.

Feature matched to a stated goal

Try the tool for {{ goal | your goal }}

Open the guided workflow and build your first result in a few minutes.

Verified trial deadline

Your trial ends {{ trial_end | soon }}

Review your plan and finish the feature you wanted to try.

Only use a specific date when it comes from a current, trusted source. Do not compute "tomorrow" from a delayed job that may cross timezones. The trial expiry guide covers deadline logic and stop events.

New paid subscriber copy

The purchase is complete. Move from selling to delivering the premium promise.

Access confirmation

Premium is ready

Open {{ feature_name | your new tools }} and take the first useful step.

First premium action incomplete

Put your new access to work

Start {{ next_action | your first premium workflow }} when you are ready.

Continue from the paywall destination

Continue with {{ plan_name | premium }}

Your saved work is ready in the app.

Avoid "Thanks for buying" as the entire message. It confirms the business outcome without helping the customer. Link to the value they just unlocked. See the post-purchase push guide for the first 24-hour flow.

Healthy subscriber and renewal copy

Renewal messaging should reinforce ongoing value, not create a fake emergency.

Upcoming recurring value

Your weekly review is ready

See what changed and choose the next focus for your plan.

Meaningful progress

You completed {{ milestone | a new milestone }}

Review your progress and choose what comes next.

Renewal confirmation with a useful destination

Your premium access continues

Open this period's plan and keep building from your progress.

Annual value recap

See the value you built this year

Your personal recap is ready, with the next plan waiting inside.

Do not send a generic renewal reminder when the store handles the renewal silently and the customer does not need to act. Use subscription renewal push notifications to decide when a message is helpful.

Billing issue copy

A failed charge needs calm, precise account help. RevenueCat's BILLING_ISSUE event does not by itself mean that access ended.

First notice

Your payment needs attention

Review your App Store billing details to keep premium access uninterrupted.

Reminder while the issue remains open

A billing update may be needed

Check your payment method and current subscription status in the App Store.

Access still available during a verified grace period

Keep your premium access active

Your store is retrying payment. Review your billing details when convenient.

Do not say "your card was declined" unless the store provides that exact, customer-safe fact. Do not claim the subscription was cancelled. Stop on renewal and move to a different state only on verified expiration. The billing issue flow contains the full state machine.

Cancellation and remaining-access copy

RevenueCat cancellation commonly means auto-renew was disabled while access may continue. Pushlane does not currently expose cancel_reason as a flow property, so generic Pushlane flows should avoid cause-specific claims.

Neutral acknowledgment

Your plan settings changed

Review your current access and renewal details whenever you are ready.

Remaining value

Your saved work is still available

Continue with {{ feature_name | your premium tools }} during your current access period.

Support invitation

Need help before your plan ends?

Open support or review your subscription options in the app.

Avoid guilt, countdown pressure and discounts that teach active subscribers to cancel. Exit on uncancellation, expiration or a verified account state that supersedes the flow.

Win-back copy after expiration

Win-back begins after access has actually ended. Use known prior value or a genuine product change.

Return to saved progress

Your progress is still here

Pick up {{ last_goal | where you left off }} and see what is new.

New relevant capability

A better way to {{ goal | reach your goal }} is ready

See the new workflow before deciding whether to return.

Current offer with verified eligibility

An offer is available for your return

Review the terms and restore premium access in the app.

No discount, value-led invitation

Ready for your next plan?

Your history is saved, and the next step is ready when you are.

Do not imply a personal offer when everyone receives it. Do not publish a discount without an eligibility check and valid destination. The win-back push guide explains cohort selection and stop rules.

Localize meaning, not just words

A literal translation can change tone, deadline clarity and the length visible on the lock screen. Review title and body together in every supported language.

Pushlane chooses localization at send time from the stored locale, with exact, script, language and default fallback rules. It never invents a translation during delivery. The localization documentation details the resolution order.

For each template:

• write a complete default-language fallback;
• keep variable fallbacks natural in every language;
• verify dates and plan names use customer-facing formats;
• open the deep link on the localized app state;
• test truncation on real devices rather than relying on one character limit.

Review the flow behind the sentence

Before activation, answer:

1. Which observed event or current attribute makes every claim true?
2. Which event makes the message obsolete?
3. Does the tap open the promised action?
4. What does a missing variable render?
5. Can another active flow send contradictory copy?
6. Is the message allowed by permission, consent and frequency rules?
7. What product or subscription outcome will define success?

Copy is the visible edge of a state machine. Start from the customer moment, adapt one of these templates, and spend as much review time on the trigger and exit as on the words.