Additional functionality needed for Event Participant Options

As we prepare for larger events to resume next year, it's becoming clear that the current functionality of event registrations will not be sufficient for the data we typically collect and manipulate. I'll use our VBS as an example of the functionality we need. (We previously used Eventbrite.)

In Participant Options:

  • Character limit is much too small in "Option Name"

  • Date should be an available "Input Type"

  • We need the ability to create Conditional Sub-Questions (if "yes," additional questions appear)

In Fees:

  • We need to be able to designate a maximum number for each ticket type, not just per registration, so that when each ticket type sells out, it is no longer available. (CRUCIAL)

  • We need the Ticket Type to be an available column in the participant list. (CRUCIAL)

  • Ideally, we also need waitlist functionality (less important, but it would be nice).

It would be great to use Blackbaud for large events that require registration, but currently the functionality would be inadequate. Thanks for considering these enhancements!

  • Catherine Montgomery
  • Dec 3 2020
  • Reviewed: Voting Open
Events
  • Attach files
  • Catherine Montgomery commented
    December 08, 2020 16:29

    Thanks, Samantha! Answers below:

    1) Here's an example of a question we have asked on a VBS registration form: If your child has special needs, do you feel that he/she would benefit from having a buddy during VBS? This would be an additional adult or older teenager who would very discretely be there to support your child only.

    2) Yes, birthdate is the most likely need for a date format. Our VBS includes many kids who are not members, for whom we would not have a birthdate on file.

    3) The current waitlist functionality we love works like this. A person clicks a link to register for specific ticket type for a grade level. It's full, and the person can select to be added to the waitlist. As spaces become available (if someone cancels or additional spaces are created), the person gets an automatic email with a registration link that is valid for 24 hours, after which they lose their place in line. So they don't actually register until their spot becomes available. The great thing is that this is automatic. The waitlist feature is built into the event on the front end, and kicks in immediately when a ticket type reaches the set capacity. As an event "owner," I don't have to do anything with it at all once the functionality is defined when the event is created.

    Thanks for your help!

    Catherine

    Attachments Open full size
  • Admin
    Samantha McGuin commented
    December 08, 2020 14:54

    Thanks for providing this feedback, Catherine! I have a few followup questions:
    1) Character limit length. Can you give me an example of how you're wording these? Are you putting these in question format and that's where you're running out of room?
    2) Input type of Date - are you collecting birthdates or other distinct date fields about the participant or asking for a date entry for another reason?
    3) Waitlist functionality - are you wanting people to fill out the registration form to join the waitlist? What would your workflow be for waitlisted participants?

    I'm also going to add some new Ideas for your fee suggestions. I want to ensure that each of these can be voted on individually. I'll add you as the owner so you still get notified of any movement on them. Thanks again!

    Attachments Open full size

Related ideas