Town Halls

No. Each session picks one of three: stream it here from an RTMPS encoder (OBS, Wirecast or Zoom), with the player on the session's page; keep the video on another platform such as Teams, Meet or your streaming vendor, with a Watch button beside the room; or no video, for a session people are in the room for. Q&A, polls and chat run the same way in all three. Streams broadcast here run on the managed Mux account, or on the company's own Mux account configured under Admin → Integrations. There is no browser-based broadcasting: a stream broadcast here needs an encoder.

Each session has a mode: open (questions go straight to the room), filtered (a keyword screen holds offensive ones for a moderator), or reviewed (every question waits for a moderator). Reviewed is the default whenever the whole company can watch, and the mode can be changed while the session is live. With the tenant's AI moderation on, an AI screen also flags questions for a moderator's attention. Moderators approve, edit then approve, or dismiss held questions from one queue, which also feeds the admin Content Moderation queue; the asker sees their question is waiting and is told if it's dismissed. Moderators can download a session's questions as a CSV.

A stream broadcast here carries live captions while it is on air by default, in the language the host speaks (English, French, German, Italian, Portuguese or Spanish; captions are not translated). The host can turn live captions off for a session that needs low latency: with captions viewers see the host some 20–30 seconds behind, without them about 5. Streams broadcast here also auto-record to on-demand playback by default, and recordings are AI-captioned when auto-transcribe is on. If recording is turned off for a stream, its recording is deleted at the provider so nothing is stored.

Yes, when the session is set that way. Each session's Names on questions setting is one of three: Shown to everyone; Moderators only, where the room sees each question without a name and the session's moderators and the questions export see who asked; or Anonymous, where the question is saved with no asker at all, so nobody — not the room, not the moderators, not the export — can tell who asked. The asker still sees their own questions on the device they asked from, and can withdraw one until it is answered. The setting is fixed once the first question arrives, so nobody's question changes rules after they asked, and an admin can take Anonymous off the schedule form for the whole company.

On the session's page (web and phone) viewers get live chat, upvote-Q&A — anyone can ask, one vote per viewer, so the questions people care about rise to the top — and in-session polls they vote in, all updating live with no page reload. A host can turn chat off for a session, before or during it. While a session is live, a late joiner can tap "Catch me up" for an AI summary of the room — and, when live captions are on, of what was said. Moderators get AI clustering that groups the flood of questions into themes, and an AI recap of the session, kept on its page for anyone who missed it. With the tenant's AI moderation on, an AI screen also flags questions for review.

Every session has a stage wall: a full-screen page for the screen behind the speaker, or a vMix or OBS browser source, showing the question a moderator put on stage in large type, the next questions in the room by votes, and the company's logo. Moderators run it from the host console or the watch page — put a question on stage, pin it so it stays up after it's answered, clear the stage, or pause the wall. Its display link needs no sign-in and works until a moderator makes a new one. A QR code on the wall, the console and a printable sheet opens the session's Q&A on a phone, after the usual sign-in if needed. A session everyone can watch can also take over the Digital Signage break-room screens at the sites the host picks while it is live — playing the stream, or the stage wall when the video is elsewhere — and hand them back to their playlist when it ends; an alert on a screen always comes first. Afterwards, the session's host, moderators and admins see Reach by location: how many of the people it was for joined, by site and by region, with small groups counted together so no one can be picked out.

When the matching options are enabled, a scheduled session is mirrored onto the company Calendar, and the host can open it for registration so anyone finds it under Calendar's Events tab. Calendar reminds the host and anyone registered an hour ahead; a session with an audience set reminds that audience 15 minutes before (a company-wide session does so only when an admin turns that on). The calendar event offers Watch live while it airs and the recording afterwards, and registrants who watch count as Attended on the roster. Going live sends an in-app/push "we're live" notification and drafts a Broadcast for an admin to publish, and the finished recording can auto-post a "Recording available" notice to the Communications feed.

A tenant setting controls who can schedule and host — admins only, or any user; company admins, Town Halls app admins and Town Halls contributors can always schedule. Running a specific session (the host console and stream key, go live, end, edit, cancel, its moderation mode, chat switch and break-room screens switch) is limited to that session's host, its session team, or an admin. Moderating the room (held questions, answer/dismiss, remove chat, polls, the stage wall, AI clustering and recap, the questions export, reach by location) is open to those people plus Town Halls contributors. Each session is open to everyone the app is published to, or only its audience. When a signing key is configured, playback uses signed, short-lived tokens (about 6 hours) so a leaked URL can't be watched from outside your organization; without one, playback is public — the Settings page says which applies.

Town Halls runs one-to-many live sessions — a town hall or training, streamed here or on another platform, with the company joining in the app for live chat, moderated Q&A and polls. Broadcast is targeted text/media announcements (no live video) pushed to specific recipient groups. Live Assist is small-group WebRTC video — a remote expert joins a worker's phone-camera POV to guide a fix — not a company-wide broadcast.