For multi-audience programmes
Nobody can drop into a virtual event by accident. The website has to carry the programme and the promise beforehand, then point every registered guest at the right door when the hour arrives.
A physical venue has an advantage no online event shares: people can find it by turning up. A virtual event depends entirely on its front door, and that door is a page doing two shifts. Before the event it persuades and signs people up. During it, it is the thing a guest reopens when the clock hits the start and they want in.
Most pages only attempt the first shift. The second is what saves the day: the guest who registers on Monday and forgets by Thursday should find everything they need on the same address, without searching their inbox. This is the structure worth building for any programme with an audience spread across more than one zone.
One address, four jobs, no separate documents.
The shape of the time: what opens the session, what follows, when the discussion happens. Short rows, in the order they will actually occur.
Names, roles, and the one fact that makes each person worth hearing. A programme of names alone asks the visitor to guess.
The private link each guest receives is the door; the page says so plainly, so nobody waits on a message that never arrives.
Emails scheduled once at setup, carrying the time in the guest's own terms back to them before the hour.
The practical build is one page rather than a stack of them. My Joyfullday's webinar invite gives the programme, the speaker section, the registration with tracked replies, and the private access links the same home, so the shift from persuading to letting people in never changes the URL.
Where a bigger gathering suits it, put the livestream link on the page so remote guests have their own door, and keep the join instructions short enough that nobody needs to ask. A page that works both before and during is a virtual event's only reliable front desk.
How it works
Open a webinar invite with the programme as its backbone, in the app or by describing the event to Jitabi on WhatsApp.
The programme rows, the speaker notes, the joining instructions, and the time spelled out with its zone, since you cannot know where your guests are reading.
Set the capacity to what your room holds and schedule the reminder emails, so the during-event shift is staffed before the first registration arrives.
Every post, email, and signature points at the same address before the day, and every guest reopens it when it is time to join.
Questions
A single well-built page usually carries the whole thing: programme, speakers, joining details, and sign-ups. A bigger site only earns its cost when there are genuinely parallel sessions with their own lists, and even then each room can start from a page.
Each registered guest receives their own access link, and the page says that is how entry works. Nobody hunts through a chat thread, and the address they already have is the one worth reopening when the session starts.
Give the start time with its zone on the page, in the form, and in every reminder. Say how long it runs. Guests in distant zones make their decision from those two facts, so leaving either out costs you registrations that would otherwise hold.
It keeps working as the record of what happened, which is useful for the next announcement. Most hosts publish a fresh page for each event and reuse the structure rather than the content, and nothing spoils a good page after the hour.
Get Started
Programme, speakers, clear times, and a link for every name. Build the page once and let it work before the event and during it.
