Collecting information when someone books an event

Setting the questions

An event can have up to eight registration questions. A question can accept a short answer, a longer answer, a yes or no answer, or one choice from a list.

Staff can add help text, set the order, make an answer required, and decide whether the question is shown during checkout.

Questions during booking

The questions appear below the ticket-holder details. A required question must be answered before payment begins.

The answers are saved against each ticket issued by the checkout. This keeps the answer connected to the person attending, including when one purchaser buys a ticket for someone else.

After answers have been received

After the first answer is stored, staff cannot change the question wording, answer type, choice list, or whether the answer was required. They can still hide the question from future checkouts or change its display order.

This prevents an existing answer from being shown under a question that later means something different.

Reviewing the answers

Event staff can filter the attendee list by a registration question and part of an answer. The same filtered list can be printed or exported as a CSV file.

If a ticket is transferred, the former holder's answers are kept in the event record but are not shown as answers from the new holder.

Screenshots show the product version available when this post was published.

Discussion

Discussion loads here through GitHub-backed comments when JavaScript is available.