Corporate Town Hall Live Streaming and Webcasting
The example scenario
This page describes an example use case: an illustrative scenario written to show how a team could set up multistreaming. It is not a customer story, and it does not describe a real organization or real results.
A professional services firm holds a quarterly all-hands meeting and a monthly client webinar. The all-hands needs to reach staff in several offices, while the webinar is also shared publicly. The communications team wants one production setup, a scheduled start time, and a recording that can be shared afterwards.
What this setup needs
A single stream from the meeting room encoder is relayed to the platforms the team uses, such as YouTube and LinkedIn Live, and to any custom RTMP endpoint an internal video system provides.
Set the date and time ahead of time, and schedule pre-recorded segments or a countdown so the broadcast starts on time.
Cloud recording archives the event so it can be shared as on-demand video for people in other time zones.
Producers, moderators and the communications lead can each have a seat, and Business adds white-label options and a custom CNAME for a branded experience.
How the setup works
Add the public platforms and any internal RTMP or SRT endpoint. LinkedIn Live access is subject to LinkedIn's own eligibility requirements; see how LinkedIn Live stream keys work and custom RTMP explained for internal endpoints.
Send one RTMP or SRT stream from OBS Studio, vMix, Wirecast or a hardware encoder to the nearest edge location.
Schedule the event, rehearse with a short test, and go live. Share the recording after the event.
Town hall webcasting: what it involves
A town hall (also called an all-hands, a CEO town hall or a company meeting) is a meeting where leaders update the whole organization and take questions. Webcasting it means broadcasting it live over the internet, often to a mix of people in the room, in other offices and at home, which is why it is also called a virtual or hybrid town hall. Most town halls need the same few things: a production (cameras, microphones and slides), an encoder, a way to deliver the stream, a channel for questions, and a recording for people who missed it.
| What a town hall needs | How this example sets it up |
|---|---|
| Reach staff where they watch | One RTMP or SRT stream from the meeting-room encoder is relayed to LinkedIn Live, YouTube and any internal RTMP or SRT endpoint at the same time. Custom RTMP and SRT destinations are supported on every plan. |
| A viewing page you control | Event hosting publishes the town hall on a white-label event landing page with an embeddable player and CDN edge delivery. White-label options with a custom CNAME are on Business. |
| Playback on any device | HLS live streaming plays on iOS, Android and the web, and adaptive bitrate delivery switches quality from 1080p down to 360p to match each viewer’s connection for events you host. |
| Questions from the audience | Moderated in-player chat rooms on the event page, and unified multichat to read YouTube, Facebook and other platform chat in one window. |
| A start time everyone can plan for | Scheduling with exact start dates, recurrences and countdowns, plus pre-recorded MP4 segments played as part of the broadcast. |
| A recording for other time zones | Cloud DVR archiving of the full broadcast for download and republishing: 5 hours on Creator, 20 on Professional and 100 on Business. Starter does not include cloud recording. |
| Confidence while you are live | Real-time bitrate, audio level and network jitter monitoring with alerts, and post-stream reports covering viewer retention, reach and uptime. |
Running live Q&A
Questions are what make a town hall different from a broadcast, so plan them as carefully as the slides.
- Pick one place for questions. On your own event page that is the moderated in-player chat. If you also stream to public platforms, unified multichat lets one moderator read every platform’s chat in a single window.
- Give the moderator a clear job. They collect and group questions, remove duplicates and pass the best ones to the host.
- Collect questions in advance through your usual internal channels, so the session starts with good ones.
- Read each question aloud before answering. Viewers on different platforms see the stream at slightly different times, and not everyone can see every chat.
Our features page does not list a separate Q&A, polling or voting tool, so in this example questions come in through chat.
Private and secure town halls: what to check
Many town halls include information that should stay inside the company. Decide who may watch before you choose destinations.
- Public platforms are public. A stream on a public YouTube channel or LinkedIn Page can be seen by anyone the platform shows it to, so use each platform’s own privacy settings and keep confidential material off public destinations.
- Use an internal destination for staff-only content. If your organization has a video system or CDN that controls who can watch, add it as a custom RTMP or SRT destination; see custom RTMP explained.
- Encrypt the stream on its way in. RTMPS adds TLS encryption to RTMP, and SRT has built-in AES encryption with an optional passphrase. See RTMP vs SRT.
- Protect the stream keys. Anyone with a key can usually stream to that destination; see what is a stream key.
Our features and pricing pages do not list viewer sign-in, single sign-on (SSO) or password-protected playback. If only employees may watch, deliver the town hall through a system that provides that access control.
Which plan could fit
A regular webinar and an all-hands fit within Professional ($49 per month billed monthly, or $39 per month billed annually): up to 10 channels, 150 streaming hours a month, 20 hours of cloud recording and up to 3 seats. Organizations that need more seats, API access or white-labelling can look at Business ($149 per month billed monthly, or $119 per month billed annually) with up to 10 seats.
Plan details are on the pricing page. Plan limits such as channels, hours and seats are the same ones listed there.
Practical tips
- Decide the audience before you choose destinations. Public platforms are visible to anyone with the link or search access, so use each platform's privacy settings and avoid streaming confidential material to public destinations.
- Run a technical rehearsal with the same network and room setup you will use on the day.
- Keep a human moderator on chat. Unified multichat helps one person watch several platforms at once.
- Publish the recording promptly and add captions where your platform supports them so the content is accessible.
Frequently Asked Questions
Questions this example tends to raise.
More example use cases
An example of how a congregation could send one service stream to every platform its members use, schedule it ahead of time and keep a recording for replays.
See this exampleAn example of how a tournament organizer could ingest a broadcast once and relay it to Twitch, YouTube, Kick and partner endpoints.
See this exampleAn example of how a boutique studio could stream scheduled classes to Facebook, YouTube and TikTok and turn recorded classes into an on-demand channel.
See this exampleLearn more: all features, pricing, how the relay works and how to multistream with OBS Studio.
Ready to stream everywhere?
Bring your live, hosted, and pre-recorded streams into one platform.