Build walkthrough
Event management, end to end.
One event record, one registration form, reminders, and a follow-up queue that exists the morning after. No separate event tool required for a straightforward hosted event.
The build
- 1
Event object
Name, date, city, capacity, owner. One record per event, not one list with a coded name.
- 2
Registration form
Creates or updates the contact and writes the event name to a multi-checkbox or an associated registration object if people attend more than one event a year.
- 3
Reminders
A workflow seven days out and one day out. Suppress it if the contact property Registered is cleared.
- 4
Attendance
A staff member checks a property or scans into a second form at the door. Attended and no-show must be different values.
- 5
Next-day queue
Workflow creates a task for the contact owner only when Attended is true and lifecycle is not customer. Customers get a different, quieter follow-up.
Paid ticketing, seat maps, and badge printing belong in a ticketing tool. Send the attendee list back as a contact import or a sync.
Campaign around the event.
The event is the record. The emails are just workflows. Keep the campaign name identical to the event name so reporting does not depend on memory.