How to build a subscription cancellation flow that saves customers, with ChatGPT or Claude

Ask cancelling customers one question, match a fair save offer to each answer, and send a 3-email win-back sequence to the ones who leave anyway. You end up with your cancel flow screens and copy, an offer for each reason, the emails, and a short list of numbers to track.

Christian MartinFrom the playbook Create a cancellation sequence that saves subscriptions by Christian Martin ✓ · Updated Nov 19, 2026

What you need

  • Your plans and prices, including any cheaper tier you could downgrade people to
  • What your billing tool lets you do: pause, downgrade, coupon, cancel at end of period
  • Your most common cancel reasons, if you know them (support tickets, past exit surveys)
  • The fastest way a customer can get help (live chat, a booking link, a support email with a reply time)
  • Recent product updates you could mention in a win-back email
  • A spreadsheet to log cancel reasons, offers and results

The steps

  1. Ask one question

    Give the AI your product and your known cancel reasons. Ask for one exit question, "What is the main reason you are leaving?", with 5 or 6 choices: too expensive, not using it, missing a feature, technical problems, switching to another tool, other (with a text box). Check that the choices are short, use your customers' own words, don't overlap, and that there's only one question. A survey longer than that makes people quit and doesn't give you better data.

  2. Match an offer to each reason

    Paste your plans, prices and billing options. Ask the AI to pair each reason with one offer: too expensive gets a downgrade or a time-limited discount (for example 30% off for 3 months). Not using it gets a 1 to 3 month pause. Missing a feature or technical problems gets a fast route to a real person. Switching gets a question about what they found, plus an offer to match it if that makes sense. Other gets a thank-you and help. Check that your billing tool can actually do every offer, and that the discount has an end date and a cap you can afford.

  3. Write each save screen

    Ask for one screen for each reason: a headline that repeats their reason back to them, 1 or 2 kind sentences, a button to accept the offer, and an equally visible "No thanks, cancel" button. Check the copy for guilt trips ("Are you sure you want to lose everything?"), for fine print, and for any extra step between the customer and cancelling. The way out has to be one click away on every screen.

  4. Confirm with care

    Ask for a confirmation screen and email that state the date their access ends, what they keep until then, what happens to their data, and how to come back in one click. Check that the date and the data policy match how your system really works. Leave out any last-minute offer at this point.

  5. Write the win-back emails

    Give the AI your recent updates and a return offer. Ask for 3 short plain-text emails. Day 1: thanks and an easy way back. Day 14: what's new or improved, tied to the reasons people gave for leaving. Day 30: a return offer with a deadline. Check that each email is under 120 words, has a single link, and that people who said "technical problems" or "missing a feature" hear about the specific fix if you've made one.

  6. Route the feedback

    Ask the AI to design a simple log with these columns: date, plan, reason, comment, offer shown, accepted yes/no. Also ask for a monthly summary format for the product team. Each month, paste the comments in and ask the AI to group them into themes and count each one. Check the groupings against the raw comments before you share the top 3 causes.

  7. Track it

    Ask for a one-page tracker covering: save rate by reason, save rate by offer, how many saved customers are still paying 60 days later, win-back rate per email, and the revenue kept. Each quarter, paste in the numbers and ask which offer to change. Check the 60-day number before you call anything a win, because a discount that only delays the cancellation by a month isn't working.

A prompt to start with

You are helping me build a respectful cancellation flow for my subscription business. Never hide the way out or use guilt.

My product: [what it does and who it's for]
Plans and prices: [list plans and monthly prices]
What my billing tool can do: [pause yes/no, downgrade yes/no, coupons yes/no, cancel at end of period]
Most common reasons people cancel: [reasons, or "unknown"]
Fastest way to get help: [live chat / booking link / email with reply time]
Recent improvements: [2-3 updates]
Return offer I can afford: [e.g. 1 month free]

Please give me:
1. One exit question with 5-6 answer choices.
2. One save offer per reason (too expensive: downgrade or time-limited discount; not using it: 1-3 month pause; missing feature or technical problems: fast help; switching: ask what they found).
3. Copy for each save screen: headline that repeats their reason, 1-2 kind sentences, an accept button, and an equally visible "No thanks, cancel" button.
4. A confirmation screen showing what they keep until the period ends and how to come back.
5. Three win-back emails: Day 1 thanks and easy way back, Day 14 what's new, Day 30 a return offer. Each under 120 words.
6. A feedback log layout and the metrics to track: save rate by reason and offer, and the share of saved customers still paying at 60 days.

Paste it into ChatGPT or Claude and put your own facts in the [brackets].

An example of the finished work

Business: Loafly, a $29/month meal-planning app (also $12/month Lite).

Exit question: "What's the main reason you're leaving?" Too expensive / Not cooking much lately / Missing a feature I need / Something isn't working / Switching to another app / Other (tell us).

Save screens:
- Too expensive: "Money's tight. We get it." Keep your saved recipes on Lite for $12/month, or take 30% off for 3 months. [Switch to Lite] [Take 30% off] [No thanks, cancel]
- Not cooking much: "Taking a break from the kitchen?" Pause for 1, 2 or 3 months. You won't be charged and your plans stay put. [Pause] [No thanks, cancel]
- Missing a feature / not working: "Let's fix that today." Chat with Maya from our team, who usually replies in under 10 minutes. [Chat now] [No thanks, cancel]
- Switching: "Mind telling us what you found?" [text box] [Send and cancel] [No thanks, cancel]

Confirmation: "You're cancelled. You keep full access until June 14. Your recipes are saved for 12 months, and one click brings everything back."

Win-back emails:
- Day 1, "Thanks for cooking with us": a one-click restart link.
- Day 14, "We added grocery delivery export": the top-requested feature from the exit comments.
- Day 30, "Your first month back is on us": valid for 7 days.

Tracker (first quarter): 412 cancel attempts, 23% saved. By reason: pause 41%, Lite downgrade 28%, discount 19%. Still paying at 60 days: pause 74%, discount 52%. Top feedback theme: "too many ingredients I don't buy." Sent to product.

The business in this example is made up.

Or hand the whole job to the playbook

Christian Martin wrote these steps as a playbook on Iggy. It runs in your own ChatGPT or Claude, and Iggy gives it the facts of your business, so you do not explain them each time. In the free webinar, we set Iggy up together, in real time.

Mistakes to avoid

  • Hiding the cancel button or adding screen after screen of offers.Show one offer that matches their reason and an equally visible "No thanks, cancel" button. Angry customers leave bad reviews and dispute charges, and several US states and the FTC require easy online cancellation.
  • Offering a discount for every reason.Match the offer to the reason. Someone who isn't using the product needs a pause. Someone with a bug needs help. A discount only fits people who said it's too expensive.
  • Writing a long exit survey.Ask one question with 5 or 6 choices and an optional comment box.
  • Counting a save as a win the moment it happens.Check how many saved customers are still paying 60 days later, and judge each offer by that number.
  • Collecting cancel reasons and never reading them.Group the comments every month and send the top 3 causes to whoever owns the product.
  • Sending win-back emails that don't mention why they left.Segment by reason, and tell people about the specific fix or feature that answers their complaint.

Questions and answers

What does a good cancellation flow look like?

First one exit question, then one save screen matched to the answer, then a clear confirmation that shows the end date and how to come back. Every screen has a visible cancel button. The example above shows one written out in full.

Is a save offer legal, or is it a dark pattern?

Making one relevant offer is generally fine. Problems start when you hide cancellation, force a phone call, or pile on screens. Keep cancelling as easy as signing up was, and check the current FTC and state rules for your business.

How much of a discount should I offer?

Offer only what you can afford for a fixed period, usually 20 to 50% off for 2 or 3 months. Show it only to people who said the product costs too much, and watch whether they're still paying at 60 days.

What save rate should I expect?

It varies a lot by product. Measure your own starting point for one quarter, then improve on it. Pause offers often keep the most people when the reason is that they aren't using the product.

Can I do this without developer help?

Many billing tools, including Stripe, Chargebee, Recurly and Paddle, plus dedicated churn tools, have cancel-flow or pause features you can paste this copy into. If yours doesn't, start by sending the exit question and offer as an email reply to cancellation requests.

How often should I update the flow?

Set it up once, then review it every quarter. Swap out the weakest offer, refresh the Day 14 email with your latest improvements, and act on the top feedback themes.

More how-to guides