Who runs the all-hands, and what a great one looks like
In most companies the all-hands belongs to internal communications or the chief of staff's office, with the people team and an executive assistant close behind. The CEO is the face of it, but the room is someone else's job, and that person is usually juggling the agenda, the speakers, the slides and the link at once.
A great remote all hands meeting has three qualities. It starts on time for everyone, rather than trickling in over five awkward minutes. It feels like the company, not like a generic call that could be anyone's. And it leaves something behind: the deck, the recording, the survey and the next date, all easy to find.
The plain meeting link struggles with all three. People join early to a blank screen and drift off, the start depends on whoever admits people, and resources are pasted into chat where they scroll away. A branded room fixes the front door without changing the meeting your team already knows how to run.
A run of show for a sixty-minute all-hands
Adapt the timings to your company, but keep the shape: a calm arrival, a sharp start, a clear middle and a deliberate close.
- Fifteen minutes before: open the room from the host control panel. Staff land in the branded waiting room, which shows the company logo, the line that leadership will be joining shortly, and a countdown to the start.
- Ten minutes before: the host starts the meeting in the meeting app as usual, with speakers and the producer joined and sound checked.
- Start time: the producer presses Start the room. Every waiting page switches to the live meeting by itself, everyone joined muted, so the CEO opens to a full room instead of a trickle.
- First ten minutes: welcome, the agenda, and one piece of good news. If there is a milestone, this is the moment for applause or confetti.
- Next thirty minutes: business update and team spotlights, with the deck and key links in view on the page rather than lost in chat.
- Fifteen minutes: open questions, moderated by a second host who reads from the meeting's own questions or chat.
- Last five minutes: recognition, the next all-hands date, and where to find the replay and survey.
How the room's features fit an all-hands
The branded waiting room carries the arrival. When several hundred colleagues click the link at once, they all see the same calm message and the same countdown instead of a meeting that has not started. Add-to-calendar on the lobby helps people who open the invite early.
Start the room carries the start. Your host starts the meeting in the meeting app first, then presses one button, and every waiting guest moves in together. That single, shared start is the difference between an all-hands that opens with energy and one that opens with people asking whether they are in the right place.
Live effects carry the moments. Keep them for real milestones: a customer win, a launch, a work anniversary, a new hire class. Keys 1 to 5 fire confetti, sparkles, rockets, applause or sounds on every in-room screen at the same time. Used once or twice, they make a remote company feel like it is in one place. Used constantly, they become noise.
Guest capture becomes attendance. Staff enter a first name and email at the door, or arrive already signed in, and every arrival is tagged with the event. On a Generic Room you export the list as a CSV and the live attendee list shows who is in while you present; on a Branded Room arrivals can also go to your CRM or email tool with tags. Single sign-on for staff is available through our sales team.
The featured offers rail, on a Branded Room, works as a resources rail for internal events: the benefits form, the survey, the strategy page or the open roles open in a slide-over beside the meeting, so nobody leaves the call to find them. Follow-up funnels then send everyone the replay and the survey after the meeting closes.
Pitfalls to avoid
Most all-hands problems are planning problems, and they are predictable.
- Forgetting to start the meeting in the meeting app before pressing Start the room. Guests will see that the meeting has not started; start it there first, every time.
- Leaving the meeting platform's own waiting room switched on. Your branded lobby already does the waiting, and with both on, staff wait twice and someone has to admit hundreds of people by hand.
- Underestimating headcount. Check your licence's participant limit against your full company list, not last quarter's attendance.
- Firing effects during serious news. Restructures, departures and difficult updates deserve a quiet room.
- Pasting resources into chat. Put them on the page where they stay visible for the whole hour.
- Skipping the dry run. Test the room on a second device, and on a phone, the day before.
Honest limits for large internal meetings
Your meeting licence is the capacity cap. Everyone in the room counts toward your meeting plan's participant limit, and the room warns you as you approach it, from the Generic Room up. If your company is larger than your licence, upgrade with your meeting provider or plan an overflow livestream for the extra audience.
Effects are not in the recording. They play over the meeting on the room page, so the meeting platform's own recording does not include them. If you want effects in the replay, screen-record the room page.
Desktop-app joiners miss the page. Staff who open the regular meeting link in their desktop app will be in the meeting but will not see the lobby, the resources or the effects. Send the room link in the invite, not the raw meeting link.
Rolling it out across the company
Start with a single all-hands on a free 30-day trial, no card needed, to prove the flow with your own team; effects and the attendee list come with the Generic Room and up. When it works, move to a Branded Room so the page carries your full brand, your own domain or subdomain, CRM hookups and the resources rail. If internal comms runs many recurring events, or IT needs single sign-on and multiple rooms under one account, talk to sales; multiple rooms, single sign-on and white-label are scoped and quoted around your calendar.