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.
Hello!
I would like to address an ongoing issue that our
institution has been experiencing with our webforms. As you know, we do have people who sign up
for membership in person at our institution.
Of course, by becoming a member, this allows the individual to get
discounts when buying tickets for a certain program.
When a person signs up for membership at our museum and
wants to buy tickets online at a later date, that individual would still need
to register on our website. Now here is
where the problem comes in. When the
member signs up on our website, the registration information must match EXACTLY
to the record we have on Altru, otherwise he/she won‰Ûªt get the discount
benefit. Because there is really no way to
get the member to make an exact match when inputting their information, it is
far too often that we end up with duplicate records.
Because of this, we‰Ûªre constantly receiving phone calls
stating that the member has registered on our website but still cannot get discounts
for certain programs. We have to do a
lot of constituent merging to fix these issues, but I would rather say that
this is something that should be completely preventable. My concern is that we have a rather large
number of members signing up so they can attend our upcoming programs.
For an Idea, is there possibly a way that we can automatically have the member
registered for our website when they sign up for membership at our museum? For example, e-mail them their Login ID and a
temporary password? Or have it texted to
them? This will save our membership
department a huge amount of headache.
7 years later, we would gladly love this feature.
This would be very welcome. We have just decided that when new members join we are going to manually create accounts for them and send the log in information to them in a welcome email, inviting them to change the password. It is not a scalable solution, but for now, we can manage the volume. this seems like a major user experience problem.
This would be a welcome update