Can a Nonprofit Use AI to Write Donor Thank-You Letters?

A nonprofit can use AI to draft donor thank-you letters. Dave by voolama (hellodave.ai) is a managed AI workflow platform where you build a workflow that takes verified gift data as input, passes it to an AI agent that drafts the letter, and routes the draft to a named staff member for approval before anything goes to a donor. The answer is yes, and the two rules that make it safe are these:

1. Gift facts come from verified records, not from the AI. The gift amount, the gift date, and any statement about goods or services provided in exchange must be entered by a staff member from your donor management system or accounting records. The AI agent receives those facts as part of its input and uses them in the draft. It does not generate or estimate them. The agent's system prompt in Dave by voolama should explicitly instruct it: "If any field is blank, write [MISSING: field name] in the letter rather than filling it in."
2. A named person approves every letter before it is sent. A Human Review task in Dave by voolama appears in the assigned staff member's Task Inbox. They read the draft, confirm the four IRC 170(f)(8) facts are present and correct, and click Approve, Reject, or Request Changes. Nothing goes to a donor until that step is complete.

What makes donor thank-you letters different from a newsletter or a payment reminder is the third requirement, covered in the next section: for gifts of $250 or more, the letter must include four specific facts required by the IRS under IRC 170(f)(8), and getting them wrong can invalidate the donor's deduction. The reviewer's job at the Human Review step is not just to check tone. It is to confirm those four facts are present and correct in the letter body.

The general draft-and-approve pattern is covered in the newsletter workflow at Can a Small Business Owner Use AI to Write a Monthly Newsletter and Still Approve Every Word? The donor letter workflow described here adds the IRC 170(f)(8) checklist as a named reviewer responsibility that the newsletter workflow does not require. For payment reminders, the same two rules apply: see Should a Small Business Let AI Write Its Payment Reminders? for how amounts from verified records and a named approver work in that context.

Under IRC 170(f)(8) and IRS Publication 1771, a written acknowledgment for a cash contribution of $250 or more must include exactly four things. All four must appear in the letter body. The AI drafts the surrounding language; the reviewer at the Human Review step confirms each of these four facts is present and correct before clicking Approve:

1. The name of the organization. The legal name of the nonprofit as it appears on the organization's IRS determination letter.
2. The date of the contribution. The date the gift was received, not the date the letter is written.
3. The amount of the cash contribution. The exact dollar amount from your records. The AI must not round, estimate, or alter this figure.
4. A statement of whether the organization provided any goods or services in exchange for the contribution. If no goods or services were provided, the letter must say so explicitly: "No goods or services were provided in exchange for this contribution." If goods or services were provided, the letter must include a good-faith estimate of their value. Contributions where the donor receives something of value in return are subject to additional disclosure rules under IRC 6115.

The IRS requires the donor to obtain this written acknowledgment by the earlier of the date the donor files their tax return or the due date of the return, including extensions (IRS Publication 1771). A verbal thank-you does not satisfy the requirement.

For letters acknowledging gifts below $250, the substantiation requirements under IRC 170(f)(8) do not apply, but donors may still request a written acknowledgment for their own records. The same workflow applies: AI drafts, staff confirms the facts, a named person approves.

This article is not tax advice. The rules around charitable contribution acknowledgments are set by the IRS and interpreted by qualified tax professionals. Consult a qualified tax professional for guidance specific to your organization's situation. The IRS resources cited in this article are the official starting point, not a substitute for professional advice.

This piece is the workflow build companion to the sibling resource in this cluster, which covers the full template for a donor acknowledgment letter at /resource/donor-acknowledgment-letter-template. That resource covers what the letter should say; this article covers how to build the Dave by voolama workflow that drafts and approves it.

The workflow for AI-drafted donor thank-you letters uses four node types from the ten available in Dave by voolama: User Interaction, Agent Interaction, Human Review, and End. You build it in the Workflow Editor, accessed from the Workflows section in the sidebar. You need the Admin or Curate role to build workflows, and the Admin or Create role to create agents.

The four nodes, in order:

1. User Interaction node: A staff member opens a task in the Task Inbox and enters four fields: donor name, gift amount (exact figure from your records), gift date (date received, not date of letter), and goods-or-services statement. This is the only point where gift facts enter the workflow. The AI agent never generates these values.
2. Agent Interaction node: The AI agent receives the four gift facts plus a system prompt. A starting Config JSON for the agent in Dave by voolama: {"systemPrompt": "You are a nonprofit correspondence writer. You will receive a donor name, gift amount, gift date, and a goods-or-services statement. Draft a warm, specific donor thank-you letter that includes all four of these facts in the body. Do not estimate, round, or alter any figure. If any field is blank, write [MISSING: field name] in the letter rather than filling it in. The letter should be 150 to 250 words.", "model": "gpt-4o", "temperature": 0.4, "maxTokens": 600}. Temperature 0.4 keeps the draft warm but factual. The agent runs automatically: no task is created, and no human action is required at this step.
3. Human Review node: A task appears in the assigned reviewer's Task Inbox. The Payload section shows the AI-drafted letter alongside the four gift facts the staff member entered. The reviewer's explicit job is to confirm all four IRC 170(f)(8) elements are present and correct in the letter body before clicking Approve, Reject, or Request Changes. If they click Request Changes, the workflow routes back to the User Interaction node so the staff member can correct the input. Every decision is logged in the audit trail with the reviewer's identity and a timestamp, supporting SOC 2 CC6.1 and GDPR Article 30 when those modes are active in Dave by voolama. For more on what the audit log captures, see How Do I Audit What an AI Agent Said to a Customer and Why It Said It?
4. End node: The workflow closes as completed. The approved letter is available in the instance output for the staff member to copy into their email system or donor management platform and send.

To create the drafting agent, navigate to Agents in the sidebar (Admin or Create role required). Click New Agent, name it "Donor Thank-You Drafter", and click Create Agent. Click Create Version and paste the Config JSON above. The system assigns version v1 automatically. Version numbers are auto-incrementing integers (v1, v2, v3). You cannot choose or skip version numbers.

Dave by voolama has six default roles: Admin, Create, Curate, Use, Reporting, and Financial. Only Admin and Use roles can see and complete tasks in the Task Inbox. If a staff member cannot see the Tasks or Agents sections in the sidebar, their role does not include the required permission. See Why Can't I See Agents, Workflows, or Other Sections in Dave by voolama? for how to diagnose and fix role assignments.

Run a test instance with a hypothetical donor name and a small test gift amount before using the workflow for real donor letters. Confirm the agent writes [MISSING: field name] when a field is blank rather than inventing a value, and confirm the Human Review task appears in the correct reviewer's Task Inbox.

This article covers the workflow design for AI-drafted donor thank-you letters in Dave by voolama and the four IRC 170(f)(8) elements a reviewer must confirm. It does not cover the following:

• Tax advice. The references to IRC 170(f)(8), IRS Publication 1771, and IRC 6115 are starting points for understanding the acknowledgment rules. They are not legal or tax advice. Your organization's tax situation, the nature of the gifts you receive, and any state-level requirements may affect what your acknowledgment letters must include. Consult a qualified tax professional.
• Non-cash gifts. The acknowledgment rules for non-cash contributions (property, securities, vehicles) differ from the rules for cash gifts and are not covered here. IRS Publication 1771 addresses non-cash gifts separately.
• Quid pro quo contributions. If a donor receives goods or services in exchange for a contribution, additional disclosure rules apply under IRC 6115. This article addresses the basic goods-or-services statement required under IRC 170(f)(8) but does not cover the full quid pro quo disclosure requirements.
• Grant proposals. The piece Can a Nonprofit Use AI to Write Grant Proposals Without Misleading Funders? covers that use case, including how to check funder guidelines on AI use before submitting. Grant proposals and donor thank-you letters are different documents with different requirements.
• Sending the letter. Dave by voolama produces the approved draft. It does not send email or connect to a donor management system directly. The staff member copies the approved letter into their email client or donor management platform and sends it from there.

Disclosure: Dave by voolama is the product described in this article, published by its maker, voolama LLC. This is vendor documentation, not tax advice or legal advice.