Verified against ChatGPT · 2026-08-10
Respond to a cancellation request with one genuine retention attempt that doesn't read as a script fighting to keep them
Writes a single cancellation-response message that addresses the actual stated reason for leaving, offers only what you're authorized to offer, and lets them go cleanly if the real reason isn't fixable — instead of a generic retention script.
The prompt
Ready to copy — highlighted parts are example details you can swap.
A customer has asked to cancel. Write the response message. CANCELLATION REASON GIVEN "We're consolidating tools and this is the one we use least — nothing wrong with it, just budget cuts." CUSTOMER TENURE 2 years, on the mid-tier plan the whole time. ACCOUNT VALUE $4,200/year, no expansion history. RETENTION OFFER LIMITS Can offer a 20% discount for 6 months or a downgrade to the lower tier instead of full cancellation; nothing beyond that without manager approval. TONE CONSTRAINT They've been a low-friction, easygoing account the whole time — keep it warm and brief, not formal. First, decide whether the stated reason is actually addressable within what you're authorized to offer. If it is (price, a missing feature that now exists, a misunderstanding about how something works), make exactly one specific, relevant offer tied directly to that reason — not a generic "before you go" discount that would apply regardless of why they're leaving. If the stated reason is not addressable within your limits (they've been acquired, they built something in-house, the product genuinely doesn't fit their use case anymore), do not manufacture an offer anyway — acknowledge the reason plainly, make cancellation easy, and close the door respectfully rather than dragging out a retention attempt that has no real chance of working, since a customer who has already decided and is met with a scripted counter-offer anyway tends to leave with a worse impression than one who was let go smoothly. Never ignore the stated reason to pivot to a different, more winnable argument — if they said it's the price, don't respond by selling them on a feature they didn't ask about. Respect the tenure and value context in how much effort the response shows, but do not let account value change whether the retention attempt is honest — a long-standing customer deserves a genuine response to what they actually said, not a more elaborate version of an offer that doesn't address their reason. OUTPUT FORMAT 1. One line stating whether this reason is addressable within the given limits, and why. 2. The message itself, ready to send. 3. If no offer was made, one line confirming that was deliberate, not an oversight.
Customize
Optional — swap in your own details for the highlighted parts above.
Why this works
The instruction to check whether the stated reason is actually addressable before writing anything targets GPT-5.1's default posture on retention messages, which is to always include a counter-offer because "attempt to retain the customer" is the implicit goal it infers from context — left unconstrained, it will produce a discount pitch even when the stated reason (being acquired, building the capability in-house) makes any offer irrelevant or slightly tone-deaf, because the model is optimizing for the shape of a retention email rather than for whether retention is actually plausible here. Requiring the offer to tie specifically to the stated reason, rather than a generic pre-cancellation discount, prevents a specific and common failure of scripted retention copy: responding to a stated reason with an unrelated argument reads to the customer as evidence nobody actually read what they wrote, which is more damaging to the relationship than making no offer at all. The instruction to let the customer go cleanly when the reason isn't addressable, rather than dragging the retention attempt out, matters because a model asked to "try to retain" without this permission to stand down will keep escalating the offer or the persuasion rather than recognizing when persistence has stopped being helpful and started being a mild irritant — decoupling account value from honesty (rather than from effort) closes the version of this failure where a high-value account gets a more elaborate non-sequitur pitch instead of a more honest one.
What you get back
Addressability: not addressable — this is a budget consolidation decision, not a product complaint, so a discount pitch would likely land as tone-deaf. Message: "Totally understand — tool consolidation during budget season is a real thing, and it sounds like this wasn't about anything we did wrong. I've gone ahead and processed the cancellation for the end of your current billing period so you're not charged again. If your needs change down the line, your account history will still be here. Thanks for the two years — it's been a genuinely easy account to support." No offer made: deliberate, since the reason wasn't about price, feature gaps, or fit.
Verified against
ChatGPT GPT-5.1 · 2026-08-10
Changelog
- 2026-08-10 — Initial publish, verified against ChatGPT GPT-5.1.
Need this built into your business?
If a prompt isn't enough — what Scult builds, built and maintained for you — that's Scult's day job.
EXPLORE WHAT SCULT BUILDS
