Apple now lets your app speak at the cancel button. Write the message you'd want to read
Until this month, the moment someone cancelled your subscription in iOS settings belonged almost entirely to Apple. Now you get a few lines on that screen. What you put there says more about your product than any onboarding flow.

Since November 4, 2026, App Store Connect lets you add retention messages to the cancellation flow for auto-renewable subscriptions: text, an image, a suggested plan switch or a promotional offer, with rules for who is eligible and how long to wait between messages. Start with one honest text message per product and locale, add a switch-plan message for people who are paying for more than they use, and request the Retention Messaging API only when you have a server-side reason to choose between messages.
What Apple shipped
On November 4, Apple announced retention messages for auto-renewable subscriptions. When a subscriber goes to cancel, they can now see a short message from you, inside Apple's own cancellation flow. It can include text, an image, or a special offer.
You set them up in App Store Connect, including which subscribers are eligible and how long to wait between messages. For more control there's the Retention Messaging API, a server-to-server service that lets you choose which message each subscriber sees based on their subscription details. Apple describes API access as available by request; the documentation calls it pre-release.
The documentation is specific about where this appears. A subscriber taps Cancel Subscription on the subscription details page. The system then shows a Confirm Cancellation page, with a statement of when service ends, a section from the developer, and two buttons: Cancel Subscription and Keep Subscription. Depending on the message, they may also be able to redeem an offer or switch to a plan you suggest. You upload and configure the messages in advance, per product and locale.
What this screen is for
It's tempting to treat this as a new place to fight churn. That's the wrong frame, and subscribers will feel it.
The person on this screen has already decided once. Respect that, and give them one true reason to reconsider.
Most people cancel for ordinary reasons. They stopped using the thing. They're paying for more than they need. Money is tight this month. They forgot what the subscription included. A good retention message speaks to one of those, honestly, and then gets out of the way. A bad one argues.
Apple's flow keeps Cancel Subscription right there. Your copy can't change that, and it shouldn't try.
There's also a quieter benefit. Writing these messages forces a team to say, in a sentence, what a subscriber actually gets. If nobody can write that sentence without reaching for vague words like "premium experience," the cancel screen is the least of the problems.
Decision guide
A message that helps vs one that pressures
| Consideration | Helps the decision | Pressures the person |
|---|---|---|
| Tone | Names one thing they'd lose, plainly | Guilt, countdowns, or "are you sure?" twice |
| Offer | A cheaper plan that fits how they actually use it | A discount that resets to full price without saying so |
| Accuracy | Only features this subscriber really has | Benefits from a tier they never bought |
| Exit | Cancelling stays one tap away | Copy written to make Keep Subscription look like the only button |
The person on this screen has already decided once. Respect that, and give them one true reason to reconsider.
Four drafts, one for each kind of message
Apple's API documentation names four message types. Here's an illustrative draft for each, written for a hypothetical recipe app. Use them as shapes, not copy.
Text, with bullets. "Before you go, here's what you'd lose: your 214 saved recipes stay, but meal plans and shopping lists stop syncing on the 30th." Specific, true, and it answers the question people actually have: what happens to my stuff?
Text with an image. Same message, with a picture of the thing they made most often. Use an image that reminds, not one that sells. A screenshot of their own saved list would be ideal; a stock photo of a happy family is not.
Switch plan. "Cooking less these days? The Basic plan keeps your recipes and shopping list for less each month." This is the most respectful message of the four, because it offers the subscriber a cheaper way to keep what they use, rather than a reason to keep paying for what they don't.
Promotional offer. "Stay three months at half price." Use it, if at all, when you know the reason is price. Say what it renews at. An offer that quietly resets is a refund request in three months, and a one-star review sooner.
Notice the 214 in the first draft. The number is a placeholder for whatever is true for that subscriber. If you can't make the message true for each person who sees it, keep it general.
Eligibility and wait time
The two settings in App Store Connect matter more than the wording. Eligibility decides who sees a message at all. Wait time decides how often someone can be shown one.
Be conservative. Someone who cancels and resubscribes every few months, chasing offers, shouldn't see a discount every time. Someone who just started a trial and is cancelling before it bills probably doesn't need a speech at all. Write down who each message is for before you configure it, and set the wait time long enough that a returning subscriber doesn't feel targeted.
The API is worth requesting only if your server knows something App Store Connect doesn't: which features this person used, which plan fits their usage, whether they've already had an offer. If you don't have that data cleanly, the static configuration is fine, and much easier to keep honest.
Walk the screen like a subscriber
Before anything goes live, cancel your own test subscription in the sandbox and read the screen as if you were tired, a little annoyed and about to put the phone down. Read each message in every locale you configured. Translations of persuasive copy drift fast; a polite English line can turn pushy in another language.
Check the facts in the message against the plan the test account actually has. If the message promises something a lower tier doesn't include, someone will notice, and they'll notice at the exact moment they were already unhappy.
Then check what happens after Keep Subscription and after Cancel Subscription. If a subscriber takes an offer, does your app reflect the new price and renewal date the next time they open it? If they cancel, does anything in your own app or email flow try to win them back again the same day? One message at the cancel screen is reasonable. Three in one afternoon is a pattern people screenshot.
Sequence of work
From first message to the API
- Week 1
One text message per subscription product and main locale. Set eligibility and wait time conservatively.
- Week 3
Add a switch-plan message for the plan people most often cancel from.
- Week 6
Read cancellations against the messages shown. Rewrite anything that reads as pressure.
- Later
Request Retention Messaging API access only if the server has a real reason to choose.
Who owns it
Retention messages sit between product, marketing and support, which usually means nobody owns them. Give them an owner, by name, in the same document where your subscription prices are written down. That person reviews the messages every quarter, checks they're still true as features and prices change, and reads the support inbox for complaints that mention the cancel screen.
Track the plain things: how many people who saw a message kept their subscription, how many switched plans, how many came back later. Don't count a kept subscription as a win if the same person files a refund request the following week.
If you're building a subscription app and want the cancellation path, plan structure and server side designed together, that's part of our mobile applications work. Talk to TWIMCO.
Related work: Sutton|Place
We build alongside the people doing the work.
Bring us the problem you’re thinking about.