How to Use Gift History and Donor Notes to Draft a Lapsed-Donor Re-Engagement Email With AI

Lapsed-donor outreach often sounds generic because staff do not have time to read the history before drafting. This workflow uses the history to create better first drafts faster. This workflow is for nonprofit teams that want to restart donor relationships without sending a bland mass reactivation message. The goal is to get to a usable result with the fewest moving parts while still keeping the work grounded in real source material.

Editorial guardrail: Use AI to extract, organize, and draft. A staff member should verify funder requirements, donor details, legal acknowledgment language, budget numbers, names, dates, privacy issues, and tone before anything is submitted or sent.

What you need

• A cleaned donor list with last gift date, last gift amount, campaign or event source, and a few useful notes
• A definition of lapsed that matches your organization, such as no gift in 12 or 18 months
• Claude, ChatGPT, or Gemini for file or text review

How to capture or gather the source material

• Export a lapsed donor segment from your CRM with only the fields needed for drafting. Include donor name, last gift date, amount, campaign or event source, and brief notes if those notes are appropriate for the drafting workflow.
• Create one short context note about the current campaign, update, or reason you are reconnecting now.
• Do not include sensitive data you would not want repeated in an email draft or shared broadly with staff.

The fastest workflow

1. Upload the donor history sample or paste the fields into Claude along with your re-engagement context.
2. Ask for a short re-engagement email that acknowledges the donor's past connection without over-claiming familiarity.
3. Generate one or two variants for different donor segments such as event donors, monthly donors, or first-time donors who never gave again.
4. Review the draft, remove anything that feels too familiar or unsupported, and send only after a human check.

Tool-specific instructions

Primary path: Claude

• Claude is a good fit because it can turn a small history record into a calm, usable outreach draft without needing a huge source bundle.
• Be specific about what the email should not do. Tell it not to invent personal history, not to mention notes that feel too private, and not to sound desperate.
• Draft by segment when possible. One lapsed-donor email rarely works equally well for every past donor type.

Fallback options

ChatGPT fallback

• ChatGPT is a good alternative when you want faster drafting and more variation testing.
• Upload or paste the same donor fields and ask for two short re-engagement versions with different tones.

Gemini fallback

• Gemini works well if your donor segment already lives in a spreadsheet and you want to review segment patterns before drafting.
• Use it to cluster segments first, then draft by cluster.

Copy and paste prompt blocks tailored to the workflow

Primary prompt

{
  "task": "Using only the donor history details below, draft a short lapsed-donor re-engagement email.",
  "source_rules": [
    "Use only the donor history details below, draft a short lapsed-donor re-engagement email."
  ],
  "constraints": [
    "Acknowledge the donor's past connection naturally, mention the current context for reaching out, and invite a low-pressure next step.",
    "Do not invent personal history, do not overstate impact, and do not use details that would feel too private in an email.",
    "Details: [paste donor fields and current outreach context]."
  ],
  "input": {
    "details": "[paste donor fields and current outreach context]"
  }
}

Fallback prompt

{
  "task": "Review this lapsed-donor segment and draft a short re-engagement email that feels informed but not intrusive.",
  "constraints": [
    "Keep it easy to edit and avoid unsupported personalization."
  ]
}

Quality checks

• Verify that the donor really belongs in the lapsed segment you are targeting.
• Check that any mention of past connection is supported by the donor history you supplied.
• Remove notes that are too private or too internal for donor-facing language.
• Keep the call to action low-pressure and realistic.

Common failure modes and fixes

• The draft feels creepy or overpersonalized: Reduce the input to objective gift-history fields and remove personal notes.
• The email is too generic: Draft by segment and include one clear current context line.
• The message sounds like a hard ask: Ask for a stewardship-first tone with a light invitation.
• Staff use outdated donor notes: Clean the source set before the drafting step and keep only notes that are current and appropriate.