General Feature Requests

If an event is archived, we no longer need any information from it. We also do the same type of events each year and adding this feature would remove clutter when trying to find a specific event.

Is there some way to create a notification system to alert event admins of possible mapping errors within the guest dashboard? When an event registrant gets incorrectly mapped to a constituent profile on RE, the pattern is that this information then gets incorrectly conflated within the Almabase profile and for the sake of overall data integrity and cleanliness, we'd like this to be avoidable if at all possible. Please let me know if you have any questions or I can provide examples.

It is not uncommon to sell items at events, especially golf tournaments as guests check in. It would be great to have an option to add items for sale, select them quickly at check out and prompt payment options at this time, all within the database. Currently, you have to create tickets and get there by editing a registration, which is cumbersome.

We would like to have event-specific details on the confirmation screens that registrants see once their transaction is complete.

In the Giving tool, there is no way for the admins to download all the reviews/ratings given by donors after they participate in Giving Days/Campaigns. We are highlighting an overall rating out of 5 and the number of reviews the giving tool has received on the QBR reports. A lot of customers have asked to see/read these reviews and be able to download them.

I would like to see ticket information in the registration notification emails, so we can see which tickets are being purchased through the email. We have somebody on campus who runs an EMS Class who would need this information. He doesn't work for our department and doesn't have access to Almabase - however he gets notified when people sign up for his classes.

It would be helpful to have a place where I can view a sequential change log for changes made to the Almabase database when synced from Raiser's Edge. It could also include user changes and administrative changes. It would make it easier to identify sync issues and have an idea of how the systems are interacting from an administrative viewpoint. This would be accessed quarterly.

We have some Alumni Week events that overlap, so registrants should be limited to selecting only one. However, the system currently allows them to register for multiple overlapping events. Would it be possible to display an error message during the registration process if an overlap occurs?

We wanted to make a change to the initial question of "How many people will be attending" to "How many people will be attending, including your student" but only wanted to make the change for the Family Weekend event, not globally.

It would be great to be able to mark an Address/Email/Phone as Primary in Almabase. In RENXT - this is possible. If a user registers for the first time on the Almabase platform, and they provide three phone numbers (cell/home/office) - we do not know which of these three phone numbers is primary. We can make the assumption that the Cell is primary - but we don't know. This is an issue when importing the data to RENXT. It's also an issue with using the data. We do a lot of calling via "Phoneathon," and we will need to know which number users prefer. Finally, if we are using the Almabase platform, and see that a person has three phone numbers, it's not clear which is their primary. We would need to go back into RENXT and see the datapoint of "primary" there.