Skip to content

Lapsed Donor Re-engagement · Nonprofit

Bring lapsed donors back with a personal, approved note

Each month AI finds donors whose last gift was 12–24 months ago and drafts a warm note with real updates from your work. Your development lead approves every batch.

Available now $79 one-time · never renewsIncluded in Enterprise
Get this agent See how it works

Free account to start. Buying and running live need a paid plan.

  • Runs on a schedule
  • 2 AI steps
  • A person approves before it acts
  • About 20 min to set up

Sound familiar?

The job, before and after this agent.

What it feels like today

  • “Donors drift away and we never ask them back.”
  • “Writing personal notes to lapsed donors is always next month's job.”
  • “I'm nervous about emailing someone who asked not to be contacted.”

What you get with the agent

  • On the 1st of every month, reads your donor sheet and finds donors whose last gift was 12–24 months ago.
  • Skips anyone marked do-not-contact, without an email or contacted in the last year.
  • Drafts a personal note: thanks for past support, one or two real updates from the impact you describe and a low-pressure invitation to give again.
  • Your development lead edits or holds any note and approves the batch.
  • Each sent note is remembered for a year and marked in the donor's row, so nobody is contacted twice.

Before

Your lapsed-donor list grows every quarter. You mean to write to them, but there's always a gala or a grant first.

After

On the 1st, a batch of personal notes is waiting. You remove one donor you know personally, approve the rest, and the sheet records who heard from you.

How it works

The whole workflow, step by step.

On the first of every month the agent reads your donor sheet in Google Sheets. The dates are worked out in code: only donors whose last gift was 12–24 months ago and who weren't contacted in the last year go on (up to 200 per run). AI skips anyone marked do-not-contact or without an email, and drafts a personal note: thanks for their past support, one or two real things your organisation has done since (only from the impact you describe) and a low-pressure invitation to give again. The whole batch waits for your development lead, who can edit or hold any note. Approved notes are emailed with replies to your inbox, remembered for a year and marked with the send date in the donor's row, so nobody is contacted twice.

  1. Trigger1st of the month at 9:00
  2. App callRead your donor sheet
  3. LogicCheck the last-gift dates
  4. LogicEach lapsed donor
  5. LogicContacted before?
  6. AI stepDraft the note (or skip)
  7. Human approvalApprove this month's batch
    • Approved:Each approved note
  8. LogicEach approved note
  9. AI stepFinal check on the wording
  10. LogicCheck before sending
  11. LogicSend it?
    • Send:Email the note
    • Hold:Not sent
  12. OutputNot sent
  13. OutputEmail the note
  14. LogicRemember the note was sent
  15. App callMark the donor row
  16. OutputBatch sent

This is the workflow that opens in your workspace when you set the agent up. Every step can be edited.

  1. Step 11st of the month at 9:00Runs on the first day of every month. Set your time zone on the trigger.
  2. Step 2Read your donor sheetReads your donor list from Google Sheets: one row per donor with name, email, last gift date and amount.
  3. Step 3Check the last-gift datesIn code, not AI: works out how long ago each donor's last gift was (in your time zone) and keeps only donors whose last gift was 12–24 months ago (365–730 days) and whose “Reactivation sent” / “Last contacted” cell is blank or over a year old. Change the window here (the tier's min / max days).
  4. Step 4Each lapsed donorDrafts a note for every donor the date check kept (up to 200 per run).
  5. Step 5Contacted before?Looks up whether this donor got a re-engagement note from this agent in the last 365 days (by the Email column).
  6. Step 6Draft the note (or skip)For each donor whose last gift was 12–24 months ago (checked in code), AI checks the do-not-contact notes and drafts a personal note on what their support made possible and what's happened since.
  7. Step 7Approve this month's batchAll of this month's notes wait in Reviews together. Your development lead edits any note, sets send to false on any that shouldn't go out, and approves the batch; nothing is sent before that.
  8. Step 8Each approved noteChecks, sends and records every approved note.
  9. Step 9Final check on the wordingAI reads each approved note for guilt or pressure tactics, the word “lapsed” and AI mentions only — thanking the donor for their gift and sharing your impact are fine. It must quote the exact sentence it objects to.
  10. Step 10Check before sendingIn code: drafted to send, still marked to send after review, exactly one valid email, a row number, a subject and a body with no placeholders left — plus the wording check's verdict. Anything that fails is held, with the reason.
  11. Step 11Send it?Notes that pass every check are emailed; skipped and held ones are kept in the run history with the reason.
  12. Step 12Not sentSkipped by the agent, held by the reviewer or stopped by a check; the reason is in the gate's output.
  13. Step 13Email the noteSends the approved note from your workspace's sender, with replies going to your development lead.
  14. Step 14Remember the note was sentRemembers the donor got a note (for 365 days) so next month's run skips them.
  15. Step 15Mark the donor rowWrites today's date (in your time zone) into the donor's row, in the column you pick (e.g. “Reactivation sent”), so the date check skips them for a year.
  16. Step 16Batch sentThe run history keeps every note that was sent or held.

Example run

What goes in, and what comes out.

Example with fictional data

Comes in

Donor row (fictional): Tom Becker, last gift $100 in March of last year, Fund: After-School Meals, no do-not-contact mark.

The agent produces

Note drafted thanking Tom for his gift to After-School Meals, sharing one update you wrote about the program this year, and a gentle invitation to give again. Waiting in the monthly batch.

What you need

Everything it takes to run it.

About 20 minutes from purchase to live. A checklist above the canvas takes you through each step.

Plan

Included in Enterprise; on other paid plans it's $79 once. Agents run live on paid plans, from Basic ($39/mo).

Your AI key

Connect any of 14 AI providers on your own key. Your provider bills usage directly, at cost; we add no markup.

Apps

Checklist

  • A paid plan (agents run live on paid plans).
  • An AI provider key (Settings → AI Providers).
  • Google Sheets, connected in Settings → Integrations.
  • A donor sheet with an “Email” column and a last-gift date, refreshed from your donor database each month.

Setup, about 20 minutes

  1. Connect your AI provider. The AI steps run on your own key (OpenAI, Anthropic, Google and more). Add one in Settings → AI Providers.
  2. Connect Google Sheets. Connect the Google account that can open your donor sheet (Settings → Integrations → Google Sheets).
  3. Describe your impact and how to give. Open “Draft the note (or skip)” and replace the placeholder with your organisation, signer, impact since last year and giving link.
  4. Pick your donor sheet. Open “Read your donor sheet” and pick the account, spreadsheet and tab (with an Email column and a last-gift date).
  5. Pick where sent notes are marked. Open “Mark the donor row”, pick the same account, spreadsheet and tab, and the column letter of “Reactivation sent”.
  6. Add your development lead's email. Open “Email the note” and enter the address donors' replies should go to.
  7. Test it with Dry Run. Press Dry Run: the agent runs on sample data with no messages sent and nothing written to your apps.
  8. Switch the trigger on. Open the trigger, set your time zone and switch the schedule on. It runs on the 1st of every month — refresh the donor export before then.

Is it a fit?

Who it's for, and what it won't do.

Built for

  • Nonprofit development directors
  • Small charities with a donor spreadsheet
  • Annual fund and individual giving staff

What it doesn't do

  • It never emails a donor before the batch is approved.
  • It drafts up to 200 notes per run (500 rows checked); for bigger lists, point it at a tab of donors whose last gift was 12–24 months ago. Rows whose last-gift date it can't read are skipped.
  • It doesn't read your donor database or payment processor directly — only the sheet you export.
  • It never invents impact figures, stories or matching gifts — only what you write in its settings.
  • It doesn't manage unsubscribes: mark do-not-contact donors in the sheet.

We list the limits up front so you can decide before you buy.

Price

$79 one-time

Per workspace. It never renews.

Available now
  • Included at no extra cost on Enterprise.
  • Buying and running it live need a paid plan, from Basic ($39/mo).
  • Dry Run costs nothing: simulated AI and app calls, nothing sent.
  • AI usage is billed by your own provider, at cost. No AI credits to buy from us.
Get this agent See how it works

One-time agent purchases aren't covered by the 30-day money-back guarantee. Refund policy

FAQ

Questions about Lapsed Donor Re-engagement.

Could it contact someone who opted out?

It skips anyone marked do-not-contact, and nothing is emailed before your development lead approves the batch. Keep unsubscribes marked in the sheet; it doesn't manage them for you.

Will it exaggerate our impact?

No. It uses only the impact you describe in its settings and never invents figures, stories or matching gifts.

How long does setup take?

About 20 minutes: connect Google Sheets, describe your impact and how to give, pick your donor sheet and add your development lead's email.

Is it worth paying for?

It's a one-time purchase that never renews, set against writing re-engagement notes one by one. You need a paid plan and your own AI key; Dry Run is free.

What should the donor sheet have?

One row per donor with First name, Email (a column named exactly “Email”), Last gift date and, if you have them, Last gift amount, Fund, and a Do not contact column. Export it from your donor database each month. Add an empty “Reactivation sent” column for the agent to fill in.

How does it avoid contacting someone twice?

Two ways: it remembers every note it sends for a year (by email address), and it writes the send date into the column you pick in the donor's row. Donors with a recent date there are skipped too.

My donor list is bigger than 200 rows.

The date check reads up to 500 rows per run and drafts notes for up to 200 donors in the window. For bigger lists, point it at a tab that lists only donors whose last gift was 12–24 months ago (e.g. a FILTER formula on your main list), or a lapsed-donor report from your donor database.

How is “12–24 months ago” worked out?

In code, not by the AI: the agent counts the days from each donor's last gift date to today (in your trigger's time zone) and keeps 365–730 days, skipping anyone with a “Reactivation sent” or “Last contacted” date in the last year. Only those donors reach the AI. Change the window in “Check the last-gift dates”.

Is this a subscription?

No. Lapsed Donor Re-engagement is a one-time purchase of $79 per workspace and never renews. The Enterprise plan includes it at no extra cost. Running it live needs a paid plan (from Basic ($39/mo)), and your AI provider bills you directly for usage.

Can I test it before it touches real data?

Yes. Once it's set up in your workspace, Dry Run plays every step on sample data with simulated AI and app calls: nothing is sent and nothing in your apps changes. Switch the trigger on only when you're happy.

Put Lapsed Donor Re-engagement to work.

Free account, no credit card. Your Agents page opens with Lapsed Donor Re-engagement ready to buy and set up, then Dry Run it before it goes live.

Get this agent See how it works