For the two weeks before you talk
The count-down to a session is not a ticking number on the page. It is the confirmation email with the date in it, the calendar file that reaches a diary, and the emails that follow as the day approaches.
A webinar register rarely empties because people change their minds. It empties because a date stops being visible. Someone signs up on a Tuesday evening, their diary holds the intention for about nine days, and by the time the session arrives the reservation has become one more thing that was meant to happen. Whatever keeps the date in front of a guest between registering and joining is doing more for the room than the invitation did.
That is the honest version of a countdown question. Counting down is not decoration; it is the sequence of reminders a page sets in motion the moment a name lands on the register.
If you came here looking for a ticking timer in the header of the registration page, here is the straight answer: a webinar page does not carry one. What it carries instead is the information a guest checks against a diary: the title, the date, the start time with its zone shown as a label beside it, the agenda chapters with their durations, the speaker, the number of places and the form. Those sections decide whether the person signs up; the counting down happens in everything that follows.
A timer, after all, is only ever as convincing as the date underneath it. The reliable version of urgency is exactness: a start time that is real, a stated end, and a page that says plainly whether there are places left. The cap you set is enforced on the page, which shows places remaining and turns to full once your number is reached.
A confirmation email arrives with the date in it, a private access link of their own, an .ics calendar file attached and a Google Calendar link. That is the guest's diary entry, and it is the only calendar arrangement the product makes.
Nothing counts down on the page, and that gap is where plans go missing. What holds the date is the calendar entry they made plus your own messages: an email, a note in a chat, a line at the end of a talk.
The first automatic email to everyone registered. The session becomes a thing happening to them rather than a thing they once agreed to.
Two more automatic sends, the last landing as you open. All three go out on their own, and you can switch them off.
The follow-up you send to a segment of the list, with the links you supply: replay, slides, resources, feedback, your own certificate.
It is not the absence of a ticking number. It is the belief that one graphic can do the work of a sequence. A countdown in the header adds motion to a page and changes nothing about the person who registered and then never opened the confirmation email. The version that fills rooms treats the sign-up as the start of the arrangement: the diary entry arrives immediately, the reminders follow, the date gets repeated in the host's own words.
A second mistake runs the other way: borrowed urgency. A counter is a promise about a fixed date and a finite room, so the page should only say what is genuinely fixed. The date is one, the cap is yours, and the counting down is handled by the emails.
How it works
The start time and its zone label, the agenda chapters with durations, the speaker and the cap. A second evening is a second page with its own register.
Each registrant gets their own access link, the calendar file and a Google Calendar link in that email, which is the arrangement the product makes.
Twenty-four hours, one hour and fifteen minutes before the start, to everyone still on the list, unless you switch them off.
A line in your newsletter, a message to a segment of the register, a closing slide. Repeat the date and the zone, and the run-up stops depending on memory.
Questions
No. The page shows the date, the start with its zone labelled, the agenda and the places left. The counting down is done by the confirmation email with its calendar file and by the timed emails before the start.
It is not synced. The confirmation email carries an .ics file and a Google Calendar link, and the guest chooses to add the date. That is the whole of the calendar feature.
Not with a widget, and not with invented pressure. What is genuinely limited is the room, so the honest line is the cap you set: places left while it lasts, then the waitlist takes names.
No. The timed emails before the session go to registered people by email. WhatsApp is used at the other end, to notify the host when someone registers.
Build a page for each date. One link means one session, so two dates need two addresses, two registers and their own confirmations and reminders for each list.
Get Started
One page, one date, the diary entry arriving in the confirmation email, then the timed emails running themselves. That sequence is the countdown, and the register you exported is what it was for.
