top of page

Thanking donors properly is not the same as receipting

  • Aug 29
  • 3 min read

Updated: 2 days ago

Introduction


A donation arrives and the system sends a receipt. It confirms the amount, the date and the tax status. It is accurate, immediate and completely forgettable.

That receipt is not a thank-you, and the difference between the two explains more lapsed donors than any weakness in the cause. Thanking people properly is the cheapest retention work available to a charity, and the most consistently skipped.


1. Thanking donors properly means separating gratitude from administration


Send two things, not one.

The receipt handles the transaction. The thank-you handles the relationship. Combining them produces a document that reads like a confirmation email, which is exactly how the donor will file it.


2. Be quick, and prefer quick over polished


Delay carries a message of its own.

A thank-you within two or three days lands while the decision is still fresh. One that waits three weeks for a nicely printed batch has already told the donor where their gift sat in the queue.


3. Lead with what they made possible


The opening sentence does most of the work.

Start with the effect rather than the organisation. "Because of you, a family gets help this week" outperforms "Thank you for supporting our vital work", because one names a consequence and the other names a category.


4. Be specific about the gift


Generic gratitude reads as automated.

Reference the amount, the appeal it answered, or the event they attended. It takes a merge field or thirty seconds and it is the difference between a message written to them and a message written to everybody.


5. Never include an ask


This single rule changes how the message is received.

A donation request inside a thank-you converts the gratitude into a preamble. Let the thank-you stand alone; there will be another opportunity, and it will work better because this one was clean.


6. Use a human voice and a real name


Institutional language undermines the whole point.

Signed by a person, written the way that person speaks, without the sector vocabulary. A slightly imperfect message from a named human beats a polished one from an organisation every time.


7. Match the effort to the gift


Not every donor needs the same treatment.

Small gifts warrant a prompt, warm, largely automated message. Larger gifts warrant a phone call or a handwritten line. Set thresholds so this happens by rule rather than by whoever notices.


8. Thank people who gave something other than money


Volunteers, referrers and in-kind donors are routinely missed.

Somebody who gave a weekend, introduced you to a funder, or supplied goods has made a real contribution and usually receives nothing at all. The same principles apply, and the omission is noticed.


9. Check that the thank-you is actually going out


Automated gratitude fails silently.

Templates break, integrations change, and a platform update stops a sequence without warning. Donate a small amount to your own organisation twice a year and see what arrives, because that is the only reliable test.

Keep a record of what was sent to whom. Thanking the same person twice is a small embarrassment; failing to thank a major donor because two people each assumed the other had done it is a genuine problem, and it happens in every organisation without a shared record.


Conclusion


Treat the thank-you as a separate piece of work from the receipt, because the receipt confirms a transaction and only the thank-you builds a relationship.

Send it within days rather than weeks, open with what the gift made possible instead of with your mission, reference the specific donation so it reads as personal, keep every request for money out of it, sign it from a named human in ordinary language, set thresholds so larger gifts get a call or a handwritten note, extend the same courtesy to volunteers and in-kind donors, and test the whole thing periodically by giving to your own organisation and seeing what comes back.


Related reading


 
 
 

Comments


bottom of page