A chat for your online event
The talks are the easy part. What an online event loses against a real one is the corridor — the people standing around afterwards still arguing about what they just watched.
A room per session
One for each talk or track, so the conversation belongs to the thing it is about and does not turn into one enormous scroll.
Open it for the day
Rooms are created and removed from the dashboard or the REST API, so an event that runs for two days does not leave nine empty rooms behind.
Delegates arrive as themselves
Single sign-on from your registration system means the name beside a message is the one on the badge, and nobody types a nickname.
Installing it
One line before the closing body tag
Anywhere that ends up on every page, immediately before the closing </body> tag — a shared template, a layout partial, or whatever your platform calls its footer code box.
Full instructionsQuestions
- Can I have a room for each session?
- Yes, and that is the usual arrangement: the conversation belongs to the talk it is about instead of turning into one enormous scroll nobody can follow.
- What happens to the rooms after the event?
- You remove them from the dashboard or the REST API, so a two-day event does not leave nine empty rooms behind. Most event sites script this from the same schedule that builds the agenda.
- Will delegates have to register again?
- No. Single sign-on from your registration system means the name beside a message is the one on the badge, which also settles the problem of attendees not recognising each other behind nicknames.
- How many attendees can be in a room at once?
- It depends on the plan, and this is the number to size on for an event: a session with four hundred people in it needs a plan that allows four hundred concurrent, not four hundred messages.
Try it on your site for fourteen days.
No card, and nothing to uninstall if you change your mind — it is one line.
Or look at what it does first
The feature pages cover the chat, the support side, moderation and single sign-on.