Requests & contact

Participants and visitors have two ways to reach you, and both land in the same place: the Requests inbox on your event dashboard.

The two channels

• Requests — signed-in participants (anyone with a submission, a pass, or a role on the event) file structured requests from the event site: equipment, audio/video, accessibility, scheduling, or anything else. Each has a category, a subject and a message.
• Contact organizers — a public message form on the event site, open to everyone including visitors with no account, so someone weighing up a registration can ask a question first. These arrive with a Contact badge.

Every new message notifies the event's admins in-app and by email — sent under the event's name, with the sender's address as Reply-To, so answering from your mail client replies to them directly.

Working the inbox

Open Requests in the event sidebar (admins and committee). For each item you can:

• Move it through open → in progress → resolved / declined — status changes notify signed-in requesters in-app.
• Leave a note the requester sees on their request (for anonymous contact messages, reply by email instead — the sender's address is one click away).
• Filter by status to keep the queue tidy.

Participants see their requests' live status under Requests on the event site, and can withdraw a request while it's still open.

Not for platform questions

These inboxes belong to your event. Questions about Congressio itself — plans, billing, bugs — go through the platform contact page, which reaches the Congressio team, never your attendees' organizers. Both pages say so explicitly, so messages rarely land in the wrong place.

Spam protection

The public contact form is protected by invisible bot detection (Vercel BotID) plus rate limits per sender and per event — no CAPTCHA puzzles for your attendees.