A fireworks night called off at lunchtime
Your fireworks night is sold out. At noon, the wind forecast crosses the limit your safety plan sets, and the event manager calls it off. Now someone has to tell the ticket holders.
The ticketing system can email everyone, but it cannot offer choices. So the email says 'we will be in touch'. The phones ring all afternoon. Staff start rebooking people into the reserve date by hand, and by evening the reserve date is oversold because two people were rebooking at once. Refunds are processed one by one through the payment provider over the following week.
Why cancellations take days to sort
Ticketing systems are built to sell, not to unwind. Cancelling an event is rare enough that the process is manual: export the list, email everyone, handle replies one by one.
Ticket holders need a choice: a new date, a credit or a refund, depending on your terms. Offering choices by email means reading replies and acting on each one.
Capacity on the new date has to be respected, which is hard when several staff are rebooking by hand at the same time.
The ticket list itself is messier than it looks. Some buyers bought for a family under one name, some bought parking or food vouchers alongside, some bought at the gate the week before and gave a phone number but no email. Each of those needs a slightly different route, and on the day nobody has time to work that out.
What manual cancellations cost
| Step | Problem |
|---|---|
| Telling ticket holders | Vague messages and a flood of calls |
| Offering options | Replies handled one at a time |
| Rebooking | New dates oversold |
| Refunds | Days of processing, and complaints while people wait |
| Records | Unclear who took which option |
The decision to cancel is yours and your safety plan's. What follows should not take the team away from everything else for a week.
A cancellation flow built for the bad day
We add a cancellation flow alongside your ticketing system, ready to use when it is needed.
- The event manager marks the event as cancelled in a simple screen, choosing which options to offer under your terms: a new date, a credit or a refund.
- Every ticket holder gets an email and a text with a personal link to choose their option.
- Choosing a new date shows real availability, and a place is held only when confirmed, so no date is oversold.
- Refunds are processed automatically through your payment provider, such as Stripe, once chosen, and confirmation is sent.
- Ticket holders who do not respond by a deadline get a reminder, then the default option your terms set.
- A dashboard shows how many have chosen each option, and the office handles only the exceptions, such as a group booking or a phone buyer without an email.
Cases we prepare for
- Events cancelled partway through, where your terms may offer a partial credit.
- Tickets bought as part of a package, such as event plus parking.
- Tickets bought at the gate for cash, which need a different refund route.
- Events postponed rather than cancelled, where the new date is set later.
The afternoon of a cancellation, afterwards
At noon, the event manager marks the event cancelled. By 12.15pm, every ticket holder has a message with their options. Most choose within hours. The reserve date fills without being oversold. Refunds are processed that day. The phones are quieter, and the calls that come in are about genuine exceptions.
- Every ticket holder told at once, with clear options
- Rebooking with live capacity checks
- Refunds processed automatically
- The team free to handle exceptions only
Would this help your attraction?
- You run outdoor events that weather can cancel.
- Cancellations mean days of emails and calls.
- Rebooking is done by hand.
- Refunds are processed one at a time.
- You have oversold a replacement date.