Collect interest in an event

This recipe records interest or a request for information. It does not create a booking, ticket, payment, or guaranteed reservation.

State the outcome clearly

Use the introduction and success message to say whether the visitor is:

• Asking to be contacted
• Joining an interest list
• Requesting event details

Do not label the final button “Book” or “Reserve” unless another verified system completes that action.

Build the form

1. Create a form under Forms → Add New.
2. Add Text named name.
3. Add Email named email.
4. Add Select or Radio named event_interest when the page covers multiple events.
5. Add Number named party_size only when the team needs an estimate; set a sensible minimum, maximum, and integer-only rule.
6. Add optional Textarea named access_needs when the organizer has a defined way to use the answer.
7. Add consent or privacy fields as required.
8. Add a specifically labeled Submit Button.

On a page dedicated to one event, a Hidden field can carry a non-sensitive event reference. Treat it as context only; browser-submitted hidden values are not authoritative.

Route and confirm

1. Create an administrator notification for the event team.
2. Use {{current_page_title}} or {{field:event_interest}} in the subject.
3. Set Reply To to the submitted Email field.
4. Optionally send a client acknowledgement that repeats the event label and explains the next step.
5. Store submissions only when the team needs a managed list and has an approved retention period.

Verify every event path

Submit each event choice and confirm the correct team receives it. Test an unavailable or changed event option before altering its stored value, because routes and external receivers may depend on that value.

If actual registration is required, connect a supported external workflow through a webhook or action endpoint and verify that destination separately.