For the first invitation you want to get right
Title, promise, agenda, speaker, seat, button. A short guide to the build order for an invitation page, from naming the session to sending one link that keeps the list.
Most webinar invitations fail at the first step, and the first step is not design. It is deciding what the session is, in words a stranger can picture. Once that is settled, the rest is a sequence: give the page something to prove, set how many people you can genuinely take, then hand out the link and let the register fill. Skip a stage and you end up with a page that looks finished while the hard parts are still undecided.
The tool underneath is a set of tabs whose answers become sections of the guest page, so each answer has to be written the way you would want it read. That is a useful constraint while learning the order: you cannot hide a weak promise behind a layout, because there is no layout to hide it behind.
Written as a guest sees them, with the job each one has to do.
Reading a Church Archive: Cataloguing 400 Photographs in Six Weeks
For anyone holding photographs older than they can account for — a society's attic, a family box, a parish cupboard.
You will leave with a filing order you can start on the same evening, and a short list of things to stop doing.
Thirty places. The page shows how many are left, and says so plainly when it is full.
The invitation is only worth sending once the page can keep the record. Publish it, then paste the address where your audience already reads your messages: an email, a chat, a slide at the end of a talk, a QR on a printed notice. One page carries one date, so a repeat evening is a second invitation with its own link and its own list.
Afterwards the list tells you more than the headline number. Page views sit beside the count of who registered, and people land as registered, attended, waitlisted, cancelled or a no-show, all of which comes out as CSV or PDF when somebody asks for the sheet. Emails at twenty-four hours, one hour and fifteen minutes go out on their own unless you switch them off. Nobody reconciles a second spreadsheet at midnight, which is the entire reason to make the invitation on the page rather than beside it.
How it works
A title that says the subject, the date and start, and the choice between webinar and workshop. If this stage is vague, no later stage rescues it.
A short description that names who it is for and what they leave with, then agenda chapters with durations and takeaways. Add the speaker: name, title, photograph, honest biography.
Cap sign-ups at the size you can host, keep name and email, and add only the questions you will use. Decide the waitlist now rather than when the page is full.
Paste your join URL, publish, and share the address. Each registrant gets a private link of their own, plus the calendar file and a Google Calendar link in the confirmation email.
Questions
A title, a date and time with the zone labelled, a description of what happens, the form, a cap you can honour, and your own join link. An agenda and a speaker line make that minimum considerably more persuasive, but those six items are the door.
After, or at the same time. The page is the invitation: whatever you type into the tabs is what guests read. Writing a separate blurb first gives you two versions of the same promise, and they drift apart almost immediately.
No. They open the link, give a name and an email, answer whatever else you asked, and they are on the list. Nothing to install and no password to invent in the middle of deciding whether to come.
No. You publish, copy the address and send it from your own email, your own chats or your own slide. The audience stays yours, which also means nothing is posted anywhere without you deciding to do it.
Not the page. It is committing to a scope: one session, one date, chapters you can genuinely deliver in the time. A title that oversells produces registrations that produce silence on the day, and no reminder can repair that.
Get Started
Name the session, prove what happens, set the room, then send the address. Fill those four stages in order and the register starts filling itself.
