For both sides of the form
Two paths, one handshake. A visitor fills in their name and answers your questions; a row appears on your dashboard; they get their own way in. Here is the whole exchange, in order, from both sides.
Your invitation — email, chat, post — carries one link, and it opens the registration page. The visitor sees what the session is: the title, the description, the agenda built in chapters with times and takeaways, the speaker with their name and photograph, and the start time with its zone label beside it. They are asked for two things that always appear, name and email, plus whatever custom questions you chose to add.
They tap register, and the useful part arrives by email: a confirmation with the time stated once more, an .ics file and a Google Calendar link for whoever wants the date in their calendar, and their own private access link for the day. Reminders then come to them at 24 hours, 1 hour and 15 minutes before the start, unless you, the host, switched them off.
At the moment the guest taps register, your attendee list gains a line. Name, email, their answers to your questions, status: registered. The list updates as replies come in, and WhatsApp nudges you when a new registration lands, so you know without refreshing. Page views and sign-up rate are counted on the same dashboard, which is how you can tell a traffic problem from a wording problem.
If you capped the room, the count behind each row is what enforces it: when the last place goes, the page says so, and further visitors meet the waitlist if you turned one on. Nothing about this needs your attention in the moment — the list is doing the bookkeeping while you prepare the session.
One row per person, with custom answers attached. There is no approval step; a completed form is a booked seat, and the seat limit is the only full stop.
You pasted your Zoom, Meet, Teams or YouTube link into your dashboard; it is never printed on the public page. Each registrant receives a personal access link instead.
You open your meeting tool as you always do. Registrants follow their own links; you mark attended and no-show names on the list as you go.
Export it as CSV or PDF, and send the registered segment the follow-up links you supply: replay, slides, resources, feedback, or a certificate you made elsewhere.
How it works
Create the webinar page in the web app: description, chapters, speaker, start time with its zone, custom questions, seat limit, the waitlist switch, and your meeting link for later.
Name and email, plus your questions if you added them. No account to create on their side, nothing to install, no meeting password to be handed out.
They receive the confirmation with the calendar file and their private access link; you receive a new row and a WhatsApp nudge that someone signed up.
Reminders arrive on their own schedule; you run the session from your own platform; afterwards the list shows who attended, exports as CSV or PDF, and feeds the follow-up email.
Questions
No. The form on your public page asks for a name, an email, and whatever custom questions you set. The meeting platform itself only matters on the day, when they follow their access link to whatever you pasted.
The seat limit holds. If the last place goes, the page says so, and with the waitlist on the form that appears collects details instead, telling them a spot opening means an email.
Attendance is marked by you on the list: statuses cover registered, attended, waitlisted, cancelled and no-show. We never verify attendance through the meeting platform, because we are not connected to it.
Each person registers separately and receives a link that is theirs alone, which is the design that keeps the meeting address private. What one does with their link after that is beyond any product's reach, so the seat limit is what you trust.
Get Started
The guest path and the host path meet at a single form. Build the page, set the room, share the link, and let the list keep score for both of you. Start free whenever you are ready.
