Events

Every event needs two surveys: one before and one after. They do different jobs. Registration has to be short and protected from bots, because the list decides badge printing and catering numbers. Feedback has to go out within a day, while people still remember which talk they liked; a week later only a handful will answer.

For sign-ups there is the event registration form: name, an email for the ticket, company, city, attendance format as cards and the tracks people want. It ends on consent and a captcha. If entry is age-restricted, use the 18+ event sign-up: from the date of birth, the logic graph sends an underage visitor to their own final screen before the form asks for contacts, and a separate screen catches dates that have already passed.

Afterwards, send the event feedback survey. It has an overall star rating, a matrix on the organisation, a ranking of what people want next time, a question about coming again and an email field for the next invitation. A QR code on the closing slide gets far more answers than a link sent days later.

Both forms work as a link, a QR code or a widget on the event site. Connect registration to a CRM or a spreadsheet through a webhook so the attendee list updates itself. In the feedback survey, skip what you already know from registration: name, company and city do not need asking twice if the link goes to the same people. The shorter the post-event survey, the more answers you get from people already heading home.

Branching like the age check is easier to reason about on a canvas than in a list of rules; why surveys need a visual logic editor explains the difference. Tickets, attendee lists and registration settings are covered on the event registration page.