How to write an event cancellation email: templates for ticket buyers

An event cancellation email should name the cancelled event and date immediately, explain what happens to the buyer's payment, and say whether they need to do anything. Send it as soon as cancellation is confirmed, even if you need a separate update to explain the refund arrangements.

Your buyer might be arranging childcare, about to book a train, or already outside the venue. They need an answer they can act on. A long apology with "refund details to follow" at the bottom leaves them doing the work.

This guide gives you cancellation email templates for different refund stages, advice on choosing the right recipients, and a sending checklist. It covers permanent cancellation. If you are moving an event to another date, write a postponement notice that explains the new arrangements instead.

What should an event cancellation email include?

Put the information in the order a ticket buyer needs it:

1. Event name, original date and location, plus a clear statement that it is cancelled.

2. A brief, accurate reason and an apology for the disruption.

3. The refund arrangement, including what amount is covered and its current status.

4. Any action the buyer must take, or an explicit statement that none is needed.

5. The next update, if something remains unresolved, and a monitored support contact.

"We are reviewing our options" is not a cancellation announcement. "The event is cancelled" is. Don't make someone open an attachment or follow a link to discover whether they should travel.

Name the affected performance when you run a series. Cancelling the Saturday evening show does not tell a Friday ticket holder anything useful. Include the original start time if several sessions share the same date.

Choose the template below by what has actually happened with the money. Replace every bracketed field and remove instructions that do not apply. The dates, amounts and reasons are fields to fill, not facts about your event or promises made by Loopyah.

Template: cancellation with a confirmed refund plan

Use this when you have approved the refund amount, checked the funding and established how your team will submit the refunds. The refund has not necessarily been submitted yet.

Subject: Cancelled: [event name], [date]

Preheader: [Event name] will not take place. Here is what happens to your payment.

Hi [first name],

We're sorry to tell you that [event name], scheduled for [date and time] at [venue, city], is cancelled. It will not be rescheduled.

[Brief, confirmed reason.]

We will refund [precise amount or description of covered charges] for your booking. This covers [ticket price, included fees and relevant extras]. [Explain any separately handled purchase without implying it is excluded from a refund entitlement.]

We plan to submit your refund to [verified payment destination] by [date]. You do not need to request it. We will email you again once the submission is confirmed, with the expected arrival information for your payment method.

Please do not travel to the venue. If you booked for other people, please share the cancellation with your group.

For questions about your booking, reply to this email with your order number. Our [team name] will respond by [achievable response time].

We're sorry for the disruption to your plans.

[Name and role]

[Organizer name]

Keep "you do not need to request it" only when that is true. If an external seller must handle the refund, identify that seller and its verified process. Don't promise a payment action that another business has not agreed to perform.

Template: cancellation before refund arrangements are ready

Use this when the cancellation is certain but a complete refund announcement would require guessing. The next update needs a real owner and an achievable deadline.

Subject: [Event name] on [date] is cancelled

Preheader: Please do not travel. We will update you about refunds by [date and time].

Hi [first name],

[Event name], scheduled for [date and time] at [venue, city], is cancelled and will not be rescheduled.

[Brief, confirmed reason.] We're sorry for the disruption, particularly if you have already made travel or other arrangements.

We are confirming the refund arrangements with [responsible team or seller]. We have not yet submitted refunds. We will email you by [date, time and time zone] with [the specific information you expect to confirm].

You do not need to submit a refund request while we complete this check. [Use only if accurate.]

Please do not travel to the venue, and share this message with anyone attending on your booking.

If you need help before our next update, reply with your order number. [Named team] is handling cancellation enquiries at [support contact].

[Name and role]

[Organizer name]

This notice buys time to verify facts. It does not replace the refund update. Send the promised update even if your answer is that a specific issue remains unresolved.

Template: urgent cancellation on the event day

When people may already be travelling, put the travel instruction above everything else. Use the additional contact channels available to you and make sure the venue team has the same message.

Subject: Cancelled today: [event name], [start time]

Preheader: Do not travel to [venue]. Today's event will not take place.

Hi [first name],

Today's [event name] at [venue, city], due to start at [time and time zone], is cancelled. Please do not travel to the venue.

[Brief, confirmed reason.] We are sorry for the short notice and disruption.

If you are already at the venue, [verified instruction from the venue team, including where to find help].

[Insert the accurate refund paragraph from the appropriate template in this guide.]

We will send the next update by [date, time and time zone]. You can also find current information at [official event update page].

Please forward this cancellation to anyone attending on your booking. For urgent booking questions, contact [monitored support contact and operating hours].

[Name and role]

[Organizer name]

Never invent a safe meeting point or tell people to wait outside while you check. Confirm on-site instructions with whoever is responsible for the venue. Email supports those instructions; it cannot replace immediate safety communication to people already present.

Template: refund submission confirmation

Send this to the purchaser after checking the individual refund record. A batch being started is not confirmation that every order in the batch has succeeded.

Subject: Refund submitted: [event name], order [order number]

Preheader: We submitted [amount and currency] to [verified payment destination] on [date].

Hi [first name],

Following the cancellation of [event name] on [original event date], we submitted a refund for your order [order number] on [submission date].

The refund is [amount and currency], covering [tickets, included fees and extras]. It is going to [verified original payment method or other confirmed destination].

[Insert the current payment provider's expected arrival information for this payment method, with the starting date clearly stated.]

You do not need to make another request. If the refund has not appeared by [appropriate follow-up date], reply with your order number and we will check its status.

[Include a usable refund reference if one is available and relevant.]

We're sorry again that the event could not go ahead.

[Name and role]

[Organizer name]

If the provider has confirmed a completed refund, say what that confirmation means. "Our payment provider confirms that the refund has completed" is more precise than claiming you have seen the buyer's bank balance. Do not call a pending refund completed.

Template: refund delayed or failed

A missed promise needs a direct update. Send it to the affected purchasers, including people who have not complained.

Subject: Update on your [event name] refund, order [order number]

Preheader: Your refund is [verified status]. Here is our next step.

Hi [first name],

Your [amount and currency] refund for the cancelled [event name] has [verified problem or status]. It has not [specific stage it has not reached].

We previously told you [the expectation you set]. We're sorry that this has not happened.

[Brief explanation of the confirmed cause, without speculation or blame.]

[Responsible team] is now [specific action]. We will update you by [date, time and time zone], even if the issue is still unresolved.

[State whether any buyer action is needed and give the verified secure route if it is.]

Reply to this email with your order number if you need help.

[Name and role]

[Organizer name]

"Please allow more time" is not enough when the original date has passed. Explain what you have checked and what happens next. If the cause is still unknown, say you are investigating it.

Template: a verified action is needed to refund the buyer

Use this only when the payment process genuinely requires information or a choice from the purchaser. Do not make everyone complete a form simply because it is easier to count replies than check orders.

Subject: Action needed for your [event name] refund

Preheader: Please complete [specific action] through [verified service name].

Hi [first name],

We are arranging your [amount and currency] refund for order [order number] following the cancellation of [event name] on [original date].

To complete it, [payment provider or responsible seller] needs [the required information or action]. This is because [confirmed explanation].

Please [clear instruction through the verified secure route]. You can check that this request is genuine by [independent way to contact the organizer or open the official account].

Once you complete this step, [accurate description of what happens next]. [Include an actual deadline and its consequences only if they apply.]

If you cannot complete the step, reply with your order number so we can help. Please do not send full card details or banking passwords by email.

[Name and role]

[Organizer name]

Test the route as a buyer would use it. Check that the destination works without an organizer login and that your support team can help someone who cannot access it.

Explain the reason without writing a defence

Give buyers enough information to understand why the event will not happen. One clear sentence often does the job. For an illustrative venue failure, that might be: "The venue cannot reopen in time for the show, and we have been unable to secure a suitable replacement."

If ticket sales are the reason, don't claim a technical fault. You can say that sales have not reached the level needed to deliver the event and that you have decided to cancel. Avoid publishing private medical details, unconfirmed accusations or a dispute with a supplier.

Take responsibility for the decision you made. "We have decided to cancel" sounds more accountable than "circumstances have dictated a cancellation." Buyers do not need your entire supplier correspondence to understand the outcome.

An apology should recognise the inconvenience to the buyer. "We know you may have made arrangements to attend" does that. A paragraph about how devastated your team feels puts the reader in the position of comforting you.

Describe refunds precisely

Before promising anything, confirm the covered amount, funding, payment route and applicable obligations. Your existing event refund policy is part of that check, but a buyer cancelling their own plans is different from you cancelling the event.

For Australian events, the ACCC's ticketing guidance says consumers are entitled to a refund when the organizer chooses to cancel. It also distinguishes cancellations caused solely by third-party actions, where other rules and ticket terms matter. Don't turn that jurisdiction-specific guidance into a worldwide promise. Check the rules that apply to your sale before announcing exclusions or replacing a refund with credit.

Separate the amount from the arrival date

"Full refund" should not leave buyers wondering whether that includes booking fees. Spell out the covered charges. If parking, accommodation or merchandise was bought separately, explain who handles those purchases and where buyers can ask about them. Don't dismiss possible additional claims with an unreviewed blanket statement.

The date you submit a refund and the date a buyer can see it are different. Stripe's refund documentation explains that refunds can remain pending or fail, and that some appear as a reversal of the original charge. Its guidance also distinguishes submitting the request from its appearance at the customer's bank. Use the current estimate for the actual payment method and situation rather than copying a generic deadline into every email.

Here is an illustrative example. A buyer paid $80 for two tickets and $6 in booking fees, for a total of $86. Your approved arrangement returns the entire $86. Write "$86, covering both tickets and the $6 booking fee." Writing "your tickets will be refunded" leaves the fee unclear.

Now suppose that buyer already received a $40 partial refund before the cancellation. Check the remaining payment record before telling them another $86 is coming. Explain the previous refund and the additional amount separately, with a total that matches what you are returning. Check group discounts and vouchers against the actual paid order too. The current face value of a ticket is not necessarily what that buyer paid.

The point is to prevent a correct event-wide announcement becoming an incorrect promise about an individual order. Where amounts vary, send the general cancellation first and verify each buyer's payment details for the follow-up.

Match the wording to the record

• Planned means your team intends to issue the refund. Say when you expect to submit it.

• Submitted means you have verified the payment action. State the amount, date and destination.

• Pending means the payment process is still waiting on something. Identify the next step.

• Completed means the provider confirms completion. Explain any remaining bank visibility question accurately.

• Failed means you need to resolve the failure and tell the buyer what happens next.

If a payment method requires buyer action, explain it plainly in a separate order-specific message. State the amount, the action, the verified secure destination and any actual deadline. Do not ask buyers to email full card details. An instruction to provide information should match the provider's real process.

Send the notice to everyone affected

Start with the event's actual orders and ticket holders. A newsletter audience is a different group. Some ticket buyers will never have subscribed to your marketing, and some subscribers will not have bought this event.

Separate the cancellation notice from private payment information. Ticket holders need to know that the event is cancelled. The purchaser needs the amount and status of their refund. If a group organiser bought several tickets, ask them to tell the rest of the group, while also using any attendee contact details you legitimately hold.

Check transferred tickets, complimentary tickets and external sales channels. A complimentary guest needs the cancellation notice without a promise to refund money they never paid. A resale transaction may have a different buyer from the person now holding the ticket. Confirm the correct refund recipient with the seller before addressing the email.

Keep sales promotions out of this notice. The UK's ICO guidance on service messages distinguishes administrative messages from marketing and explains that adding promotional content can change that classification. A discount code for your next show can wait. Right now, the buyer needs to understand what happens to this purchase.

Do not paste the entire audience into a visible recipient field. The ICO's email security advice explains the risks of exposing recipients and recommends assessing whether bulk email or other secure methods are appropriate. Use your attendee communication tool and check the recipient selection before sending.

How to handle the cancellation email in Loopyah

The first thing you want to do is stop new purchases. On the event page, open More options and choose Deactivate Event. Loopyah's deactivation guide confirms that this removes the event from search and prevents further ticket sales.

Next, check the orders. Under More options, open Orders. The ticket orders guide explains that each order shows the buyer, ticket type, quantity and payment amount, with refund status in its details. Use those records when confirming payment information.

Prepare the notice using Loopyah's attendee email tools. Loopyah distinguishes event updates from promotions so information about an existing ticket can reach the relevant holders without depending on marketing opt-in. Keep your cancellation email factual and check the event audience before sending.

The attendee email guide describes opening Email Campaigns from the event's More options menu, creating a campaign, choosing ticket types or specific attendees, and sending immediately or scheduling it. Send yourself a test and inspect the names, subject, message and destination links.

Refunding is a separate action. The refund guide explains how to open an order, choose Issue refund, select the ticket and provide payment. Deactivating an event is not evidence that its buyers have been refunded. Check the actual refund record before using the confirmation template.

Check the email before it leaves

Use a recognisable sender name and a reply address someone is monitoring. Put "cancelled" and the event identity in the subject. The preheader, the preview text beside it in many inboxes, should add the practical next step rather than repeat the apology.

Check how the subject looks when shortened on a phone. "An important message from the team about your forthcoming booking" may hide the cancellation entirely. "Cancelled: [event name], [date]" puts the news first. Keep order numbers for messages about a specific payment, and make each follow-up subject describe the change since the last email rather than another vague update.

Keep the important details in selectable text. Buyers should be able to read the cancellation with images disabled. Use short paragraphs and meaningful link labels such as "Read the cancellation update." These choices follow the W3C's accessible writing guidance on clear instructions, headings and descriptive links.

Ask someone who did not write the email to answer these questions from the test:

• Which event and session are cancelled?

• Should the recipient travel or take another immediate action?

• What happens to their money, and what has actually happened already?

• When will they hear again, and who answers questions?

Then check the operational details. Stop scheduled reminders that still say the event is happening. Update the event's public information and brief your venue and support teams. Make sure a reply, a social post and the event page do not give different refund instructions.

After sending, inspect delivery failures and incoming questions. Use an appropriate alternative contact route for affected buyers you could not reach. If several people ask the same question, correct the public update and include the answer in your next message.

Keep a copy of the message, its send time, the selected audience and the promised follow-up. Assign one person to track unresolved payment cases. A buyer who reports a missing refund needs someone to check the order, not another copy of the original announcement. Close the case when you have verified the outcome and explained it to the buyer.

A good cancellation email leaves the buyer with a clear outcome, a truthful payment update and a usable next step. Send the cancellation promptly, then keep every refund promise tied to what your team has verified.