AI in Live Events: Postponed-Show Messages and Refund Replies

Tell ticket holders the same day you decide: say the show is postponed, give the new date or the date you will announce it, and offer a clear choice between keeping the ticket and a refund by a set deadline. AI can draft the notice, FAQ and refund replies from one facts sheet; a person approves every send.

The one thing AI cannot supply is the rulebook. Your ticketing platform's postponement terms, the terms printed at checkout and the consumer rules your buyers fall under decide who is owed a refund, and when. Eventbrite's own policy, for instance, gives an organiser 90 days to name a new date and requires refunds on request once that window has passed. Read yours first, write the decisions down second, and only then open an assistant.

Follow me on Instagram@sagnikteaches

What the ticketing platform has already decided for you

Two platforms show how much the terms vary. I read both in October 2026; yours may differ, so treat them as a guide to what to look for on your own platform's help pages.

Connect on LinkedInSagnik Bhattacharya

• Eventbrite, postponed shows. Its Postponed Event Policy (for events postponed on or after 1 April 2023) treats a show as postponed while it is expected to happen later but has no new date, and as cancelled once it will not be rescheduled within 90 days. The organiser must give a new date within 90 days. Refunds during those 90 days are at the organiser's discretion; after that the organiser must honour refund requests for 45 days even if a date has been set, and keep processing them until the show is rescheduled. Every refund request needs an answer within five business days. Eventbrite holds the payout until the show happens or the new details are published, and it can refund buyers itself at the organiser's cost if the rules are ignored.
• Eventbrite, fees. Its help page on the ticketing fee says refunds after a cancelled or postponed event cover the entire purchase, while an ordinary refund request does not return the fee. Fee terms change, so read the current page for your account before you write "minus fees" or "fees included" in a reply.
• Ticket Tailor. According to its help article on cancelling or refunding an order, cancelling does not refund the payment by itself. You choose a refund to the original payment method through Stripe, Square or PayPal, a voucher, or "No refund or credit", and the buyer gets a cancellation email carrying your reason (limited to 120 characters). Orders that were rescheduled or transferred can only be credited to a voucher (anything extra paid when an order was rescheduled can still go back to the card), and cancelling tickets does not return credits or pay-as-you-go fees already spent.

Two practical consequences follow. If your platform lets you move buyers to the new date in bulk, find out which refund options a moved order keeps before you press the button, because Ticket Tailor's article limits rescheduled or transferred orders to a voucher credit. And a refund can cost you the platform's own fee as well as the ticket money, so put a figure on it before "full refunds" goes into writing.

Subscribe on YouTube@sagnikteaches

Consumer law is the third layer, and it sits above both platforms. In some places a buyer whose event date changes has a legal right to their money back whatever your terms say, and a voucher may not satisfy it. I can't tell you the rule for your buyers, and a chatbot can't be trusted to. Check your consumer regulator's guidance or ask a solicitor once, then write the answer into the facts sheet so every message uses it. The tutorial on drafting a refund policy and checking it against consumer law covers that check in more depth.

The one-page facts sheet every message is written from

The commonest failure in AI-drafted postponement notices is invention. Give an assistant a loose brief and it fills the gaps with plausible detail: a new date nobody has agreed, a refund that "happens automatically", a reason nobody approved. The cure is a facts sheet written before any drafting, with every decision on it and the word UNKNOWN wherever nothing has been decided yet. It holds no names or emails, so it is safe to paste into any assistant.

This one is illustrative, for a small music venue. Your lines will differ; the structure is what matters.

SHOW: [Band name], doors [time], [old date]
STATUS: POSTPONED, not cancelled
REASON WE MAY GIVE: the headliner is unwell (say nothing more about their health)
NEW DATE: UNKNOWN. We will email again by [update date, 7 days from now] with the date or an update
IF THERE IS NO NEW DATE BY [day 60]: we cancel and refund every order without being asked
TICKETS: all existing tickets stay valid for the new date; access and carer tickets move with the main ticket
REFUNDS: on request, full amount including booking fee, until [deadline]; once a new date is announced, requests stay open for 14 days after that announcement
HOW TO ASK: reply to the email or use the link on the order page; we answer within 2 working days
PAYING BACK: we start each refund within 3 working days; the card issuer controls how long it takes to show
NOT COVERED: travel, accommodation, parking, anything bought outside our ticketing page
RESELLERS: we can only refund orders in our own system; resale buyers must ask the seller
CONTACT: box office [name], [phone], 10:00 to 16:00, Monday to Friday
APPROVER: [owner's name] reads every message before it goes
DO NOT SAY: "cancelled", "automatic refund", "we will make it up to you", anything not on this sheet

Three lines do most of the work. STATUS fixes the vocabulary, because "postponed" and "cancelled" carry different consequences on a platform like Eventbrite, and a draft that swaps them can change what you owe. NEW DATE: UNKNOWN gives the assistant permission to say "we don't know yet", which buyers cope with better than a vague hint. DO NOT SAY blocks the two inventions most likely to cost money. The IF THERE IS NO NEW DATE line is your own deadline: with a 90-day clock running, as on Eventbrite, a diary reminder at day 60 leaves time to decide whether to cancel and refund everyone.

Drafting the first notice: prompt, draft and fixes

Paste the sheet under a prompt that confines the assistant to it. This one asks for three formats at once so the wording stays consistent, and ends by making the assistant list its own guesses.

You are drafting notices for ticket holders on behalf of a small venue.
Use ONLY the facts sheet below. Where it says UNKNOWN, say plainly that we don't know yet.
Do not add dates, numbers, deadlines, reasons or promises that are not on the sheet.
Never use the word "cancelled". No emoji, no exclamation marks, and no "we apologise for any inconvenience".
Lead with the decision, then what happens to the ticket, then how to get a refund and by when.

Write three things:
1. An email of 100 to 130 words, with a subject line, addressed to [first name].
2. A website banner of 30 words or fewer.
3. A social post of 60 words or fewer.

Finish with a list headed GUESSES: every detail in your drafts that is not on the sheet, or "none".

FACTS SHEET:
[paste the sheet here]

Here is the sort of email an assistant returns (illustrative):

Subject: [Band name] on [old date] is postponed

Hello [first name], we're sorry to let you know that [Band name] can't play on [old date] because the headliner is unwell, so the show is postponed. We don't have a new date yet, and we will write again by [update date] with either the date or an update.

Your ticket stays valid for the new date, and access and carer tickets move with it. If you would rather not wait, reply to this email or use the link on your order page by [deadline] and we will refund your ticket in full within 3 to 5 days.

Questions? The box office is on [phone], 10:00 to 16:00, Monday to Friday.

Four fixes before it goes anywhere:

1. "We're sorry to let you know" delays the decision. Open with the status, then apologise once, briefly, if at all.
2. "Within 3 to 5 days" is not on the sheet, which says refunds start within 3 working days. Assistants rephrase numbers; compare every figure against the sheet.
3. The draft dropped the IF THERE IS NO NEW DATE line. That sentence is the commitment that stops buyers refunding in a panic, so put it back.
4. The GUESSES list said "none" while the draft contained the invented "3 to 5 days". The self-report is a prompt for your own check, never a substitute for it.

For contrast, this is what an owner might fire off late at night with no sheet:

Hi all, big news, due to circumstances beyond our control Saturday is off for now!! We're working on something and will let you know. Refunds available if you need them, just message us. Thanks for understanding.

It never says whether the show is postponed or cancelled ("off for now"), gives no deadline or method for refunds, says nothing about the ticket staying valid and offers no contact route. Each gap turns into its own message from a worried buyer, which is how a twenty-minute job becomes a three-day inbox.

One decision, five channels, four groups who need their own line

The facts sheet feeds every channel, so the website, the email, the social post and the person answering the phone say the same thing. Ask for each format in the same prompt and give each a job.

Order matters: buyers should not learn about a postponement from a social feed before their inbox. Eventbrite's postponed-event policy asks organisers to share the change through its own email tool, and the platform's own email is the sensible route on any system, because it reaches every order without you exporting a mailing list.

Some buyers need a different sentence from the standard email. Ask the assistant for one variant per group from the same sheet, then compare each against the main email: only the group line should differ.

• Access and carer tickets. If the sheet says carer tickets move with the main ticket, say so in the first line, and invite a reply about access arrangements for the new date.
• Group bookers. One person holds ten seats. If your platform ties refunds to the name on the order, tell that person to pass the message on, because their friends cannot ask for refunds themselves.
• Add-on buyers. Parking, merchandise bundles and drinks packages each need a line on the sheet saying what happens to them. Without one, the assistant will guess.
• Guest list and complimentary tickets. These holders are not in the ticketing system, so someone rings or messages them. Give that person the phone script, not the email.

The second email: new date fixed, keep, pass on or refund

When the date is set, update the sheet first, then regenerate. Change the NEW DATE line, replace the refund deadline with the new rule (say 14 days from the announcement) and add a TRANSFERS line if your platform lets buyers pass tickets on. Then use a short follow-up prompt.

Using the updated facts sheet, write the second email to ticket holders in 90 to 110 words.
Open with the new date and time. Then give three options in this order: keep the ticket (no action needed),
pass it to someone else (only if the sheet has a TRANSFERS line), or ask for a refund by [deadline].
Do not describe the new date as exciting or better. List any guesses at the end.

A typical result reads like this (illustrative):

Subject: [Band name] is now on [new date]

Hello [first name], the postponed show is now on [new date], doors at [time]. Your ticket is valid as it is, so if the date suits you there is nothing to do. If you would rather pass your ticket to someone else, use the transfer link on your order page. If the date does not work, reply to this email by [deadline] and we will refund the order in full. Questions to the box office on [phone].

What to check: the deadline is 14 days after you actually send, not 14 days from the day you wrote the sheet, and the transfer sentence matches a feature your platform really has. On Eventbrite, remember the policy above: once 90 days have passed since the postponement notice, refund requests must be honoured for 45 days even if a date has been set, so a 14-day window offered after day 90 would be too short.

Refund replies: six situations and who decides each

Postponements produce a handful of repeat questions. Group them, decide the answer once on the sheet, and let the assistant write the reply from the sheet plus the buyer's message. The decision comes first and is always a person's.

A card dispute is a buyer asking their card issuer to reverse a payment, and your payment processor may add a fee on top. An unanswered refund request is the usual route to one, which is why a holding reply within two working days beats a perfect reply on day six. Set your own clock shorter than the platform's five business days.

The reply prompt carries the decision in a single line, so the assistant never gets to decide:

Draft a reply to the ticket holder's message below. Use ONLY the facts sheet.
The owner has already decided: [APPROVE REFUND / DECLINE: RESELLER ORDER / OFFER VOUCHER AND KEEP REFUND OPEN].
Under 90 words, warm and plain. Use [first name] and [order number] as placeholders.
If the message asks for anything the sheet does not cover, do not answer it; list it under QUESTIONS FOR THE OWNER.

FACTS SHEET: [paste]
MESSAGE: [paste, with name, email and phone number removed]

Take this illustrative message: "Hi, I bought two tickets for Saturday but I'm working away on whatever the new date turns out to be. Can I get my money back, and do I get the booking fee back too? Thanks, [first name]". The assistant's draft:

Hello [first name], yes, you can have a full refund for both tickets, booking fee included. I have started it on order [order number]; we start refunds within 3 working days, and your card issuer decides how long it takes to show. You do not need to do anything else. We will hold two seats for you when the new date goes on sale.

The last sentence is the classic invention: nothing on the sheet promises held seats, and a promise like that is expensive to honour. Delete it and send the rest. The same message, run through the prompt with "DECLINE: RESELLER ORDER" because the buyer's confirmation came from a resale site, should return something shorter: we can only refund orders made through our own ticketing page, the seller named in your confirmation email is the one to contact, and here is the box office number if you are unsure who sold you the ticket.

For the sixth row, the furious message, let the assistant produce a draft if it helps you get started, then rewrite it in your own voice. A buyer who is angry about a postponement can tell when the reply came from a machine, and the tutorial on replying to a customer demanding a refund has wording for that moment.

Question-and-answer lines for the box office and event page

Ask the assistant for ten likely questions with answers, again only from the sheet, then ask it to find any answer that contradicts the sheet or another answer. That second pass catches the quiet drift where one answer says "within 3 days" and another says "within a week". Five lines from an illustrative set:

• Has the show been cancelled? No, it is postponed because the headliner is unwell. We don't have a new date yet; we will update this page and email every ticket holder by [update date].
• Do I need to do anything to keep my ticket? No. Your ticket stays valid for the new date, and access and carer tickets move with it.
• How do I get a refund? Reply to the email we sent you or use the link on your order page before [deadline]. We answer within two working days and start the refund within three.
• Will you refund my travel or hotel? No. We can only refund tickets bought through our own ticketing page, so check the terms of any travel you booked.
• I bought through another website. Can you refund me? Only the seller can. We can refund orders made through our ticketing page; your confirmation email shows who sold the ticket.

Put the set on the event page under the banner, print it for the box office and paste it into the booking-confirmation email if your platform allows edits there. The tutorial on writing ticket-page copy with AI covers how to keep the page itself clear once the postponement banner is up.

A 240-ticket postponement, hour by hour and sum by sum

Take a 300-capacity room with 240 tickets sold at $26 each, booking fee included, across 171 orders, a gross of $6,240. All figures here are illustrative, and the time estimates assume ten minutes to write a reply by hand and three to review an AI draft.

Two sums are worth doing before the notice goes out, not after. First, the exposure: 32 tickets at $26 is $832, but if a quarter of the room had asked, 60 tickets, the figure would be $1,560. On a platform that has already paid you out, refunds come from your own balance, so check that the money is there. Second, the clock: the new date landed on day 21, well inside Eventbrite's 90-day window. Had the headliner's recovery been uncertain, the day-60 reminder on the sheet would have forced the decision to cancel and refund everyone while there was still time to do it on the organiser's terms.

The AI saved just over three hours of drafting (203 minutes) in the first 72 hours, but the quality gain mattered more: all 29 replies used the same figures because they came from the same sheet.

Eight checks before anything is sent

A person approves every message, and the approval is a checklist, not a glance. Whoever is named as approver on the sheet works down it each time.

1. Status word. "Postponed" or "rescheduled", exactly as the sheet says, and never "cancelled" by accident.
2. Every number. Copy each date, time, amount and deadline from the draft into a list and tick them off against the sheet.
3. Money words. Refund, voucher, credit and exchange each mean something different on your platform. Use only the ones you intend.
4. Promises. Hunt for "automatically", "guaranteed", "priority", "first access" and "we will make it up to you". The check for promises you never made to customers is built for this.
5. Reason line. Only what the sheet allows. Do not let a draft speculate about illness, safety or the artist's reasons.
6. Working routes. Click the refund link and ring the number before sending.
7. Tone. One apology at most, no jokes, no emoji, no exclamation marks.
8. Leftovers. Nothing left in square brackets, and the right show name and venue throughout.

The assistant never sends anything. Drafts are pasted by a person into the platform's email tool or the mail client, and a person presses send. That also means no auto-reply connected to a chatbot for this job, however tempting during a busy first morning. If your ticket page has a chat widget that answers questions on its own, update what it knows the minute the notice goes out and make sure it says it is an automated assistant; if you have customers in the EU, the transparency duty for chatbots under the EU AI Act applies to it.

When a draft promised an automatic refund

An illustrative case of how one sentence builds a large inbox. A venue's AI-drafted notice said, "You will be refunded automatically within five working days." Its platform required each buyer to request the refund. Nothing moved for nine days. By then 40 buyers were waiting, 11 had written to ask where their money was, and 3 had gone to their card issuers.

The warning sign was in the inbox: the same question, "where is my refund?", arriving eleven times in a morning. The repair took three steps. A corrected email went out the same day naming the real route. The sheet gained a line, REFUNDS ARE NOT AUTOMATIC: the buyer must ask. And the approver added a rule that no draft may contain a timing the sheet does not hold. Two hours of checking at the start would have cost less than the nine days of damage.

Refunds, fees and buyer data: the costs that matter

Drafting needs only a few thousand words of text, so a free assistant plan is usually enough. A paid plan at about $20 a month (ChatGPT Plus and Claude Pro both list at that price) is worth it only if you will use it for other work too. The costs that matter sit elsewhere: the platform fee that may not come back, the refunds themselves, and staff time during the first 72 hours.

Keep personal data out of the assistant. The sheet needs none. For individual replies, paste the buyer's message without their name, email or phone number, and add them back when you send. On consumer plans, find the switch in privacy settings that controls whether chats are used for model training and turn it off; business plans such as ChatGPT Business and Claude Team don't train on your content by default. Whatever you use, check the setting yourself, because labels change.

If postponements are rare for you, the sheet is the only thing worth keeping between incidents. Fill in a blank copy now, with UNKNOWN on every line, and store it beside your ticketing login. The first morning of the next disruption then starts with a form to complete rather than a blank page, and the venue's cancellation terms (see cancellation and deposit terms for event venues) are already settled when you need them.

Questions promoters ask after the notice has gone out

Should the message say postponed or rescheduled?

Say postponed until a new date is confirmed, and rescheduled only once it is. Avoid cancelled unless the show will not happen, because on some platforms the word changes your refund duties. Eventbrite, for example, treats a show with no new date inside 90 days as cancelled.

Can I offer a voucher instead of a refund?

A voucher can be a kindness for buyers who want one, but it should not replace a refund they are entitled to. Whether they are entitled depends on your platform's rules, your terms of sale and the consumer rules where they live, so check those before the offer goes into a message.

How soon should I tell ticket holders?

On the day you decide, ideally within a few hours, even when you do not know the new date. A short honest message saying what is known, what is not and when they will hear next cuts the number of repeat questions far more than a polished message sent days later.

Is it safe to paste ticket buyers' details into an AI assistant?

Not by default. The facts sheet holds no personal data, and replies can be drafted from the buyer's message with the name, email and phone number removed. Turn off model training in the privacy settings of a consumer plan, and add the personal details back yourself when you send.

Further reads

• AI for Marketing an Event: A Six-Week Promotion Plan for Venues — Sell the new date with a six-week promotion plan.
• Event Feedback Survey: Write It and Summarise the Answers With AI — Ask the crowd what they thought once the rescheduled night has happened.
• How to Use AI in the Travel Industry: Weather Cancellations for Tours — A parallel case: weather cancellations, with messages and refunds.
• Venue Booking Software: Calendar, Deposits and AI Replies Compared — Compare calendar and deposit tools for running the venue itself.
• How to Automate Returns and Refunds With Clear AI Rules — Write clear refund rules before any AI drafts a decision.
• Tour Cancellation Policy: Draft the Wording and Customer Messages With AI — Build a tour cancellation policy from your costs, have AI draft clauses and customer messages, then test it on real situations before a solicitor reviews it.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: Eventbrite help pages on its Postponed Event Policy, Cancelled Event Policy and ticketing-fee refunds, and Ticket Tailor's help article on cancelling or refunding an order, all read in October 2026.