# The Second Gift Starts Here
## A welcome message and a plan for what follows

The first gift gives you something to acknowledge, not a deadline for the next ask. Start with an accurate thank-you, a person who will answer, and a next step your team can keep.

Use the message and record below to prepare that welcome. Replace the example details with verified information before sending.

### A welcome you can adapt

**Fictional worked example:** Riverbend Reading Project received Priya Shah’s first, one-time gift of $75 on September 8. The gift record confirms it supports the after-school reading program. Priya selected email only and requested the October program update. The receipt has already been sent. Every name, amount and date below is invented.

**Subject:** Thank you, Priya — from Riverbend Reading Project

Hi Priya,

Thank you for your $75 gift to Riverbend’s after-school reading program. We’re grateful you’ve chosen to support this work.

The program gives students a place to read with a tutor after school. Your receipt was sent separately on September 8. If it hasn’t reached you, reply here and I’ll help.

You asked for the October program update. I’ll email it by October 15, once our program team has checked the details. We’ve also recorded your preference for email only.

If there’s something you’d like to know about the program, you can reply directly to me. There’s no need to respond to this message.

Thank you,

Maya Chen
Donor support, Riverbend Reading Project

**Why these details belong:** the amount and designation confirm what was received; the receipt sentence resolves a practical question; the update has an owner and a date. The message makes no claim that one gift produced a particular student result.

### Put the promise on someone’s calendar

These dates fit the fictional team’s available capacity and Priya’s request. Choose your own dates before making a commitment.

| When | Owner | Work to finish | Record when complete |
|---|---|---|---|
| September 9 | Maya, donor support | Check gift, receipt status and preferences; send the welcome. | Message and sent time; delivery failure if reported. |
| October 8 | Luis, program lead | Verify the reporting period, figures and permitted details for the update. | Approved text and source references. |
| October 10 | Maya | Check approval and resolve missing information before the deadline. | Ready to send, or blocker with next action. |
| By October 15 | Maya | Email the requested update. | Exact message, recipient and sent time; known delivery status. |

“Sent” does not mean read. An update also does not close an unanswered question. Keep each obligation visible until its work is finished.

### Change the next step when the situation changes

**The donor has asked a question.** Answer it before sending a generic welcome sequence. If the answer needs another colleague, acknowledge the question and commit only to a check-in you can make:

> Thanks for asking how tutors are trained. I’m checking with Luis, who runs the program. I’ll email you by September 12, even if I’m still waiting for the full answer.

Keep Maya accountable for replying; Luis supplies the information. September 12 is the check-in date, not proof the question is resolved.

**The gift is monthly.** Confirm the recurring amount and status from the gift record. Replace the one-time wording with “Thank you for starting a monthly gift of [verified amount].” Include the actual route to change or stop the gift. Check future messages for duplication with existing receipts and recurring-donor communications. A monthly gift does not establish interest in another appeal.

**Communication preferences are unknown.** Record “unknown.” Use only the communication route your organization has established for this acknowledgement. Do not infer newsletter permission from an email address or add the donor to a new sequence. If appropriate, offer a way to state preferences without requiring a reply.

**The update is delayed.** Keep the original October 15 commitment in the record. Before it passes, explain what is missing and offer a realistic next check-in. Changing an internal task date does not update the donor.

### Leave a record your colleague can use

**Completed example:** Priya’s October update remains open. Maya owns delivery by October 15. Luis must verify the text by October 8. Maya checks progress October 10. Email only; October update requested on the September 8 gift form. Receipt sent September 8. Welcome sent September 9; no failure reported. No reply required.

**Copy for your next welcome:**

```text
Donor / internal record ID:
Verified gift: amount, date, designation, one-time or recurring:
Receipt status and evidence:
Donor-stated preferences / source and date:
Open question or exact promise:
One accountable owner:
Needed from whom, by when:
Original promised date:
Next check-in:
Message / sent time / known delivery status:
What remains open:
```

Keep this record in your team’s approved system. The next colleague should be able to see what happened, what the donor actually requested, and what still needs doing.

*Further reading: [Randall Hallett on second gifts and a relevant welcome](https://www.hallettphilanthropy.com/podcast/episode-233-creating-second-time-repeat-donors-needing-speed-and-personalization-to-succeed). These messages and the schedule are original Gratona examples.*