Picture the week before a kirtan evening or a weekend retreat. One person is emailing about parking near the venue. Another is asking whether the sunrise yoga session is suitable for a beginner. A third can no longer travel and wants their money back. In the days before an event these all arrive at once, often through different doors, and it is easy to lose track of who asked what. BrightStar gathers all of it into one inbox inside your dashboard. Every exchange becomes a thread tied to a specific event and a specific customer, and both sides of the conversation — the attendee's message and your reply — are written into that same thread rather than scattered across a personal email account you would otherwise have to search back through later.
Two kinds of thread
Not every thread needs the same handling, so BrightStar keeps two kinds apart. A message is an ordinary question — about parking, about a workshop, about what to bring to a sound healing session. A refund request is different: it is raised against a specific order, and it carries the tickets and the amount in question along with it. That is what lets you settle a refund from inside the thread itself, instead of leaving the inbox to look up the order somewhere else. Because a busy inbox around an on-sale or a check-in can hold a lot of activity, threads can be filtered by state, by type, or by event, and searched by name, email or the content of a message. The top of the inbox shows what is open, what is unread, what is waiting on a reply from you, and how much of your inbox you have answered — the numbers worth watching when doors are about to open.
Replying with help
Three things sit alongside the reply box when you're answering a thread, and all three are optional — you can always just write your own reply from scratch:
- 1Saved replies, for the answers you give over and over
- 2An AI draft that reads the thread and writes a reply in your voice, drawing on the FAQs, documents and past answers you have given it
- 3A rough note you can hand the draft instead, which it turns into a finished reply
How far the AI goes is your choice
The assistant that can draft your replies does not have to work the same way for every organizer, so there are three settings for it. Off means it never touches a thread, which suits anyone who would rather write every reply themselves. Review means it prepares a suggested reply and holds it there for you to edit and send, so whatever the attendee receives has still passed under a person's eyes before it goes out. Autopilot means it sends the reply on its own, and because that reply left without a person checking it first, it carries a note saying it was automated, so the attendee knows what they're reading. A draft you ask for on demand, separate from these settings, behaves the way Review always does: it appears in the reply box, you can change it, and nothing leaves until you send it.
Settling a refund request
A refund request thread carries two decisions, and either one closes it out. Approving processes the refund through Stripe on your authority, records it against the exact tickets in question, changes their status so they no longer admit anyone at the door, and posts a note into the thread so the record of what happened stays attached to the conversation instead of living somewhere else. Declining posts your reason and closes the request the same way. Either decision notifies the person and takes the thread off your open list. What makes this screen different from your event's general refund policy is that an approval you make here is not blocked by the refund deadline you set when you built the event. That is deliberate: it is the place for the case that falls outside your own rules — the bereavement, the missed flight, the person who genuinely cannot travel — without you having to rewrite your policy for everyone else buying a ticket.