Someone registers for your fall lecture on their phone, hits submit, and a minute later gets an email with a generic subject line that thanks them for their gift. They didn’t give a gift. They bought two seats and want to know where to park.
That gap between what the guest did and what the email says is the real problem with web form acknowledgements in Altru. The email technically works. It just doesn’t sound like your organization, and it often doesn’t answer the question the guest has right after paying. Below is what you can usually change inside Altru, where the limits tend to be, and how other organizations handle the parts Altru doesn’t cover well.
Start by deciding what the email is for
“Acknowledgement” is a fundraising word. It comes from the donor receipt world, where a gift has to be formally acknowledged. For a ticket purchase, an event registration, or a new membership, guests think of the same message as a confirmation: proof that it worked, plus what happens next.
Before you edit anything, write down for each web form what the guest needs from that first email:
- Tickets and registrations: date, time, quantity, how entry works, parking or arrival notes, who to contact.
- Memberships: level, start and expiration dates, when the card arrives, what they can use today.
- Donations: amount, date, tax language your finance team has approved, and a real thank-you.
Those are three different emails. A lot of the frustration comes from one generic template being stretched across all of them.
What you can typically change in Altru
Altru web forms include acknowledgement email settings, and in most setups you can edit the sender details, the subject line, and the message body, with some merge fields available to pull in transaction information. Exactly which fields are available, and how much formatting the body supports, depends on the form type and your Altru configuration. Rather than guess, open each live form’s email settings and look at what’s actually editable.
A few changes that are almost always worth making:
- Rename the subject line. “Your tickets for Saturday’s Garden Tour” beats a generic one-word subject, and it’s usually the easiest change to make. If your form only allows a static subject, at least make it specific to that form.
- Rewrite the opening sentence. Lead with what they bought, not with a thank-you for “your support.”
- Add the practical details. Hours, address, entry instructions, a phone number. Plain text is fine.
- Set a real reply-to address. Guests reply to these emails. Make sure the replies land in an inbox someone checks.
- Check every form, not just one. Each web form tends to carry its own email settings. Fixing the membership form doesn’t fix the event form.
Where the limits usually show up
Altru’s built-in acknowledgements are meant to confirm a transaction, not to be a fully designed marketing email. Organizations commonly run into some combination of these:
- Limited control over layout, branding, and images compared to what your marketing team sends from its email platform.
- Not every detail you want to show is available as a merge field.
- Conditional content (different text for members vs. non-members, or for different ticket types) is hard or impossible within a single template.
- No easy way to send a second, follow-up message (a reminder the day before, a thank-you after the visit) from the same form.
If you’re not sure whether a specific change is possible natively, test it in a sandbox or a duplicate form first, and ask Blackbaud support before rebuilding a live form around an assumption.
Test like a guest, not an admin
Run a real transaction through each form with a personal email address, on a phone. Then check:
- Did it arrive quickly, and not in spam or a promotions tab?
- Does the subject line make sense in a crowded inbox?
- Are merge fields filled in, or are any blank or showing raw placeholder text?
- Would someone who has never visited know where to go and what to bring?
Refund or void the test transactions afterward so they don’t skew your daily sales or revenue reports.
When to stop fighting the built-in email
Some organizations keep Altru’s acknowledgement short and functional, then send a richer confirmation separately. A common pattern is to build an Altru query for the transactions you care about (today’s web ticket sales, new memberships, online gifts) and use that list to drive the follow-up email. Done by hand, that means exporting the query and uploading it to an email tool every day, which tends to slip as soon as the person who owns it is out.
Whatever route you take, keep the donation receipt language owned by whoever handles gift acknowledgements, so a well-meaning rewrite of the ticket email doesn’t change your tax wording.
Social Good’s Email Designer sends automated, branded emails, such as eTickets, acknowledgements, and renewal notices, directly from Altru queries, so the follow-up step above runs without manual exports. Altru still holds the transaction data.
Quick answers
Can I call it a “confirmation” instead of an “acknowledgement”?
In the email itself, yes: the subject line and body are what guests see, and you can usually word those however you like. The label Altru uses for the setting on its own screens is a separate matter, and changing it is likely outside what an administrator can configure.
Can each web form have its own email?
Generally, yes. Email settings are tied to the form, which is also why you have to update each one individually.
