FIELD GUIDE 02 / DONOR WELCOME
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.
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.
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.
One gift. A welcome. A kept promise.
- SEP 9Maya welcomes
Check the gift and receipt. Send the thank-you.
- OCT 8Luis verifies
Approve facts and permitted details.
- OCT 10Maya checks
Resolve missing information.
- BY OCT 15Maya updates
Send the update Priya requested.
Answer it; give a check-in date if facts are missing.
Explain before October 15. Keep the promise open.
Verify recurring details. Avoid duplicate messages.
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:
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:
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.
If your team is setting this up in Gratona, explore Journeys and assigned work. Check the enrollment and the tasks each configured step creates so the handoff has an owner and a visible result.
TAKE IT TO YOUR TEAMThe welcome message and planEditable guide · Full example, schedule and blank recordFurther reading: Randall Hallett on second gifts and a relevant welcome. These messages and the schedule are original Gratona examples.
Explore the reading list ↗