Not everyone who lands on your event page has decided to buy yet. Someone reading about a weekend retreat wants to know if it is suitable for a beginner before they commit. Someone looking at a kirtan listing wants to know if there is parking nearby, or whether the venue has stairs, before they buy a ticket for a friend who needs to plan around that. These are real hesitations, not idle curiosity, and if the only way to ask is to hunt down your email address somewhere else, most people will not bother. Every BrightStar event page carries a "Contact the organizer" link, alongside your host profile, so a visitor can ask without searching for you. It is part of every plan, Seva included.
Where the link takes them
The link opens BrightStar's contact page with your event already selected, so the visitor does not have to explain which gathering they mean. The form lives on that page rather than inside the event page itself. A visitor can log in, in which case their name and email are filled in for them, or continue as a guest and type them in. Either way, they write their question and send it to you through BrightStar, never to an address of yours.
Private on both sides
The conversation is private in both directions. The visitor never sees your email address: when you reply, the email they receive comes from your name "via BrightStar", with a "Reply on BrightStar" button that opens the conversation. Replying to that email itself does not reach you, so the conversation always continues on BrightStar. On your side, the notification you receive shows the visitor's name and message with a "Reply in BrightStar" button. For a question asked before buying, the visitor's email address is not shown to you; it appears only when the person is a ticket holder writing about their own order.
Where the question lands
Every question is saved as a conversation in your BrightStar inbox, under Communications in your dashboard, alongside your other attendee conversations. The conversation is saved even if the notification email fails to send, so a question is never lost because an email went astray. That matters because a pre-purchase question is rarely asked only once, and keeping the exchange in one place means the thread and your reply stay together, visible alongside everything else connected to that gathering.
Why a cold question arrives as a request
Someone who has not bought a ticket has no existing conversation with you, so their message arrives as a message request rather than dropping straight into the conversations already waiting on you. That distinction protects your attention: a cold enquiry does not count the same as a message from someone who has already paid and is counting on hearing from you before a gathering starts. A ticket holder who writes about their order is treated differently; their message is linked to that order, so you have the booking in front of you when you answer.
How a visitor reaches you before buying
How a visitor reaches you before buying:
- 1They select "Contact the organizer" on your event page.
- 2BrightStar's contact page opens with your event already selected.
- 3They log in, so their name and email are filled in, or continue as a guest and enter them.
- 4They write their question and send it, without ever seeing your email address.
- 5You are notified, and the question is saved in your BrightStar inbox, ready for your reply.
Protection from spam
An open door also needs a way to keep out what should not come through it. A guest has to pass a quick human check before their message is sent. There are limits on how many messages one sender can send, and on how many any one organizer can receive, in a short time, and very long messages are refused. A message that looks like spam, such as one packed with links, is held quietly for review instead of being delivered to your email, so a genuine question reaches you and a flood of junk does not.