A school group’s coordinator asked for a wheelchair-accessible lunch space. A donor has asked never to be charged the convenience fee. A caller has two returned checks and should only pay by card. Someone on your team knows each of these things. The question is whether the person taking the next phone order or editing the next reservation will see it in time.
Staff naturally expect a warning to pop up the moment they pull a constituent into an advance sale or open a group reservation. Altru’s support for that kind of interruptive alert is limited and varies by area, so most organizations end up combining what Altru does natively with a few habits that put the warning where staff already look. This guide covers both.
Start by finding out what your Altru actually shows
Altru lets you record notes on constituent records, and depending on configuration some note-like information can surface when a record is opened. What it does not reliably do, as far as we can tell, is interrupt a cashier with a pop-up in every transaction screen. Behavior in advance sales and group sales may differ from what you see on the constituent record itself.
Don’t guess. Run a ten-minute test:
- Pick a test constituent (or use your sandbox if you have one) and add a note that clearly reads like a warning.
- Start an advance sale for that constituent and watch whether anything appears.
- Create a group sales reservation with that constituent as the contact and do the same.
- Open the existing reservation again later, the way a coordinator would when making a change.
Write down exactly where the note showed up and where it didn’t. If the results don’t match what you expected, ask Blackbaud support whether there is a notification option you haven’t turned on, and check the current Altru help documentation for your version. That answer shapes everything below.
Put warnings where staff are already looking
Where a true pop-up isn’t available, the next best thing is a warning that’s impossible to miss in the place staff work. A few approaches that hold up:
Use the reservation itself for group-specific notes
Accessibility needs, dietary restrictions, arrival quirks, and billing arrangements belong on the group sales reservation, not buried on the coordinator’s constituent record. Reservations have their own notes and details that coordinators open anyway. Agree on a consistent prefix, such as ACCESS: or BILLING:, so a quick scan catches them.
Use constituent attributes for person-level flags
For things that follow a person across every sale (payment restrictions, VIP handling, “do not contact”), a constituent attribute is easier to report on than free-text notes. Keep the list of attribute values short and specific. “Card payments only” is useful. “See notes” is not.
Make the flag visible in the record’s name or summary only when it truly matters
Some teams append a short marker to a constituent’s lookup name so it appears in search results during a sale. It works, but it touches mailing and acknowledgment output if you’re not careful, and it gets messy fast. Reserve it for a handful of high-stakes cases, document who is allowed to do it, and test how the name prints on receipts and letters before you rely on it.
Back it up with a daily list
Even a perfect flag fails if nobody opens the record. A simple safety net is a query that runs every morning:
- Upcoming group reservations for the next few days that have notes or a specific attribute on the contact.
- Constituents with a payment or handling flag who have an advance sale or reservation scheduled soon.
Print it or post it for the box office and group sales team, and cover it in the morning huddle. It’s low-tech, but it catches the cases where the person processing the change never thought to look.
Write alerts people will actually act on
An alert system only works if staff trust it. When every record has a note, nobody reads any of them. A few rules help:
- One action per alert. “Charge to card on file only; no invoices” beats a paragraph of history.
- Date and initial it. Staff need to know whether a warning from three years ago still applies.
- Give it an end. A school’s accessibility request for one visit should not follow that teacher forever.
- Keep sensitive details out. Notes can be seen by many users. Record what to do, not why, when the reason is personal.
Review the flags on a schedule
Set a quarterly reminder to pull every constituent with an alert attribute or warning-style note and ask the owning team whether each one still applies. Remove what’s stale. A short, current list of alerts is far more effective than a long list nobody believes.
Quick answers
Can Altru force a pop-up in group sales when a reservation is opened?
Not in a way we’d promise across every screen and version. Test it with a sample record, and confirm with Blackbaud support if you need certainty.
Should alerts live on the constituent or the reservation?
Person-level warnings go on the constituent (ideally as an attribute). Visit-specific details go on the reservation. Mixing them is the most common reason warnings get missed.
