Cancelling or completing an event
Call an event off (emailing every ticket-holder) or mark it completed - and what each does and doesn't do.
Two end-states close out an event: Cancel (it's not happening) and Complete (it happened). Both are run from the event Dashboard, and the difference in side effects matters.
Cancelling
Cancelling sets the event status to cancelled and emails every ticket-holder automatically. You can include an optional reason, which is shown in the email. Soaly reports how many attendees were notified.
Who gets the email
Every booking with a contactable email address is notified, de-duplicated by email - if one person holds several bookings they're emailed once. Delivery is best-effort: the cancellation still completes even if an email fails to send, so a flaky inbox never blocks the cancel.
Completing
After an event has happened, mark it completed to keep your dashboard tidy. Completing sends no emails and keeps all data - completed events still appear in financial reports.
Cancel vs complete vs delete
| Action | Emails attendees | Refunds | Keeps data | Reversible |
|---|---|---|---|---|
| Cancel | Yes | No (do it manually) | Yes | Status only |
| Complete | No | No | Yes | Status only |
| Delete | No | No | No - permanent | No |