💬 Surveys, chat rooms & moderation

Ask attendees what they think, open chat rooms, and keep the community civil.

📝 Surveys

📝 Surveys in the console creates the single-question polls attendees answer at /{event}/surveys. The page states the constraint up front: "one response each".

Open + New survey question (already open when you have none).
Type the Question.
Put the answer options in the box, one option per line.
Press Create survey. It's live and open immediately.

Each survey then shows its results as bars with counts and percentages, plus a total response count, and a pill you click to toggle ● open / ○ closed. Closed surveys stop accepting answers but keep showing results to attendees.

⚠️ Heads up

Attendees see the running results the moment they answer, and they cannot change their answer. So one question, unambiguous options, and options that genuinely cover the space — there's no "other" unless you add one, and no free text.

💡 Tip

The pre/post pattern. Before the event, ask one or two questions that shape it — "which workshop would you attend?", "first time at this conference?" — and promote them in a drip email. Afterwards, close those and open a short post-event set — "would you come back?", "which day worked better?" — promoted in your thank-you campaign, segmented to checked-in only so you hear from people who actually attended. Two rounds of three questions beats one round of ten.

Surveys are separate from session ratings (stars and comments on each session page, reported in 📊 Reports) and from live polls (launched from the sessions console and shown inside a session). Three different tools; don't duplicate a question across them.

💬 Chat rooms

Group rooms are created from the event hub, under 💬 Chat rooms (3). Type a name — the placeholder suggests "☕ Hallway Lounge" — and press Create room.

Rooms appear under Join a room on the attendees' chats page, each prefixed with #. Any signed-in attendee can join; attendees cannot create rooms themselves, so the set you make is the set that exists.

💡 Tip

Three or four well-named rooms get used; a dozen sit empty and make the event look deserted. A hallway/lounge room, one per track at a multi-track event, and a first-timers' room is usually the right shape. Announce them — an unmentioned room stays empty.

📋 The community board

The board at /{event}/community needs no setup — attendees post discussion topics and meet-ups, and reply to each other. Meet-ups are pinned above topics with their time and location.

There's no moderation queue and no delete button in the console, so oversight is active rather than gatekeeping: read the board during the event. It's also the best informal signal you get — the questions people ask there tell you what your communications missed.

ℹ️ Note

Meet-ups are attendee-run and visible to everyone, which is the point — but it does mean a dinner booking for six can attract sixty. Worth a line in your know-before-you-go email about being realistic with capacity.

🚫 Blocking someone

The moderation lever is on the public 👋 People page: signed in as an organizer, each person's row carries a red block / unblock control that attendees don't see.

Blocking is decisive. A blocked participant:

Is removed from the People directory	Attendees no longer see them or can message them from there.
Is excluded from AI match suggestions	They stop being proposed to anyone.
Is excluded from meeting requests	They can't be picked in the Meetings form.
Is removed from the speakers directory	Their profile page returns not found, even if they're assigned to sessions.
Is locked out of participant pages	Opening their portal or other participant-only pages bounces them back to the event page.

Organizers still see blocked people in the directory, dimmed, so you can find them and unblock. Blocking is reversible and leaves their history intact.

⚠️ Heads up

This is a heavy tool — effectively ejecting someone from the event's social layer, and it does not refund their ticket or stop them entering the venue. Use it for harassment and abuse, decide it with another organizer where you can, and follow up with the person by email so they know what happened and why. For a speaker, remember it also removes their public profile.

🤝 What runs itself

These need no configuration, but knowing they're there helps you promote them:

Direct messages between attendees, and 👋 Say Hi from the directory.
⚡ Speed networking — a matching queue at /{event}/networking. It only works when two people are waiting at once, so point people at it during breaks and it comes alive; leave it unmentioned and it stays empty.
🤝 Meetings — attendees proposing a specific time to each other.
✨ AI match suggestions on the People page — which work far better when profiles are filled in, so nudge people to complete theirs in a drip email.

The attendee-side detail is in 🤝 Networking & messaging and 💬 Community board & surveys — both reasonable things to link from a know-before-you-go email.