For the session where the guest list matters
A quarterly update cannot be a link anyone can forward. Gate the page with a password, cap the seats, hold a waitlist as a courtesy, and export the list as the record when it ends.
Investor updates are unusual among webinars because the risk is not a half-empty room. It is the room having someone in it who was not meant to be there. An update sent as a normal meeting link travels by forwarding, lands in a group, and stops being a conversation with shareholders the moment it does.
So the shape of the page matters more than its design. You publish one page for one session, put a password on it so the address alone opens nothing, and let the registration flow do the rest. Every attendee who gets in receives their own access link by email, which means the way into the meeting is not one shared string circulating on its own.
The gate is optional and yours to set. Write the word into the invitation you send by name, so the page reads as locked to anyone who arrives without it.
Limit the places to what you can answer questions from. Once they are gone the page says so, and a waitlist holds further names with the plain message that an email will come if a spot opens.
Chapters and durations: the numbers, the reading on them, then the discussion. Written as chapters, the shape of the hour is on the record before anyone attends.
A speaker section takes a name, a title, a photo and a short biography. For a shareholders' session that line carries more weight than usual.
A full page reads worse than a page that offers a way to still be counted, and the waitlist is the courteous version.
After the update, the registrant list exports as CSV or PDF: names, emails, the statuses you marked, and any custom field you asked for — a fund name, a region, whether someone is a first-time attendee. That file is the practical output of the session, and the thing you hand over when someone asks who was invited.
One clarification is worth stating plainly, because this is where invitations get careless. There is no approval step on registrations; the controls are the password, the cap and your own list. Attendance reflects what you mark, not a verified headcount, and the record you keep for anything formal is your own document. The export supports that work; it does not replace it.
The same honesty applies to the rest of the evening. There is no question queue, no poll, no recording made for you and no transcript, so if you want questions collected in advance, ask for them as a field on the form and answer the recurring ones in the follow-up. Reminders go to registrants by email at twenty-four hours, an hour and fifteen minutes before the start.
Follow-up is where most of the value lands anyway. Broadcast to the segment of names who registered with the material you are supplying — the deck, the recording, the one-page summary — and mark the discussion points you could not close in the hour for the next update.
How it works
Chapters, durations, and one line each on what is covered. On a page like this the running order is the reassurance, so make it specific enough to be checked afterwards.
Company or fund, region, or the question someone wants answered. Each arrives as a column on your list and a line in the file you export.
Limit the places, turn on the waitlist if you want a polite overflow, and gate the page. Send the word in the same note as the link, to the names you chose.
Send the page address — never the meeting address — to your shareholder list. When it ends, mark who came and export the names and statuses as CSV or PDF for the record you keep.
Questions
The meeting link was never on the page to begin with. Each registrant receives their own access link by email, and the password is a second door in front of the page, so someone with the address alone sees neither.
There is no approval step in the product, so a registration is a registration. What you control is the password on the page, the cap on places and the invitation list you personally send the link to.
It tells them a spot opening means an email. Their name sits on the list marked as waitlisted, so you can see the size of the overflow before deciding whether to run another session.
However you run your own meeting; the invitation page has no question tool, poll or chat. A common approach is to collect the question as a form field beforehand and answer the recurring ones on the page.
You get the list, with statuses you mark yourself, exported as a file. That is a record of registrations and of what you recorded. Anything formal remains your own document rather than something this page certifies.
Get Started
Gate the page, cap the places, hold a waitlist for the rest, and let the export be the list you keep. The meeting address never has to leave the room.
