For the person who has to fill the room
An all-hands posted as a bare meeting link leaves you guessing who intends to come. Put it on a page: a seat cap for the room, a second person minding the list, and reminders that run themselves.
The usual way an all-hands gets announced is a message in the general channel with a meeting address at the end of it. People react, someone says looking forward to it, and on the day nobody knows whether forty or three hundred intend to come. For a town hall held in a real room with a real capacity, that guess is the problem you actually have to solve.
A registration page turns the guess into a list. You publish one page for one session, staff register with a name and email, the places stop when you said they would, and each person gets a private link of their own. The address you advertise is the page, never the meeting.
Cap the registrations to what the room and the platform can hold. The page can show how many places are left, and switches to saying it is full — which is the honest way to stop a hundred extra people turning up.
Each chapter gets its own duration and a line on what it covers, so the plan reads as ninety minutes with a shape rather than an open-ended meeting nobody wants to sit through.
Speaker sections carry a name, title, photo and biography. For an all-hands this is the line that tells staff whether leadership is presenting or someone is reading slides on their behalf.
The zone appears as a label next to the start time. Distributed teams stop arguing about it when the page says which one you mean.
The list is a genuine improvement on a chat reaction, but it is worth knowing its edges before you plan the room.
An all-hands is too big a thing for one pair of hands on the day, and you do not have to hand someone your login to solve it. Bring a colleague into the event at their own access level so they can watch registrations, take the questions that arrive by mail and handle the awkward minute when the room fills. Two people reading the same list is the difference between a hosted event and a scramble.
The same logic covers the invitation itself. Until you publish, the page is invisible to anyone with the link, so you can build it quietly, let a second pair of eyes read the wording, and only then post it in the channel. Nothing half-finished reaches a colleague.
Reminders do their work in the background: emails at twenty-four hours, an hour and fifteen minutes before the start, to everyone registered unless you switch them off. There is no WhatsApp nudge sent to staff on your behalf, and no sync into anyone's calendar — the confirmation email carries a calendar file and a Google Calendar link, and that is the extent of it.
Once the session closes, export the list and send one follow-up to a chosen segment of the registrants with the deck or the recording link you are supplying yourself. For the departments you expected and did not see, the honest route is the manager who owns that team, not a message the product cannot send to people who never registered.
How it works
The date, the start time with its zone, how long the session runs, and the capacity of the room you are using. Everything else on the page is written around those four facts.
Chapters with durations, then a short biography for each person presenting. Ask Jitabi for the first draft from a paragraph describing the all-hands, or fill it in the web app.
Set the limit to the room, switch on a waitlist if you want overflow held politely, and bring a co-host into the event at their own access level so the list has two watchers.
Post the page link in the channel — not a meeting address. Before the session, export the list for the room; afterwards, mark attendance and send the follow-up to the registrant segment.
Questions
The page lists everyone who did register, with statuses you can mark, and exports as a file. The names missing from it are only visible by comparing that export against your own staff list, which stays your side of the work.
Registered attendees get emailed reminders before the session. Staff who never opened the page are outside that, so the reminder cannot reach them. A channel post plus a manager's nudge is the realistic combination.
That is the design. The public page never shows the meeting address; each registrant gets their own access link in their confirmation email. Add the page password too if the town hall is meant to stay closed to a named group.
No. The list updates as replies come in, and attendance reflects what you or your co-host mark. There is no running dashboard of people present in the meeting, and no read on who watched a recording later.
It cannot. A webinar page holds one live session, so each quarter needs its own page. The agenda and speaker sections copy across, and the previous registrant list is the group you send the new page to first.
Get Started
Put the all-hands on a page with a cap, a co-host and an agenda that ends. Then you know how many chairs to set before anyone walks in.
