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.

Web forms: preferences applied by individual vs. by group

We have some preferences that apply to an entire group signing up via webforms. Right now, the way we've handled this is to have a "Not applicable" option in the preferences, but it would be nice to specify whether the preference was for an entire party registering or to the specific individuals. For example, it makes sense to specify entree by the individual, since one person in a group may want chicken and the other fish. However, we're using preferences on an event to allow someone purchasing at a sponsorship level -- which is a minimum of a group of four tickets -- to specify how they would like their sponsorship to be displayed. Here are the options we're offering:



* Not a sponsor


* Formal name (individual): "Sponsored by Mr. James X. Jones"


* Formal name (couple): "Sponsored by Mr. and Mrs. James X. Jones"


* Use my organization name: "Sponsored by Company ABC"


* I will supply a unique listing via email



It would be nice if there was only one of these per sponsorship purchase, however we still need to specify the 4-8-10 tickets so the purchaser can supply the names of their guests.



Actually, it would also be nice if we could allow a write-in preference, so they can supply their information with their registration instead of potentially having to do a follow-up email.
  • Guest
  • Jan 4 2016
Events / Fundraising / Web Forms
  • Attach files
  • Dayna Aldridge commented
    March 31, 2016 14:37

    Having a text field would be preferable by far (especially since organizations can't register via web forms), but this would be a step in the right direction.  We have a similar set up, but it looks really unprofessional to have to explain at the top of the form that the registrant should ignore the additional 9 fields because they aren't needed but we can't remove them.

    Attachments Open full size
  • +2

Related ideas