A donor gives at the front desk, and before they reach the parking lot they have a generic “thank you for your gift” email in their inbox. Ten minutes later your development director sends the personal note she had planned, and now the donor has two thank-yous that don’t sound like the same organization. Or a comp ticket goes out to a board member and Altru sends the standard acknowledgment anyway.
When the default acknowledgment email keeps sending even though you didn’t want it to, the cause is almost always one of a handful of settings working exactly as designed. The trick is finding which one, because Altru can send email from more than one place.
Start by identifying which email is going out
Before changing anything, get a copy of the email the guest actually received. Forward it to yourself or send a test transaction to a staff address. Look at:
- The sender address and subject line. Compare them to the templates you have in Altru. If the subject doesn’t match anything you recognize, the email may be coming from somewhere other than Altru (a payment processor receipt, a third-party form tool, or an old integration someone set up years ago).
- The channel the transaction came through. A web form gift, a daily sales transaction, an advance sale, and a membership processed by staff can each be tied to different email behavior.
- Whether it happens every time or only sometimes. “Always” usually points to a form-level or default setting. “Sometimes” usually points to staff choices or to whether the constituent had an email address on file.
The usual reasons it keeps sending
The web form has its own acknowledgment
Altru web forms for donations, memberships, and tickets typically carry their own confirmation or acknowledgment email. That email is attached to the form, not to the person, so it goes to every buyer who completes that form. If you edited a template elsewhere and nothing changed, check whether the form is pointing to a different template than the one you edited. Organizations that have copied forms over the years often have several near-identical templates, and the form may still reference an older one.
A template is set as the default
Where Altru lets you mark an email template as the default for a type of transaction, that default fills in automatically unless someone changes it. Staff may not realize there’s a choice at all. If you want “no email” to be the normal outcome for a certain kind of transaction, confirm whether your version allows that to be the default, or whether the best you can do is have staff clear it each time.
Staff are processing in a way that triggers it
At the desk, an email address on the constituent record or entered during the sale can be all it takes. Seasonal and part-time staff tend to accept defaults, which is reasonable. If the fix depends on someone unchecking a box, write it down and put it where the transaction happens.
Something outside Altru is also sending
If you’ve ruled out everything above, look at what sits around Altru: your payment gateway’s receipt settings, any form tool that feeds Altru, and any marketing platform that receives Altru data. Those can produce an email that looks like an acknowledgment and gets blamed on Altru.
Be honest about what you can’t turn off
Some of this behavior may simply not be optional for certain transaction types. We don’t want to guess at the exact settings in your environment, so the reliable way to confirm is to test it: run the same transaction through a sandbox or a test constituent with a staff email, change one setting at a time, and note what arrives. If an email still sends no matter what you change, open a case with Blackbaud support and ask directly whether that acknowledgment can be suppressed for that transaction type, and if not, whether the template can at least be edited to fit.
Workarounds people try, with the tradeoffs:
- Leaving the email address off the transaction. It stops the message, but you lose the address for future communication and may create a duplicate constituent later. Generally not worth it.
- Making the default template neutral. If you can’t stop the email, rewrite it as a short receipt (“We received your payment”) and save the warm, personal thank-you for a separate message. Two emails is fine when they have different jobs.
- Separate forms for special cases. A dedicated form for comps, tributes, or major gifts lets you attach a different template, or a minimal one, without changing your main form.
Decide what each transaction should get
The cleanest long-term fix is a short written rule for each channel: which transactions get an automatic receipt, which get a personal acknowledgment, and which get nothing. Once that’s agreed, configure Altru to match as closely as it allows, and use a query of recent gifts and sales to spot-check that the right people heard from you.
If you want more control over acknowledgments
Some organizations stop relying on Altru’s built-in acknowledgment for certain transactions and send their own instead. Email Designer sends automated, branded emails, including acknowledgments, from Altru queries without manual exports, so you decide which records get which message by how you build the query. It doesn’t switch off Altru’s own email, so you’d still confirm in your setup which default you can disable.
Quick answers
I changed the template and the old email still sends. Why?
The form or transaction type is probably pointing to a different template than the one you edited. Check which template each form references.
Can I stop acknowledgments for one donor only?
Communication preferences on the constituent record can help for marketing mail, but whether they suppress a transactional acknowledgment depends on how that email is triggered. Test it with a staff record before relying on it.
