Custom fields that follow a contact from one event to the next

Custom contact fields already let you collect anything you like through a request. The piece that was missing: some answers are worth keeping past the one event you asked them on.

Durable fields write through to the contact

A field can now be marked durable (the default for anything new). When a request mapped to a durable field is answered, the answer doesn’t just sit on that request: it writes through onto the contact’s record and becomes part of who they are. Their public liability certificate, their licence, an account code, a standing party size: collected once, carried forward, no re-asking event after event.

A non-durable field still works as a reusable request template, it just keeps the answer on the request and never touches the contact. Use durable for things that are true about the person; leave it off for things that are true only about this booking.

You can see where each value came from

Because both you and the crew member can fill these in, the contact tab badges which values arrived from a crew submission versus your own edits. For an upload field, the contact’s current value is simply the most recent file across every request that fed it.

Change your mind without losing anything

Durability is now editable after a field exists, and the switch is non-destructive. Turn it off and saved contact values are hidden, not deleted, and they come straight back if you turn it on again. Turn it on and new answers start writing through from that point; we don’t rewrite history behind you. The notice tells you exactly what each direction does before you commit to it.