Event Ticketing needs to collect more info
We need more fields to collect information when people register for events. Many of our events are training/seminars and we info on dietary requirements as well as other questions to gauge areas of interest and what topics we should focus on. Our current solution is to use Google forms to collect all of the free form information and then at the end, give them a link to pay for the ticket. This then requires us to manual match up who has registered and who has paid. It is also difficult to keep track of the new ones. Those paying by check is also an issue. Because many of our attendees need an invoice to submit to get a check issued. The reporting also needs to be added onto. There are fields that are being collected, but not reflected on the standard reports. Is this an issue for anyone else?
9/30/2023: Campaigns: Added the ability to add a Request Type to a campaign. This will allow clients to organize more that one request type on a campaign. Request Types can be multiselect or single select. The Request Type Name field can hold up to 255 characters. Current requests will appear in a n/a group until a request type is created and assigned to the request. Clients may take caution in changing since these have all been multiselect to make sure and note which item was selected for the ticket purchaser before modifying the request.
-
Billie Jo Lake commented
We also need the ability to collect other information not only dietary requirements but we also sell tickets that allow the purchaser to make a "tribute" in our program book. It be nice to collect that at the time of the ticket and not to have to follow up with an email.