Altru Ideas
We value your unique insight into our products and services and often receive ideas and feedback from our community in a variety of ways. To streamline this process, we’ve created an idea bank where you can post product suggestions, vote for those most important to you, and add comments to existing ideas.
We value your unique insight into our products and services and often receive ideas and feedback from our community in a variety of ways. To streamline this process, we’ve created an idea bank where you can post product suggestions, vote for those most important to you, and add comments to existing ideas.
Not being able to mark any/all registrants as "will not attend" at our convenience causes instability in tracking data and attendance.
Not being able to remove guests or mark as will not attend makes our event capacity numbers inaccurate and requires us to do manual clean-up of data outside of the database when exporting guest lists.
Yes! Agree! All this reporting and tracking capability, but it is worthless if we can't use the system to reflect the realities we know about the event.
This is causing a lot of problems for me. The event capacity count is worthless if we know that a number of tickets won't be used but Altru doesn't reflect that.
The work around given to me by Altru support is truly ridiculous. Marking as a "no-show" and then artificially increasing capacity? It seems like a very easy fix to me and instead you are expecting your clients to go out of the way to fix Altru's issue.
How can this solution be of any use when our staff are working on seating arrangements, guest lists, name tags, etc. The hope was to reduce the manual labor by our staff not increase it.
Added to the fact that this has been and issue for YEARS with no response from Altru!?! Truly shameful.
A three year old problem with no solution? Very disappointing. PLEASE fix this. I'm also unhappy to see the workaround for this is to artificially increase the capacity of the event. I would prefer to put good, correct data into altru, not bad, falsified data. What's the point of a database if we fill it with bad data?
Seems counter productive to not be able to mark guest as will not attend and the attendance count not adjust. Requires maintaining separate list for registrations with accurate planned attendance count
There is no logic behind this. Please change it!
This is one of Altru's stranger functionality failures (among many shortcomings). It is arguably more important to be able to flag registrations as unused ("will not attend") when they have been assigned in bulk as part of a sponsorship than it is to flag just the host as not-attending or, even more impractically, individual ticket buyers as not-attending. This oversight means that we have to navigate around artificially inflated guest lists and event capacities throughout our prep for events, including always having to manually recalculate attendee totals when reporting to event caterers and vendors, with no means of tracking the actual event capacity in Altru. It is really unacceptable that this essential functionality is not available.
PLEASE change this!! It completely skews my reporting and negates the purpose of linking guests in the registration lists. I honestly do not see the reason why this option isn't easily available; it seems like more work to take the option away.
PLEASE Change this. I have many unnamed guests that I know are not going to attend, but I can't remove them from the count or the registered list. Not very efficient!
This would be a great improvement on the event side of Altru. Currently, this skews my reports and is not very user friendly.
This is a basic feature that should be an easy fix. It makes the pairing of guest with host to be a useless feature. I shouldn't have to adjust my capacity numbers or write special queries to be able to quickly see who all has bought a ticket (and thus supported my event) but is not coming. It skews all numbers and reporting.
Being unable to mark an Unnamed Guest as cancelled really throws a wrench in the works when tallying the final head count for a seated dinner. We're required to keep two lists...one here in Altru, then one kept by hand. Double work and extra room for error, especially for a large event. This defeats the entire purpose of Altru's event planning capability.
I loved the idea of Altru automatically posting the number of guests equivalent with the sponsorship level on the event -- until I discovered that if they were not going to bring the guest, we could not delete the Unnamed Guests at all. We could not even mark them as "Will not attend." Since many of our biggest donors do not use all of the seats available to them, this makes our event screen show us to be overbooked by about 500 guests. We need to be able to over-ride the number of seats a sponsor is going to use, so it accurately reflects the numbers. Having a lot of unnamed guests that are not going to come just clutters everything else. Also, we occasionally have a larger donor ask if they can bring an additional one or two guests, and we usually let them. So we also need to have a way to add a couple of guests when necessary!