A family buys four tickets online and gets a tidy confirmation within a minute. The family behind them in line buys the same four tickets at the admissions window and walks away with a paper receipt. A school coordinator books a field trip over the phone and gets nothing at all until someone remembers to type an email. Same program, same price, three very different experiences.
That gap exists because, in Altru, the automatic acknowledgement email is tied to the web form, not to the program or the sale itself. Sales entered by staff in Daily Sales or Advance Sales don’t pick up the confirmation you designed for the web. This article explains where that line falls, what you can do inside Altru, and how to close the gap without someone hand-writing emails at the end of every shift.
Where the acknowledgement actually lives
When you set up a ticketing or registration web form, the confirmation email is part of that form’s configuration. The wording, the merge fields, and the trigger all belong to the form. So when the same program is sold through a different channel, the sale goes into Altru just fine, but nothing tells Altru to send that form’s email.
Staff-entered sales do have some options, but they vary by version and setup. Depending on your configuration, staff may be able to email or print tickets from the sale, and some organizations have receipt templates attached to their point-of-sale workflow. What you generally won’t get is the same branded, program-specific message your web buyers receive. Because this depends on your version and configuration, test it in your sandbox, or ask Blackbaud support, before you tell staff what will and won’t go out.
Decide which sales actually need an email
Not every desk sale needs an acknowledgement. A walk-up general admission guest who’s standing in your lobby doesn’t need an email telling them they bought a ticket. Before you build anything, sort your staff-entered sales into groups:
- Advance sales by phone: almost always need one. The buyer has no ticket in hand, and the email is their proof of purchase, arrival time, and directions.
- Program registrations sold at the desk (camps, classes, workshops): need one. Parents want the drop-off time, what to bring, and the cancellation policy in writing, just as web registrants get.
- Same-day admission: usually optional. A short thank-you or post-visit message may be more useful than a receipt.
- Group sales: often handled separately with a contract or invoice, so a generic acknowledgement can confuse things.
That list becomes your scope. It’s much easier to automate three message types than to promise “every sale gets an email.”
Options inside Altru
Capture the email address at the sale
None of this works without an address on the constituent record. Make asking for an email part of the script for phone and desk sales of anything that needs a confirmation, and attach the sale to a constituent rather than an anonymous patron. This one habit fixes more than any tool will.
Use the ticket emailing options you already have
If your setup lets staff email tickets from the sale, train them to use it for advance sales at minimum. It won’t carry the full program details from your web confirmation, so keep that content short and put the essentials (date, time, location) where staff can paste or reference them.
Build a query and send in batches
The most common workaround is a query of sales by channel and date: for example, yesterday’s Advance Sales and Daily Sales transactions for specific programs, with the constituent’s email, program name, event date, and time. Someone exports it each morning and sends a merged email from your marketing or email tool. It works, but it relies on a person doing it every day, and an export step is where mistakes and delays creep in. A sale on Friday afternoon might not get its confirmation until Monday.
Route phone buyers through the web form
Some organizations have staff complete phone orders on the public web form on the caller’s behalf, so the standard acknowledgement fires. It gets the right email out, but it can affect how revenue is attributed to channels and how payment is handled, so talk to your finance team before adopting it. Be careful about entering card details into a public form while on the phone, and check it against your payment and PCI policies.
Make the desk email match the web email
Whatever route you choose, write the staff-sale confirmation from the web version so buyers get the same information either way. Keep a shared document with each program’s key details (arrival instructions, parking, what to bring, refund terms) and point both messages at it. When those details change, update one source instead of discovering months later that the phone confirmations still list last year’s parking lot.
Check the result once a month: pull a handful of recent desk and phone sales, confirm an email went out, and read it as a buyer would.
Automating it from Altru queries
The query-and-export approach is the right idea; the weak link is the manual step. Social Good’s Email Designer sends automated, branded emails, including eTickets and acknowledgments, directly from Altru queries without manual exports. You can point it at a query of Daily Sales or Advance Sales transactions so desk and phone buyers get a confirmation that looks like the one your web buyers receive, and Altru stays where the sale is recorded.
Quick answers
Can a Daily Sales transaction trigger the web form’s acknowledgement?
Not as a rule. The web form’s email is tied to the form. Confirm your own version’s behavior in a sandbox before relying on any desk-side email option.
What’s the minimum I need for any workaround?
An email address on the constituent record, and sales tied to that constituent. Without those, no query or tool can send anything.
