Cancellation and Save Offer

When a customer asks to leave, two things matter: understanding why, and respecting their decision. A good save conversation solves the real problem when there is one, offers one fitting option when it would genuinely help, and otherwise makes leaving easy and leaves the door open. The standard: no dark patterns, no repeated offers, no obstruction, every offer within the owner's written rules and the law, and every reason recorded so the business learns.

When to use

• "Acme wants to cancel; reply to them."
• "A customer says we're too expensive and wants to downgrade."
• "Design our cancellation flow and save offers."
• "What can we offer customers who want to leave?"
• "How many cancellations did we save last quarter, really?"

What you need

• The request in the customer's words, and their account: plan, price, tenure, usage trend, open tickets, billing status, contract terms (notice period, minimum term, refund rules). From the helpdesk, CRM and billing (connected apps such as Intercom, HubSpot, Stripe) or the owner.
• The owner's save rules, in writing: which options exist (pause, downgrade, discount, extended trial, free training, a fix), who qualifies, limits (for example one discount per customer, a maximum percentage and duration), and who approves what. If none exist, propose a set (see references/save-playbook.md) and get approval before offering anything.
• The cancellation rules that apply to this customer. They vary by country, by state, and by whether the customer is a consumer or a business. Check with web_search on official sources and cite them. Examples to check:
  • US: the federal ROSCA rules on simple cancellation of recurring charges, and state automatic-renewal laws (some, such as California's, restrict how save offers can be presented during online cancellation). The FTC's 2024 click-to-cancel rule was vacated by a federal court in July 2025, and the FTC restarted rulemaking in March 2026; check the current position.
  • UK: the subscription contract rules in the Digital Markets, Competition and Consumers Act 2024 were not in force at the time of writing. In August 2026 the government said they will come into force in January 2027; the start date has moved more than once, so check the current position.
  • EU: several countries (for example Germany) require an easy online cancellation route. If unsure, the owner decides, with legal advice if they choose.

Method

1. Acknowledge and make leaving clear. In the first reply, confirm you have their request and tell them plainly how and when it will take effect. Never hide the cancellation route, require a phone call where the law or the original sign-up channel says otherwise, or make the customer ask twice.
2. Ask one question about why, as optional: "So we can improve, could you tell me the main reason?" If the reason is already in their message, or obvious from the account (a failed payment, a business closed), do not ask.
3. Diagnose the reason from their words and the account data:
   • Price or budget: the cost is too high for the value they get, or a budget was cut.
   • Not using it, not getting value: low usage, setup never finished, the champion left.
   • Product problems: bugs, performance, reliability, a bad support experience.
   • Missing feature: they need something the product does not do.
   • Switching to a competitor.
   • Temporary or seasonal: a project ended, the off-season, a pause in their business.
   • Business closed, acquired or changed direction.
4. Match at most one option, and only if it fits:
   • Price: right-size first. Help them do what they asked, quickly: a cheaper plan, fewer seats, removing unused add-ons. A discount only within the owner's rules, time-limited, stating its end date and the price afterwards.
   • Not using it: a short working session or training with a concrete goal, or a pause. Not a discount on something they do not use.
   • Product problems: a fix, if it can be fixed now, with a specific plan and date the owner has approved. Be honest if it cannot.
   • Missing feature: be honest about whether it exists or is planned (no promises or dates without the owner); record the request in their words.
   • Competitor: ask what tipped it; offer nothing unless there is a real gap you can close; wish them well.
   • Temporary: a pause or a lower plan until they return, if the owner offers it.
   • Business closed: no offer. Thank them and process the cancellation. Offer once. If they decline, proceed immediately, without a second attempt.
5. Draft the reply for the owner's approval:
   • acknowledge the request;
   • the cancellation details: effective date, what happens to their data, final charges or refunds under the terms;
   • the one option, if any, clearly optional, with an easy way to go ahead with cancelling regardless;
   • an open door. Keep it short and warm. Discounts, refunds, credits and exceptions are decided by the owner.
6. If they still want to cancel, confirm in writing: effective date, last charge, any refund due under the terms, how to export their data and until when, what happens to the data afterwards, and how to come back. Process it only through the proper system, and only after the owner's go-ahead where the owner requires it. Never delete data early.
7. Record the outcome: the reason (category and their words), the option offered, accepted or declined, the final state (saved, paused, downgraded, cancelled), and the revenue impact. Feed missing features and product problems into the product feedback loop, and any process failure (slow support, an onboarding gap) to the owner.
8. Measure honestly. A save counts only if the customer is still active and paying 90 days later. Report saves by reason and option, the cost of discounts, and the 90-day survival of saved customers. If discount saves mostly churn later, stop offering discounts for that reason.
9. Design or improve the process when asked: map the current cancellation path, remove obstacles, write the reason question and the options per reason, set approval limits, and get the owner's sign-off (and legal review if the owner chooses) before changing a live flow.

Worked example

Customer: "Please cancel our subscription. It's too expensive for what we use."

• Account: Business plan, 12 seats, 4 active in the last 30 days; the reporting add-on has never been used.
• Diagnosis: price, driven by paying for unused seats and an unused add-on.
• Option (within the owner's rules): move to 5 seats and remove the add-on, which cuts the bill by more than half from the next invoice. No discount needed.
• Draft: confirm the cancellation will take effect at the end of the current period on 31 October; offer the right-sized plan as one optional alternative ("reply yes and I'll switch it; otherwise nothing more is needed"); explain data export and what happens to their data.
• Outcome logged: price, right-size offered, accepted, active at 90 days (checked on 29 January).

Output

• A reply draft for approval, with the diagnosed reason, the option (or none) and why.
• After the decision: the confirmation draft and a logged outcome.
• For process work: the cancellation path, the reason-to-option table and approval rules (see references/save-playbook.md), plus a quarterly report on reasons, save rate and 90-day survival.

Checks before you finish

• The customer can cancel easily, and the reply says exactly how and when.
• At most one option offered; it fits the reason; it is within the owner's written rules.
• No discount, refund, credit or exception promised without approval.
• The applicable cancellation rules were checked and cited, or flagged to the owner.
• Data handling and final charges are stated correctly; nothing deleted early.
• The reason and outcome are logged.

Pitfalls

• Obstruction. Hidden buttons, forced calls, repeated offers and guilt trips are disrespectful and, in many places, unlawful. They also generate complaints and chargebacks.
• Discount reflex. Discounts do not fix low usage or a bad product experience; they delay the cancellation.
• Arguing with the reason. If they say it is too expensive, help them spend less first; ask questions later.
• Counting fake saves. A save that cancels next month is not a save. Measure at 90 days.
• Losing the lesson. Every cancellation reason is free research. Record it in their words.

See also: churn-risk-signals, support-ticket-reply, product-feedback-loop.