How to handle a ticket buyer's death or serious illness compassionately

Someone emails your event team to say their partner has died. They bought two tickets months ago and won't be coming. Your usual refund deadline passed last week. The person answering the inbox knows the rules, but nobody has told them what they can do in this situation.

Start by acknowledging what happened, take ownership of the request, and check whether the buyer already has a right to a refund. Where you're considering a compassionate exception, make the decision through a clear, proportionate process. Ask for as little sensitive information as possible, give staff enough authority to help, and follow the approved refund through to completion.

You can run a commercially responsible event business and treat this person with care. That takes preparation. A sympathetic reply followed by repeated requests for documents, conflicting decisions and an unresolved payment is still a poor experience. The useful work happens behind the reply, where your team decides who can approve what and how the money will move.

This guide covers requests involving serious illness, a ticket buyer's death and bereavement that prevents attendance. It explains how to define an exception, handle group bookings, verify a representative and write replies that don't make someone explain their circumstances to several people. The examples are suggested operating choices for your team to review, rather than universal legal rules. All hypothetical money amounts are in US dollars.

First, work out which kind of refund request you're handling

Read the whole message before checking the cancellation deadline. A buyer may mention illness while also explaining that you moved the event to an inaccessible venue. Another may be asking for a refund that falls within the terms you already offered. Neither should have to qualify for a special favour to receive something they're entitled to.

Separate the buyer's applicable rights, the refund promises attached to their booking and any additional help you're willing to provide. An existing entitlement goes through the ordinary refund process. A compassionate exception concerns help beyond that entitlement. An unresolved question about rights goes to someone qualified to assess it, without asking the buyer to prove hardship first.

For Australian sales, the ACCC's event-ticket guidance explains that an organiser's decision to cancel or make a major event change can entitle consumers to refunds. It also distinguishes other circumstances where the reason, contract and applicable law matter. That guidance doesn't establish one worldwide answer for personal illness or bereavement. Check the rules for the markets in which you sell.

Your general event refund policy should already explain ordinary cancellations and changes. Use this additional process for the sensitive situations that need a person to take responsibility. A disabled refund button or an expired voluntary window doesn't settle the legal position, and a support agent shouldn't describe a required refund as an exceptional act of generosity.

Consider a hypothetical buyer with a serious illness who purchased a ticket carrying an unused refund option. If they can already cancel under the agreed terms, help them use it. There's no reason to ask for a medical letter. The business has already promised the refund, and the buyer's private circumstances add nothing to that decision.

Now consider a different buyer asking after the voluntary deadline, with no separate entitlement identified. Your exception policy determines who can approve additional help and what information they need. Keeping those cases separate protects the buyer from unnecessary questions and gives your team a clearer explanation of why they made each decision.

Decide what you can offer before the difficult email arrives

Write the exception with your support and finance leads. Decide which circumstances it covers, which tickets may qualify and who can approve a request. Include an escalation route for cases that don't fit neatly. If the only instruction is "use your judgment," two well-meaning people can give opposite answers to the same situation.

A practical policy might cover a ticket holder who is too seriously ill to attend, a necessary companion who can no longer attend with them, and a booking affected by a death. You still need to define the scope for your event. Decide whether you include a person providing care, and how you assess other people on a group order.

Avoid a rigid ranking of whose loss deserves sympathy. Family structures vary, and a relationship label doesn't tell your team how the booking has been affected. Ask which ticket holders cannot attend and what help is being requested. A manager can review unusual relationships or circumstances without asking the support agent to judge how much someone ought to grieve.

Write the first reply so the person knows what happens next

Keep the opening brief and specific. "I'm sorry to hear about your partner's death" acknowledges what they've told you. "I'm sorry you're dealing with this illness" can work when the person has described their own situation. Follow their wording and avoid assumptions about their prognosis, family or feelings.

Bereavement charity Sue Ryder's guidance on what to say recommends acknowledging a loss and avoiding attempts to make it sound less painful. For a ticket-support reply, that means leaving out explanations about everything happening for a reason or the person being in a better place. You don't need to find comforting words that solve their grief.

Then take responsibility for the booking problem. Tell them who is reviewing the request, what you need to locate the order and when you'll next contact them. If you can resolve it immediately, do so. If another person must approve it, explain that you've passed it to the named role and will keep the conversation in the same thread.

Here's an example acknowledgement for a request you haven't approved yet: "I'm sorry to hear about your partner's death. I'll handle the ticket request for you. Could you send the booking reference and tell me which tickets you want us to review? Please don't send medical records or a death certificate at this stage. I'll update you by tomorrow afternoon."

Use that timing only if your team can meet it. A small operator might set a next-business-day update, while an event opening tonight needs an urgent route. The promise should describe the next contact, not imply that a bank will return money within the same period. Those are different commitments, and confusing them creates avoidable worry.

If the buyer has already provided the reference and ticket details, don't ask again. Confirm what you've understood instead. Repeating the request makes the reply look unread and adds work for someone who may be handling many difficult tasks. A few seconds checking the thread can prevent another exchange and a needless delay.

Let someone help without demanding account access

A person receiving treatment may ask a partner or friend to handle the booking. Allow a representative to explain the situation through your support route, then verify the authority needed for the specific action. Receiving information, disclosing booking details, cancelling tickets and changing where money is sent carry different consequences.

Don't tell the representative to log in as the buyer or share a password. If the buyer can provide consent through your approved process, use that. Where they cannot, escalate the authority question. Explain the next step in ordinary language, and avoid treating inability to access an inbox as evidence that the request is dishonest.

Someone may need help using a form because of illness, disability or language. Offer an accessible alternative your team can operate securely. The aim is to establish the necessary booking facts and authority, rather than test whether the person can complete a particular online journey unaided. Record the agreed contact so other staff know where updates should go.

Ask for the minimum information needed to make the decision

Start with the booking. You usually need enough information to find the purchase, identify the affected tickets and understand the requested outcome. That might be an order reference, event date and clarification that one of several ticket holders cannot attend. It doesn't automatically require a diagnosis or a copy of a medical document.

Treat evidence as a decision you must justify internally. What uncertainty would this document resolve? Would a brief statement answer the question? Could an authorised manager approve the exception without collecting it? If the team cannot explain why a document changes the decision, remove it from the standard request rather than collecting it because that's what another business does.

The UK's Information Commissioner's Office describes data minimisation as keeping personal data adequate, relevant and limited to what's necessary for the purpose. Its guidance is currently under review following legislative changes. Have the process checked against the privacy rules that apply to your operation, including what you collect, who sees it and how long it remains necessary.

Health information needs particular care. Under the ICO's special-category data guidance, processing this information under UK GDPR requires an appropriate general lawful basis and an applicable special-category condition. The guidance is also under review. A customer voluntarily attaching a document doesn't remove your responsibility to establish how you may handle it.

Build a reviewed evidence procedure before requesting health information. If limited confirmation is genuinely necessary, explain the purpose and the approved secure route. Ask the person to exclude unrelated details where appropriate. Don't ask for a complete patient record or contact a clinician just because the buyer has said they are unwell.

For example, you might need confirmation that the person couldn't attend on the event date, rather than the name of their condition. Your privacy lead should decide whether collecting that confirmation is necessary and lawful at all. Support staff shouldn't improvise consent language or assume that every medical attachment can be saved in the ordinary customer record.

Keep the decision record separate from the private story

The person approving the case needs enough information to apply the policy. The person checking the payment needs the approved amount and transaction details. The door team needs the correct admission status. These people rarely need the same view of the request. Design access around what each role must do.

A general operational note can say, "Exception approved by the duty manager; ticket B cancelled; refund submitted; follow-up due Friday." It doesn't need to reproduce a diagnosis or a family member's account of a death. Where sensitive material must be held, restrict it through the reviewed process rather than copying it into every booking note.

Set retention rules by purpose and applicable obligations. A payment record may need to remain after an evidence document is no longer necessary. Have the responsible person define those periods and deal with any legal hold. "Delete everything as soon as we reply" and "keep the whole email forever" are both poor substitutes for an actual retention decision.

If someone sends an unexpected attachment, don't circulate it while asking colleagues what to do. Use your privacy procedure, limit access and ask the responsible person how to handle it. You can often continue locating the booking while that question is resolved. Don't make the customer resend the same information to multiple staff members.

Use checks that address the actual risk

Compassion doesn't require sending money to whichever account appears in an email. Verify the order and the action through your approved payment procedure. Watch for conflicting ticket numbers, an existing refund or an unexpected request to redirect funds. Investigate those booking or payment discrepancies without demanding more intimate information about the illness.

If a detail doesn't match, state the discrepancy neutrally. "The reference you sent is for a different date. Could you check the event name on the receipt?" is more useful than challenging the person's circumstances. People dealing with an emergency can make mistakes, and an accurate booking check helps resolve them without turning support into an interrogation.

Give staff authority that matches the help you expect them to provide

A policy can't work if every request waits for a founder who is busy producing the event. Decide what a trained support person can approve, what a duty manager can approve and what finance or another specialist must review. Base those permissions on your actual event, ticket values and payment controls.

For a hypothetical event, you might let a trained agent approve one eligible compassionate ticket refund up to $100, with a manager reviewing larger requests and group bookings. That amount is an invented training example, not a recommended limit. A higher-priced conference would need a different arrangement, and a required refund shouldn't be refused because it exceeds someone's discretionary authority.

Assign a backup approver and a response target. If requests arrive outside office hours, tell staff which ones need immediate attention because the event is starting and which can wait for the next working period. Keep ownership with one person even when an approval comes from elsewhere. The customer shouldn't have to find the right colleague themselves.

Record the reason for the outcome in terms your team can apply again. "Approved under serious-illness exception for affected ticket holder and necessary companion" explains more than "manager discretion." Use a less specific operational note where privacy requires it. A restricted decision record can hold the detail needed for a later consistency review.

Consistency means applying the same relevant criteria. A quiet email shouldn't receive less help than a public complaint, and a familiar customer shouldn't receive automatic priority. At the same time, a group booking, a deceased payer and a single unused ticket can require different checks. Document why those differences matter instead of forcing every request into one answer.

Decide what happens when the request arrives late

Illness and bereavement don't follow your inbox schedule. Decide whether your team can review requests after the event and under which circumstances. Someone admitted to hospital may be unable to contact you before doors open. A representative may only discover the booking later. A blanket timing rule can miss the very situations the exception was intended to address.

Set a reasonable published contact expectation and an internal route for delayed requests. Explain that your team will consider the circumstances rather than promising unlimited retrospective refunds. The reviewer should establish what happened to the ticket, any existing entitlement and what additional help the policy allows. Don't require a person to prove that they were incapable of emailing at an exact minute.

Check admission information carefully. A scan record may help establish that a ticket was used, but it can also be mistaken or concern another person in the order. Investigate a conflict before making an accusation. Your ticket management process should help staff identify the individual ticket rather than assume every ticket on a booking had the same outcome.

Handle the affected tickets without cancelling the whole group's plans

A booking can include a payer, several ticket holders and a companion. Start by identifying who cannot attend and which tickets the request concerns. If one person is ill and the others still want to come, cancelling the entire order can create a second problem. Confirm the proposed action in plain language before making a change that affects everyone.

Imagine a fictional order for four $80 tickets, paid by one buyer. Two ticket holders cannot attend because one is seriously ill and the other is providing necessary care. Your reviewed exception covers both, and the other two people still plan to attend. The proposed ticket refund is $160, with two admissions remaining valid, before any separately identified fee or tax treatment.

Don't turn that calculation into an automatic rule about companions. Your own policy needs to say how they are considered, and the buyer's rights may change the answer. The example simply shows why a ticket-level decision matters. It also shows why the person communicating with support needs to understand which admissions will remain usable.

Ask for confirmation that can be answered easily. "We're reviewing tickets A and B for a total ticket refund of $160. Tickets C and D would remain valid. Is that the change you're requesting?" Use your real ticket identifiers and a verified total. Avoid sending a full attendee list to someone whose authority to see it hasn't been established.

The W3C's financial error-prevention guidance describes ways to prevent consequential submission errors, including review, correction or reversal. Apply that principle to your support journey. Give people a clear chance to correct the selected tickets and amount before an irreversible action, using an accessible route rather than a rushed phone conversation alone.

When the person who paid has died

Distinguish the person attending from the person who paid. The deceased person may have bought tickets as gifts, so cancelling every admission could be the wrong action. A relative may be asking about only one ticket, the whole order or the destination of a refund. Establish the request before deciding which procedure applies.

A death also creates questions about authority and money that a support agent shouldn't settle from a surname alone. In the UK, GOV.UK's estate guidance explains the responsibilities of an executor or administrator for the deceased person's assets. Other jurisdictions have their own rules. Use the appropriate finance and legal route to verify authority where needed, without assuming every ticket request requires the same probate documents.

Don't promise to send money to a relative's new bank account simply because the original payer has died. Explain that the payment team must check the permitted refund route and any representative requirements. Keep the compassionate decision and the safe payment decision connected. You can approve help while still needing a specialist to establish how it can be paid correctly.

Tell the representative exactly what remains unresolved. "We've approved the requested ticket refund. Our payment team is checking the return route because the original payer has died. I'll update you on Friday even if that check is still open." This avoids making them repeat the story while giving an honest account of what your team has and hasn't completed.

Offer alternatives only when they are useful to the person

A transfer can help a buyer who wants someone else to use their ticket. A later date can help someone who expects to attend another performance. A cash refund may be the most appropriate answer when a person is seriously ill or a family is dealing with a death. Don't assume keeping the purchase within your business is a helpful outcome for them.

Ask about preferences without creating a negotiation. If you've approved a cash refund, state that clearly before mentioning an optional alternative. The buyer shouldn't have to decline several retention offers to receive it. Where a refund is required, don't substitute compulsory credit merely because that is easier for your event's cash position.

If the person chooses a transfer, check the actual supported process and any restrictions. Confirm who will receive the ticket and what happens to the old admission. If they choose credit, explain the value, eligible events, expiry and any price difference before acceptance. A vaguely described invitation to "come next time" can create another unresolved obligation.

Don't make resale a condition of a compassionate refund you've already approved. Resale depends on another buyer and may take time. If resale is the available voluntary option under a different policy, explain that outcome honestly and check that it doesn't conflict with rights already due. The person should know whether money is approved or merely possible.

Keep general flexibility separate from exceptional support

There is a commercial reason to explain refund terms before purchase. In Loopyah's 2025 attendee survey, people responded differently when asked how a hypothetical offer of full refunds until 48 hours before an event would affect their buying time. The chart shows the whole set of answers rather than only the group who said they would buy much earlier.

Source: Loopyah Event Attendee Insights Report, Q12, Pollfish survey of 500 US respondents fielded November 11, 2025. These are unweighted, single-choice responses to a hypothetical offer, including respondents who reported no live-event attendance in the preceding year. Read the full attendee report for the question and methodology. This measures stated buying timing, not compassionate-refund demand, actual sales or the effect of any exception policy.

The distinction matters when you review results. An ordinary refund window is a promise that eligible buyers can use. A compassionate exception is additional help for a particular situation. You shouldn't advertise a broad refundable ticket and then quietly require medical evidence. Equally, a carefully described exception doesn't promise unlimited change-of-mind refunds to every buyer.

Write the public summary with that difference in mind. Explain where ordinary refund terms can be found and how someone can contact your team about exceptional circumstances. Avoid using sensitive cases as a promotional angle. The aim is to make help discoverable before it is needed and to have the team prepared to provide it.

Write a public exception summary the team can honour

Your public wording needs to make the route easy to find without promising that every difficult circumstance produces the same outcome. Explain who to contact, what booking information helps and that someone will review exceptional requests. Keep detailed approval limits internal. Buyers need to understand the help available, while staff need the fuller instructions for applying it consistently.

For a policy offering discretionary review, you could write: "If serious illness or a death affects your booking, contact our support team with your order reference and the tickets affected. We'll review the request under our exceptional-circumstances policy and explain the available options. Please don't include medical records in your first message. This process doesn't limit any refund rights you already have."

That is sample wording to adapt and have reviewed. If your policy promises a refund in defined circumstances, say so instead of making a promised benefit sound uncertain. If you offer only certain forms of help, explain those accurately. The published summary and the private instructions should describe the same policy, even though they contain different levels of detail.

Put the contact route where a buyer will look for it, including the refund information and booking confirmation. A buried social-media post isn't a dependable support channel. Check whether the confirmation routes replies to a monitored inbox, and make the event date visible so someone handling several bookings can identify the right purchase without opening every receipt.

Deal with an event-day request without a public conversation

A sensitive request may reach the box office because that is the only team the person can find. Give door staff a short instruction for moving the conversation somewhere private and contacting the duty manager. They don't need to make the whole decision beside a queue, and they shouldn't ask for personal documents on a shared check-in screen.

If two people in a group still plan to enter while another ticket is under review, check those admissions separately. Keep any unresolved cancellation from accidentally blocking the rest of the booking. The door manager needs accurate ticket status and a case contact, not the private explanation behind the request. Tell the support owner what happened so the customer doesn't have to repeat it later.

Keep the case workable when staff change shifts

Before handing a case to another person, record the last verified action and next promised contact. "Refund approved, not yet submitted; finance checking funding; update due tomorrow afternoon" is enough to prevent a false completion message. Add the selected ticket identifiers through the appropriate record. Leave sensitive background in its restricted location rather than repeating it in a shift chat.

If an update deadline arrives before you have an answer, send the update anyway. Say which check is still open and when you'll contact the person again. Silence makes them chase your team for information you had already promised. A brief, accurate message allows you to keep responsibility for the unresolved work without pretending it has finished.

Turn an approved decision into a verified refund

Before initiating payment, confirm the approved amount, selected tickets and destination through your supported process. Check for a previous refund or a pending payment dispute. A refund approval in an email doesn't prove that money has been submitted, and a completed payment action doesn't automatically prove that the right admissions changed status.

Loopyah's ticketing solution includes a configurable buyer refund window. That can handle eligible ordinary requests through the available process. Your team still owns the compassionate decision outside those terms, including which tickets qualify and the amount approved. Don't describe the refund setting as a system that evaluates illness or bereavement.

The current Loopyah organiser refund instructions describe finding the order, selecting the ticket to refund and using a payment option to issue it. They also state that issuing a refund requires payment by the organiser. Verify the funding and fee treatment for your actual booking before committing to the final amount or telling the buyer it has been sent.

For a general payment example, Stripe's refund documentation explains that refunds return to the original payment method and can have pending or failed outcomes. A closed or replaced card needs the provider's handling, rather than an improvised second payment. Check the actual provider and payment method used for your order, and keep a failed refund assigned until the permitted next step is complete.

Use different internal statuses for approved, submitted and resolved. The exact labels can follow your existing system, but staff need to know what each means. If funding is missing or a provider reports failure, don't mark the case finished. Tell the customer what you can verify and when you'll update them while finance resolves the problem.

Reconcile the money and the remaining admissions

Return to the fictional four-ticket order. The original ticket total is $320. Refunding two $80 tickets returns $160 and leaves $160 of ticket receipts associated with the two remaining admissions. Separately confirm any tax or order-level charge, rather than assuming an equal split is always the correct legal or system treatment.

If the event had 100 valid admissions before this action, cancelling these two leaves 98. That only means two places may become available if the ticketing and capacity setup permits them to be sold again. Check inventory before reopening sales. Don't assume a monetary refund alone restores stock or that another buyer will take the released places.

Suppose both places later sell at $80 each. Those new sales bring in another $160 in ticket receipts. They don't remove the need to fund the original $160 refund when it is due, and they don't reverse provider costs or support time. These are fictional cash movements, not an estimate of how often refunded tickets resell.

For a simple planning test, suppose six approved tickets at $80 require $480, and additional unrecovered payment costs are $18. Allow $498 before considering tax or other event costs. If handling the cases takes two staff hours costed at $30 per hour including overhead, allow a further $60 for that work, making $558 across refunds, payment costs and staff time. Use actual costs to plan your allowance, not these illustrative amounts as a benchmark.

A cash allowance helps staff make decisions that the business can carry out. It mustn't become a reason to reject a refund that is legally or contractually owed. If you reach the limit for discretionary help, escalate the next request through the agreed route and review funding. Don't let different agents quietly invent different rules as the event gets closer.

Prepare replies your team can adapt without sounding rehearsed

A useful template removes uncertainty about the action. It shouldn't force every customer into the same emotional script. Have staff read the message, remove questions already answered and check that the reply's tense matches the payment status. "We've refunded you" is wrong if the manager has only approved the request.

For approval before payment submission, try: "I'm sorry you're dealing with this. We've approved a refund of $160 for tickets A and B. Tickets C and D will remain valid. Our payment team will submit the refund through the approved payment route and I'll confirm when that's done. You don't need to send us any further information for this decision."

Once submission is verified, send a separate factual update. Confirm the submitted amount, date, reference where available and the provider's verified expected timeframe. Explain what the person should do if the money doesn't arrive, using one contact route. Don't guarantee an arrival date you can't control or ask them to start a new case from the beginning.

When more information is genuinely needed, explain the missing booking fact. "I have the order reference, but I can't tell which of the three tickets you want us to review. Could you confirm the ticket holder's name through this secure support route?" That is a much narrower request than asking the customer to explain their illness again.

If you cannot approve the requested exception

Have the right person review a refusal before sending it, especially when the case involves serious illness or a death. Recheck applicable rights, the booking terms, your exception criteria and the facts already provided. If the person has identified a service failure or another entitlement, route that for assessment rather than treating it as an unsuccessful hardship appeal.

State the decision and the relevant reason without lecturing the person about your costs. "Our manager has reviewed your request against the exceptional-circumstances policy. We can't approve the cash refund requested for these tickets. We can offer this transfer option, if it would help. If we've misunderstood which tickets are affected, reply here and we'll review that information." Replace the general reason with an accurate, specific explanation where appropriate.

Don't offer a transfer that is unavailable or unsuitable merely to make the refusal sound warmer. If no alternative exists, say so plainly and give the review route you can actually provide. A person should be able to challenge an error privately, without being pushed toward a public complaint or asked to produce more sensitive material without a defined purpose.

Remove sales language from the close. This isn't the time for an upgrade offer, a testimonial request or a cheerful invitation to post about the experience. Keep any required operational notice factual. Where your systems allow it, review event reminders and promotional messages linked to the affected booking so the person doesn't receive avoidable, insensitive follow-ups.

Rehearse the process before the next on-sale

Take a fictional case through the process with the people who will answer it. Use an order with more than one ticket, an absent approver and a payment that remains pending. Ask someone who didn't write the policy to explain what they would do. Their questions will show you where your instructions still depend on unwritten knowledge.

Test a request from a representative as well. Can the team receive it without disclosing the order to an unverified person? Do they know who checks authority if the payer has died? Can they separate that question from whether a compassionate refund is approved? Fix the handoff before someone has to learn it while speaking to a bereaved family member.

After the event, review a small sample of approvals and refusals using appropriately limited records. Look for inconsistent decisions, unnecessary document requests and cases left pending after an approval. Check whether published terms, staff authority and available funds matched what happened. Review sensitive records only with the people authorised to see them.

Keep the commercial review grounded in actual costs and outcomes. Count refunds, unresolved payments and support time separately, with clear definitions. Don't claim that a kind response caused future loyalty or increased ticket sales unless you have evidence for that claim. You can decide that treating customers fairly is part of how your business operates without inventing a financial return for every case.

Before the next tickets go on sale, give your support lead one completed example and ask them to handle it using the written instructions alone. They should be able to find the affected ticket, identify who decides, request only necessary information and confirm what happens to the payment. If they still need to ask the founder what "be compassionate" means, make the missing decision now.