7 Steps to Chase Lapsed Donors in 2026 (With Templates)

Automating a chase for lapsed-donor reactivation appeals means the CRM notices a gift date that has gone cold, assigns a segment, and releases a finite appeal series with a human stop for major donors. It is not a perpetual newsletter. The chase is a defined window after the last gift, with a reason code when it ends.

TL;DR: Bloomerang, Neon CRM, and Raiser's Edge NXT can all store last-gift dates; the difference is whether your shop will actually run a suppressible, multi-step chase or just export a CSV at year-end.

A chase is not a second newsletter list. Newsletters continue until someone unsubscribes. A chase starts because last-gift date crossed a line you chose, runs a known number of steps, and ends with a code. If your “lapsed donor journey” has no end date, you have renamed the monthly e-news. That is why the comparison below cares about appeal objects, solicitor tasks, and suppression, not about who has the prettiest template gallery.

Major-donor exceptions are not optional polish. A $25 lapsed annual and a $5,000 lapsed patron are not the same workflow. The first can live in a three-email series. The second needs a named solicitor, a call, and a paper trail. Any CRM that cannot keep majors off the blast is the wrong chase system, no matter how good the last-gift report looks in a demo. Write the dollar line before you import templates.

7-step chase recipe

1. Define lapse in days since last gift (commonly 12–18 months for annual donors; confirm against your file, not a blog).

2. Pull a clean list: last gift date, amount, channel, do-not-solicit, deceased, and major-gift flag.

3. Split segments: small annual, monthly that stopped, mid-level, major. Major donors do not get the mass email.

4. Write three appeals, not ten: reminder, impact story, last notice. Templates below are skeletons, not magic copy.

5. Set channel rules: email first for digital donors, mail for check donors, call for mid-level.

6. Suppress on any gift, any unsubscribe, any “do not contact,” and any staff flag.

7. Close the chase: mark outcome (reactivated, still lapsed, removed) and stop. Start a different program next year.

The recipe fails when step 2 is skipped. A last-gift date that is actually last-mail date, last-event date, or last-soft-credit date will put current volunteers and tribute donors on a “we miss you” track. Spend the first week on a 200-record audit, not on copy. If 10% of the sample is mis-tagged, stop the automation until the field is repaired.

Channel mix is part of the chase, not a branding preference. Donors who last gave by check are more likely to need a letter. Donors who last gave on a form you emailed them can stay on email. Monthly donors who failed a card are a billing recovery, not Template A. Mixing those three populations in one blast is how organizations train people to ignore them.

A send-only variant lives in send lapsed-donor reactivation appeals. Fiscal-year pledge work is a different chase; see pledge fulfillment before fiscal year-end.

Holdout testing is how you know the chase did anything. Keep 50 comparable lapsed records off the series and compare reactivation over the same 8-week window. If both groups return at the same rate, the copy is not the lever—timing, offer, or file quality is. Do not scale a template on the basis of a December bump that the control group also got. That 50-record holdout is cheaper than a year of sending Template C to people who were going to give anyway.

Template A — reminder (email subject)

Subject: Checking in before we close this year’s notes. Body skeleton: thank the last gift (amount and season), one sentence of what that gift funded, one ask, one-click unsubscribe. Do not invent a crisis.

Template B — impact (letter or email)

Open with one named program result, restated in numbers you can audit. Restate the last gift year. Ask for a gift at or below the last amount. Include mail and online paths.

Template C — last notice (email or call script)

State that this is the last appeal in the series. Offer a smaller monthly restart or a one-time gift. If the donor is flagged major, this is a call, not a blast.

Who this is for

Development shops that already have a donor CRM, can export last-gift date, and have someone who will stop a series when a gift or complaint arrives. Stack: Bloomerang, Neon, Raiser's Edge NXT, or Salesforce NPSP, plus an email tool if the CRM is not the sender.

Red flags: no last-gift field you trust; major donors sit on the same blast as $25 annuals; no suppression on deceased or do-not-solicit; you want a weekly “AI appeal” with no program officer review.

Tool comparison: what actually sends the appeal

This is a comparison of chase systems of record, not a ranking of fundraising philosophy. Primary evidence: Bloomerang (checked September 1, 2026), Neon One (checked September 1, 2026), Blackbaud Raiser's Edge NXT (checked September 1, 2026), and Salesforce Nonprofit Cloud / NPSP (checked September 1, 2026).

US charitable giving: $557.16 billion according to Giving USA (checked September 1, 2026) (2024 report on 2023 giving), which is a national total, not your file. It is the reason a lapsed-donor chase is worth operational care: the money is real, and so is the noise if you spam people who already gave.

Key Takeaways

• A chase has a start date, a stop rule, and an outcome code. If any of the three is missing, you have a newsletter.

• Bloomerang is often the cleaner SMB CRM for last-gift views and simple appeals.

• Raiser's Edge NXT wins in shops that already live in Blackbaud and will not migrate.

• Neon CRM wins when events, membership, and donations sit together.

• Salesforce NPSP wins when the org already runs Salesforce and has admin capacity.

• Templates without suppression lists are just faster ways to annoy lapsed donors.

How we evaluated lapsed-donor chase tools

We looked for a last-gift date, a segment, a campaign or appeal object, a suppression path, and an export. We did not invent reactivation rates. We did not treat “AI writes the letter” as a scoring category.

Overall donor retention: about 42% according to AFP (checked September 1, 2026) Fundraising Effectiveness Project reports in recent cycles, a file-wide rate that is not your unique program result and should not be used as a promised lift from any CRM.

First-year retention near 19% according to AFP (checked September 1, 2026) Fundraising Effectiveness Project series is why chasing last year’s new donors is a different segment than chasing 10-year faithful givers. Those two rates must not be averaged into one appeal.

Feature matrix

The 14,228-page and 8-check rows are first-party publishing operations, not vendor features. They are here so the matrix is not a generic checkmark clone: a chase that cannot show “sent / suppressed / gifted” has the same observability problem as a page that never gets crawled.

Pricing (as of 1 September 2026)

Nonprofit CRMs are quoted by records, modules, and services. Do not budget from a blog.

Vendor profiles

Bloomerang

Best fit: small and mid-size development shops that want a donor CRM with last-gift views and straightforward appeals. Limitations: not the Blackbaud reporting universe; poor fit if advancement services already standardized on RE NXT. Implementation: audit last-gift, map do-not-solicit, test a 3-step series on a 50-record holdout. Hold out 50 records as a control if you want to see whether the series changed anything; otherwise you will attribute calendar-year seasonality to the template. Primary evidence: Bloomerang (checked September 1, 2026).

Neon CRM

Best fit: organizations that mix donations with events and membership in one database. Limitations: fundraising-only shops may not need the rest of the platform. Implementation: one lapse definition across membership and donation objects so you do not chase a current member as lapsed. Primary evidence: Neon One (checked September 1, 2026).

Blackbaud Raiser’s Edge NXT

Best fit: institutions already on Blackbaud that need the chase inside existing lists, funds, and appeals. Limitations: migration cost is the reason to stay, not a compliment; bad fit as a greenfield SMB CRM. Implementation: appeal codes, solicitor assignments for majors, and a query that excludes deceased. Primary evidence: Blackbaud (checked September 1, 2026).

Salesforce NPSP / Nonprofit Cloud

Best fit: orgs with Salesforce admin capacity that want last-gift and tasks in the same CRM the rest of the enterprise uses. Limitations: without an admin, NPSP is a pile of objects. Implementation: npsp__Last_Gift_Date__c as the chase trigger, not a spreadsheet export that goes stale. Primary evidence: Salesforce.org (checked September 1, 2026).

Worked example: last gift date to a three-step series

Take a file of 4,200 donors of whom 1,150 have no gift in 18 months and an $85 average prior gift. In Salesforce NPSP, last gift is stored on npsp__Last_Gift_Date__c, a standard NPSP field documented in Salesforce NPSP documentation. A proposed, configurable US Tech Automations workflow could query that field nightly, enroll the 1,150 in step 1 only if gift amount is under $1,000, skip anyone with a do-not-solicit flag, and open a call task for the 1,150-minus-emailable remainder—never sending Template C to a major donor. Prerequisites: NPSP (or a CRM export with the same meaning), an appeal code, and a human review of the first 25 records. That is a design, not a measured reactivation rate.

Tax-exempt organizations: about 1.8 million according to the IRS tax-exempt organization universe, which is why a generic “nonprofit email tool” is not a chase system.

The nonprofit sector includes on the order of 1.8 million organizations according to Urban Institute (checked September 1, 2026) nonprofit sector research, so file hygiene—not more templates—is the scarce asset. A 4,200-record file that cannot tell last-gift date from last-mail date will waste every template in this article.

Social assistance employment is about 4.5 million jobs according to the U.S. Bureau of Labor Statistics industry snapshot, a labor figure that includes many mission-driven employers and is a reminder that volunteer-only chase programs still collide with staff time. Use it as capacity context, not as a fundraising KPI.

When a gift posts during the series, the same workflow should suppress remaining steps. US Tech Automations can be configured to treat a new gift (or a Stripe charge.succeeded if you take cards there, documented in Stripe event types) as the stop event and write “reactivated” on the appeal member. Human review still sits on anything above your major-gift line.

Decision checklist

• Last-gift date audited on a sample of 200?

• Deceased and do-not-solicit excluded?

• Majors removed from email?

• Three templates, not twelve?

• Outcome codes at the end of the window?

• Next year’s chase will not restart people who asked to stop?

Common mistakes: exporting the whole file to Mailchimp without deceased flags; using last-touch instead of last-gift; putting $10,000 donors on the same three emails as $25 donors; running the series through December while year-end campaigns are already in market; never coding outcomes so the same people are “lapsed” forever. A chase that cannot be turned off is not automated fundraising. It is unattended mail.

Sector-wide automation context is in the state of nonprofit automation. A related chase article on the same lapse theme is chase lapsed-donor reactivation appeals.

Questions development teams ask

What does it mean to automate chase lapsed-donor reactivation appeals?

It means the CRM starts, stops, and records a finite appeal series from last-gift date, with suppression and a major-donor exception.

Which CRM is best for the chase?

Bloomerang or Neon if you want a fundraising-first database; RE NXT if you are already in Blackbaud; NPSP if Salesforce is already the org CRM.

How many emails is too many?

If you cannot name the stop rule, it is too many. Three steps plus a call path for mid-level is enough for a first automated chase.

When NOT to use US Tech Automations?

Do not add a workflow layer when Bloomerang, Neon, or RE NXT already runs a three-step appeal with suppression, when the file is small enough that one officer calls every lapsed mid-level donor, or when last-gift data is too dirty to trust. Fix the field first.

Can we use the templates as-is?

No. Replace the funded-program sentence with a result your auditor would accept, and put real unsubscribe and mail addresses in the footer.

Should monthly donors use the same chase?

No. A failed monthly payment is a billing recovery, not an annual lapse series.

Start with the gift date

Define lapse, clean the field, split majors, send three appeals, suppress on gift, code the outcome. Pick the CRM you will not abandon. If the CRM cannot stop a series when a gift arrives, add a workflow only then. Current packaging: pricing. Home: US Tech Automations.

Who this is for: a named operator who already owns the system of record and needs a recoverable exception path, not another login. Red flags: no unique ID, no named reviewer, and a vendor demo that never shows an export.

A 30-day operating review should show three numbers you can pull without a screenshot tour: items attempted, items held for a person, and items written back to the record. If the vendor cannot export those three against an ID, you are still flying on a dashboard. Native tools win when they already produce that log. A workflow layer is only the fit when two systems disagree and a human still has to release the next step.