Events

Need to filter Registrant with non registrant (guest of) to manually map only Registrants.

Currently, AlmaBase offers four ticket types when creating events: Open Ticket, Mandatory Ticket, Sponsored/Team Ticket, Seated Ticket. One challenge our team faces is that ticket purchase deadlines can be set for all ticket types except Mandatory Tickets. This creates a significant limitation for events that require attendees to purchase a ticket as part of a registration while also enforcing a firm registration and payment deadline. While Seated Tickets do allow us to set a purchase deadline, they are not a suitable workaround because Seated Tickets are not truly mandatory. Registrants can still proceed through registration without purchasing a ticket, which defeats the purpose of requiring payment as part of event registration. Please add the ability to configure a ticket purchase deadline for Mandatory Tickets, similar to the functionality currently available for other ticket types.

I like that the email groups are created for guests that have attended events. It would be nice if a list would also be created automatically for those who did not attend. We often like to send "We missed you at...." messages with photos from the event with hopes to inspire the alum to connect with us at future events.

Allow admins the option to make the email mandatory or optional for additional/accompanying guests. Currently it is not mandatory for accompanying guests to input an email address. Admins should have the option to make it mandatory or optional. Eg: If you've got guests coming to a conference and you want to communicate content received/follow-up with participants post-event. It should be optional as its not always appropriate for every transaction. Definitely not applicable for every event, but if you are doing a conference or seminar type event with material/deliverables it would be really good.

Make email required for event accompanying guest registration. Right now it's a core field but it's not marked as required.

Currently, when a registrant modifies their registration (guests, tickets, etc.), Almabase overwrites the original entry with the updated information. While an email notification alerts admins that a change took place, it provides no details on what was altered. Because we prepare nametags and ticket packets on a rolling basis during long registration periods, staff must manually compare old spreadsheet exports against current data to identify changes. We request a built-in change log on the admin record and detailed line-item changes in the notification emails to eliminate this manual workflow.

Show the sub-event venue locations on the ticket selection page for guests. Currently, only the description of the sub-event and the time show up, but if I am not using the schedule feature (I don't want all attendees to know about the events they were invited to) I need to show them the location there as well and not just in their guest kit.

Description: Currently, the "Let others know I will be attending" checkbox operates at the top-level registrant level. When a registrant checks this box, every individual added to that order is automatically published on the public "See Who's Coming" guest list. The Issue: Many alumni want to be listed on the public attendee roster to encourage classmates to attend, but they do not want their children or family members' names displayed online. Under the current structure, registrants must choose between an "all-or-nothing" setting: either publish the entire family (including minors) or keep the main alumnus entirely anonymous. Proposed Solution: Move the privacy checkbox from the primary registrant level down to the individual attendee level (guest details). Allow a checkbox for each registered attendee (e.g., "Include [Attendee Name] on the public guest list" or "List as Anonymous"). Default main registrants to opting in while defaulting additional guest/child tickets to opted out (or giving the registrant explicit toggle control per person). Impact: This granular control protects attendee privacy—particularly for minors—while boosting overall participation in the "See Who's Coming" feature, as alumni won't have to hide their own attendance just to protect their family's privacy.

I'm adding this request on behalf of The Shipley School. The team has requested for an automated email to be triggered to people who abandon their carts just before the payment step during Event registrations and Giving campaigns. The email should basically say that their registration for the event was incomplete/their gift was not received and urge them to complete the payment step.

Currently, Almabase only syncs event dates and the name to RE. It would be helpful if the event venue (Location, City, State) were also synced to Raiser's Edge.