Let Attendees Refund Themselves

Picture the week before a retreat, or the day before a kirtan you're hosting. Someone writes in because they got sick, someone else because the weekend stopped working for them, and a third person just changed their mind. None of these are disputes — they're the ordinary churn of running events for people whose lives don't always cooperate with a calendar. Answering each one by hand, checking the date, deciding the amount, issuing the refund, is a small tax that adds up across every event you run. Self-serve refunds let you write your policy down once — a percentage and a cutoff — so that any request landing inside it is handled by BrightStar without you touching it. A request that falls outside your stated policy isn't refused and isn't silently ignored either. It becomes a case, waiting for your decision, exactly as if the attendee had emailed you directly.

No. BrightStar doesn't impose a universal refund window across events, because a five-day sound healing evening and a ten-day retreat abroad don't call for the same policy. The percentage and the cutoff are set by you, per event. If you run many events and don't want to configure each one from scratch, you can set an account-level default that applies to any event without its own policy. If you set nothing at all — no per-event policy, no account default — a buyer who asks for a refund is told that you handle refunds directly and is pointed to messaging you.

BrightStar checks a request against your settings in a fixed order. First, whatever you configured for that specific event applies, if anything. If the event has nothing set, BrightStar falls back to the refund defaults in your organizer communication settings. If neither is in place, the request is not processed and no case opens — the buyer is told that you handle refunds directly and can message you. Only one outcome is allowed to happen without you: an instant cash refund that falls cleanly inside an active policy. Anything that would resolve to event credit instead of cash, to no refund at all, or to a date past your cutoff, is routed to you for a human decision rather than processed silently in the background.

A ticket holder requests a refund by choosing which tickets the request covers, and can add a reason for asking. If the request is inside your policy, the refund is processed and the buyer receives a confirmation email — no waiting on you. If it falls outside your policy, the request is sent to you rather than being refused.