The regular giver retention guide: keeping donors who try to cancel

Every month, some of your recurring donors click "cancel." Most fundraising teams treat that moment like any other churn event. That is a mistake. A voluntary cancellation request is a different problem from a failed payment, and it is a different problem from a cold prospect who never gave. It deserves its own playbook, its own offers and its own scorecard.

This guide explains why, and shows you how to build a save discipline that protects recurring revenue you have already earned.

What is sustainer save optimisation?

Sustainer save optimisation is the practice of keeping monthly donors who have actively asked to cancel. It covers the save offer you present at the moment of cancellation, the reason you capture when they leave, and the win-back sequence you run afterward.

It is not dunning. Dunning recovers gifts lost to an expired card or a failed charge. The donor did not choose to leave. It is also not acquisition. Acquisition converts strangers into first-time givers. Save work starts with a committed donor who is trying to walk out the door.

These three jobs can look similar on a churn dashboard, but they are not the same work and they should not share the same response.

Why voluntary cancellation needs its own discipline

Dunning, acquisition and voluntary saves fail for different reasons, so they need different fixes. Treating them as one bucket hides the real problem and wastes effort on the wrong fix.

Here is how the three compare.

The intent is the key difference. A dunning donor wants to stay, while a cancelling donor wants to go, so you cannot win one back with a tactic built for the other. A card-update email does nothing for someone who thinks your mail arrives too frequently.

Voluntary cancellations also carry more signal. The donor is telling you something about price, trust or frequency. Code that signal well and it improves your whole programme, not just the save.

How to design save offers: pause, reduce, redirect

A good save offer gives the donor a smaller step than quitting. The goal is to keep the relationship alive, even at lower value, instead of losing it to zero. Three offers do most of the work.

Pause. Let the donor stop payments for 1 to 3 months and restart automatically. Pause suits donors facing a short-term money squeeze. It beats cancellation because the gift resumes without a fresh ask.

Reduce. Offer a lower monthly amount. A donor giving £50 who drops to £20 is worth far more than a lapsed donor worth nothing. Reduce suits price and value objections.

Redirect. Move the gift to a different programme, cause or frequency. Redirect suits donors who still believe in the mission but have cooled on the specific appeal.

Match the offer to the reason. Show pause to someone citing money. Show reduce to someone citing cost. Show redirect to someone citing the cause. A single generic "please stay" offer leaves money on the table.

How to code exit reasons so the data is useful

Exit-reason coding is a short, structured list of why a donor cancelled, captured at the moment they leave. It turns a vague loss into a signal you can act on.

Keep the list short and mutually exclusive. Five to seven reasons is plenty:

• Cost or affordability

• Too many contacts or fatigue

• Lost trust or unhappy with the charity

• Life change, such as moving or illness

• Prefers a one-off gift

• Supporting a different cause

• Other, with a free-text box

Use the codes two ways. In the moment, the reason picks the save offer. Over time, the pattern tells you what to fix upstream. If a quarter of exits cite contact fatigue, the problem is your contact plan, not your save page. Reason coding is the bridge between saving one donor and fixing the leak.

How to sequence delayed win-back

Not every donor will accept a save offer. That is fine. A cancellation is not the end of the relationship unless you treat it that way. Delayed win-back is a planned sequence that invites a lapsed sustainer back weeks or months later.

Timing matters here. Reaching out the day after someone cancels feels tone-deaf, so a few weeks of space works better, and the right gap depends on the exit reason they gave you.

A simple sequence looks like this:

1. Honour the cancellation cleanly and thank the donor. No guilt, no friction.

2. Wait. Give money and emotion time to settle, often 30 to 90 days.

3. Reconnect with impact, not an ask. Show what their past gifts achieved.

4. Make a fresh offer suited to the exit reason. Offer a one-off gift to a price-sensitive leaver, or a new programme to someone who cooled on the old one.

5. Suppress donors who ask for no contact, and respect it fully.

Tie the sequence to the reason code. Someone who left over cost needs a different path back than someone who had a life change. A generic win-back blast treats them the same and underperforms.

How to measure save rate separately from conversion and churn

If you fold saves into your overall churn rate, you cannot see whether your save work is paying off. You need a clean metric.

Save rate is the share of donors who requested a cancellation and were kept as active givers, through any offer. The formula is simple:

Save rate = donors saved / donors who requested to cancel

A donor counts as saved if they pause, reduce, redirect or simply agree to stay. Decide upfront how to treat a reduced gift. Many teams track a pound-weighted save rate too, so a saved £50 donor counts for more than a saved £10 donor. Both views are useful.

Keep three metrics apart:

• Save rate measures how well you keep donors who tried to leave.

• Conversion rate measures how well you turn prospects into donors.

• Churn rate measures how much of your base you lose over a period.

They answer different questions. A healthy conversion rate can hide a weak save rate. A churn number alone never tells you whether the loss was a dead card or a donor choosing to leave. Report save rate on its own, alongside recovery rate for dunning, and you can finally see which leak to fix first.

Practical takeaways

• Separate voluntary cancellations from payment failures and acquisition. They have different causes and different fixes.

• Build three save offers: pause, reduce and redirect. Match the offer to the stated reason.

• Capture a short, structured exit reason every time. Use it to pick the offer and to fix upstream problems.

• Run delayed win-back on a planned schedule, keyed to the exit reason, not a same-day scramble.

• Track save rate as its own metric, in both donor and pound terms, next to conversion and churn.

The payoff

A sustainer you save is revenue you already paid to acquire. Keeping that donor costs far less than replacing them. When you give voluntary cancellations their own offers, their own reason codes and their own scorecard, you stop guessing and start protecting the recurring base you worked hard to build.