For whoever is running the session
Nobody joins a session from a calendar paste. The page has seconds to make attendance look worthwhile: promise, agenda, speakers and joining steps in the right order, with sample wording for each part.
What the attendee can do after the session that they cannot do before. One sentence, above everything else, and no question-mark titles doing the work the sentence should.
Date and start with the zone attached: Thursday 6 March, 15:00 CET. Add one line on whether a recording exists, because that quietly decides a dozen registrations.
Three to five short lines, each an outcome or a topic rather than a paragraph. Readers scan for the twenty minutes that justify their hour.
Name, what they do now, and one proof line. A bio written for a conference brochure does not get read on a phone at a desk.
What signing up gets them, with the capacity cap working in the background. Each registrant receives their own private join link when they register.
One line on what happens after registering, one on what the room needs: browser, headphones, camera optional. That is the whole door.
A virtual event page wins when someone registers, turns up, and is not confused at the door, which is a browser tab. Design matters, but every element serves those three jobs, in that order, and nothing earns its place otherwise.
The samples below are original wording for each part of a page that works. Borrow the sequence as readily as the sentences.
A fictional session about pricing pages. Swap the subject, keep the moves.
By the end of this hour you will have a pricing page drafted, tested on three real customers, and ready to ship.
15:05 — What our own pricing page got wrong, and the numbers that showed it.
Anna Lindqvist has priced two marketplaces and sunk one. She is here to talk about the third.
Use the link in your confirmation email; it is yours alone. No downloads: the session runs in any browser, with headphones recommended if the office is loud.
You will get one reminder the day before and one on the hour. If you registered, you are set; the link finds you.
How it works
Registration is the core of the product: real sign-ups by name and email, capacity tiers, and a secure per-attendee join link wired in from the first publish.
Write the outcome sentence first, then break the hour into rows. The AI drafter can propose lines, but edit them until they describe what you will actually cover.
Choose the number the session can genuinely handle. Reminder emails go out to the registered list without another tool involved.
Send the page wherever your audience already gathers. Each registration counts itself against capacity, and every attendee gets their own route in.
Questions
Rhetorical questions that answer nothing, adjectives standing in for outcomes, and promises the hour cannot keep. The strongest shape is: by the end, you will X. Write X first, then build the rest of the page around it.
Two lines, roughly twenty-five to thirty-five words. Their current role and one concrete credential. Anything longer belongs on their own site; the agenda is what is being judged, and a wall of text slows the scroll towards registering.
They still help. Say which link to use, what the room needs, and when the door opens. Those three lines reduce the can't-get-in panic at the start of the session to almost nothing, and let you begin on time.
State it as a fact about the session, not scarcity: seats are capped at the number we can answer questions for. An honest cap also makes the private join link and the reminders feel like the service they are.
Each event gets its own page, its own registration list and its own join links, so a monthly session means one page per date. The wording carries over easily; the attendee lists and reminders stay separate and clean.
Get Started
Write the promise, the agenda and the joining steps as plainly as the session will run. Set the page once, share the link, and let registration and reminders do the rest.
