How to increase webinar attendance: show-up rate is a system.

Show-up rate is a system, not a subject line.

Almost everything written about webinar attendance is a tactic looking for a home: an extra reminder, a bolder countdown, a bonus for the people who turn up. The number moves when the whole path from registration to room is built deliberately, and barely at all when one part of it is decorated.

Define it once

Show-up rate is live attendees divided by registrations for one session. The definition that matters is the numerator: decide now whether an attendee is anyone who joined at all, or anyone who stayed a set number of minutes, and then use the same definition every time. Two definitions produce two trend lines, and you will end up comparing a good session measured strictly against a weak one measured loosely.

Then resist the benchmark. The averages published everywhere blend industries, price points, list warmth, gap lengths and traffic sources that have nothing in common with yours, and importing one gives you a target with false precision. Your own last session is the only comparison that carries information.

Why this number is worth the effort

Registration rate is mostly a function of your topic, your title and where the traffic came from — things that are slow to change. Show-up rate is almost entirely a function of your operations between two fixed points. It is the most fixable number on the webinar report, and it multiplies everything downstream: the same registrations, the same session, the same offer, more people in the room to hear it.

Shorter gap, hotter room.

The gap between registering and attending is where intent decays. Someone who registers three weeks out has to carry an intention across three weeks of everything else in their life. Someone who registers on the morning has to carry it for hours.

That is the whole mechanism, and it produces a trade you cannot escape: a short promotion window gives you a higher show-up rate and usually a smaller room, and a long one gives you the reverse. Neither is correct in general. Which you want depends on whether this session needs volume or reliability, and the only way to know what it costs you is to run it both ways and compare attendees rather than registrations.

Shortening the gap without shortening the window

This is the part most people miss. The window and the gap are not the same thing. You can promote for two weeks and still pull a large part of the room closer to the session by moving promotion weight to the last two days — the last-call sends, the partner who agreed to a second send, the morning-of post. Those registrations arrive with almost no gap to survive.

Which also means the promotion plan and the attendance plan are the same plan. Where the weight sits in the fourteen-day calendar is a decision about show-up rate as much as about registrations.

Tag the cohort, then stop guessing

Record how many days before the session each person registered, then read show-up rate by that cohort. The point is not to confirm what you already believe about early registrants — it is to stop reasoning from belief at all. Once you can see which cohort is thin, the reminder plan has somewhere to aim, and “send everyone another email” stops being the only available move.

Time, day and timezone

Pick a time you can defend for the audience you actually have, then keep it. A session that is always on the same weekday at the same hour becomes a habit; a session at a new time every month is a new decision every month, and new decisions lose to whatever else is already in the calendar.

If a meaningful part of your list is in another region, you are choosing between accepting the attendance cost and running two sittings. Both are legitimate. What is not legitimate is scheduling around your own convenience and then treating the resulting split as a reminder problem. When the honest answer is that they cannot all be in one room at one time, running it on their clock is the structural fix.

The highest-leverage artifact you will build.

Not because calendars are magic, but because the calendar is where the decision is actually made. On the day, nobody asks their inbox what they are doing at two o’clock. An email is a reminder competing with every other email; a calendar block is the schedule.

Hand it over at the moment of registration — on the confirmation page and in the confirmation email, both, because people register on phones and add things to calendars on laptops. An .ics file works everywhere; the “add to Google / Outlook / Apple” buttons are convenience on top of it rather than a replacement for it.

Write the entry as though it is the only thing they read

Because on the day it very often is. The description field is treated as a formality almost universally, which is why fixing it is cheap. Everything the attendee needs at the moment the alert fires should be inside the block itself.

TITLE
[Session title] — live with [Your name]

LOCATION / URL
[Join link — the personalised one, if yours are per-registrant]

DESCRIPTION
[45] minutes, live. We start at [time] [timezone] exactly.

Join here: [Join link]

Have ready: [the one thing they need open].
[Replay policy, in one sentence.]

Questions before we start: [email address]

ALERT
[15] minutes before

Three details in there do most of the work. The title says “live” and carries the session name rather than the words “webinar registration”, so it reads as an appointment rather than as a receipt. The join link is the room link, not a link back to the registration page — and if your links are personalised per registrant, the entry has to carry the personalised one, because a generic link in the calendar and a personal one in the email means half the room clicks the wrong thing at the worst possible moment. And the alert inside the entry is a reminder you do not have to send, delivered by a system the attendee already trusts more than they trust you.

If the time changes, update — never resend

A calendar update moves the existing block. A second invitation creates a second block, and the attendee now has two appointments, one of which is wrong, with no way to tell which. If you have to move a session, update the entry and say plainly in the email that the calendar item has moved itself.

Every send has one job. Name the job before you write the email.

The mistake is thinking of reminders as repetition — the same message at decreasing intervals until somebody gives in. A reminder sequence is a set of distinct jobs, and when two sends share a job, one of them is noise that teaches people the rest can be ignored.

Read the table as a set of constraints rather than a schedule. The T−1 hour send is not the place to add a bonus. The T−10 minute send is not the place for a paragraph. The T−3 day send is the only one allowed to be interesting, and it earns that by being useful on its own to somebody who never attends. Every send that reaches outside its job borrows attention from the one after it.

This page is the architecture; the copy is a separate artifact. All six sends are written out in full — subject lines, bodies, variations by business type — in the webinar email sequence templates. Take the timings from here and the words from there.

Channels other than email

SMS raises attendance where you have genuine consent, said on the registration page that you would use it, and use it once — at T−1 hour or T−10 minutes. Beyond that it burns goodwill considerably faster than it earns attendance, and an unannounced message arrives as a breach rather than as a reminder. The same rule applies to any channel where you are borrowing a more personal surface: one send, disclosed in advance, at the moment it is most useful.

Deliverability is an attendance problem

The T−10 minute send only works if it arrives within ten minutes. A sequence built perfectly and sent from a domain with no sending history, on the day, to a list that has never received anything from you, is how an immaculate architecture produces an empty room. If you have added a large number of unfamiliar registrants, the T−3 day send is doing double duty as a warm-up — it is the email that tells you, by whether it lands, whether the critical one will.

The same architecture transfers almost unchanged to one-to-one bookings, where the stakes per no-show are higher and the sends are shorter — the call version is its own pack.

Give them a reason to be there that is actually true.

The strongest attendance lever is not a reminder. It is that something happens in the room which does not happen anywhere else. Everything above is logistics for getting people to a thing worth attending; this is the part that makes it worth attending.

Reasons you can state and keep

1. 01Real questions, answered by name. Collect a question at registration from anyone who wants to ask one, then answer some of them out loud, naming the person. It is the easiest true promise on this list and the most consistently undersold.
2. 02A live review of something an attendee brings. A page, a plan, a set of numbers. Unrepeatable by definition, and the reason people clear a slot rather than bookmarking a replay.
3. 03A working session rather than a presentation. They leave with the thing built. Watching a recording of other people building something is a strictly worse experience, and everybody knows it.
4. 04A deadline that genuinely applies. An offer window that really closes, a cohort with a real seat limit, a replay window with a real end date. Real is the whole requirement.

That cost is worth naming precisely, because it is delayed enough to be invisible in the reporting. The people who rearrange their day are your most reliable cohort — the highest attendance you have, session after session. They are also the first to learn that showing up was unnecessary. You do not see the damage in this session’s number. You see it in the slow decline of the next four, in a figure you will attribute to something else.

And if the honest answer is that nothing about the session requires being live, that is information about the format rather than about your reminders. Either add the live element or accept a replay-first model and stop optimising a number that the design of the session does not support — turning it evergreen is often the more honest move.

Count the steps between the reminder and the room.

Open the email, find the link, click it, log in, install something, approve a permission, wait in a room with nothing in it, configure audio. Every one of those is a place people leave, and they leave at the exact moment you have already paid for their attention.

Remove what you can remove. An install step is the most expensive one, because it converts “I am joining now” into “I will do this later” for anyone on a phone or a locked-down work laptop. A login on top of a personalised link is a second door on the same doorway. A waiting room with nothing in it produces the question “am I in the right place”, and some proportion of people answer it by closing the tab.

Keep the door open early

Open ten minutes before the advertised start, with something on screen: a slide naming the session and the start time, and a question in chat that arrivals can answer. It converts “am I in the right place” into “I am in the right place and something is already happening”, and it gives the people who arrive on time a room that is already warm.

Then start on time, at the advertised minute. Waiting five minutes to let stragglers in teaches your audience that your start times are soft, which is a permanent cost paid for a temporary gain — and it punishes exactly the people who were punctual, who are the cohort you least want to train out of the habit.

Test it the way they will do it

From the real reminder email, on a phone, on cellular data, signed out of everything. Four minutes of work, and it is where expired links, install prompts and login walls make themselves known. Testing from the editor with the room already open in another tab tests nothing that can fail.

Have a plan for the failure you cannot prevent: a fallback link, a number for your co-host, and a message drafted in advance to send registrants if the room does not come up. The equipment checklist covers the hardware side of the same problem.

One show-up rate is an average of several.

Registrations from your own list, from a partner’s audience, from paid traffic and from a message you wrote to one person do not behave the same way on the day. The blended number is a summary of behaviours with different causes and different fixes.

So carry the source through to attendance. That is a plumbing question more than an analytics one: the tag has to survive from the link, through the registration, onto the attendee record. If it does not survive, everything in this section is an estimate and should be labelled as one — which is still better than a confident number built on a join you did not check.

What to do when it splits

A source with a low show-up rate is not automatically a bad source. It is often an audience with a different relationship to your calendar — people who registered out of mild interest rather than because they had the problem this week. What the split changes is concrete: how heavily you remind that cohort, whether you count its registrations toward your room target, and what you are willing to pay for more of it.

Repeat behaviour deserves its own decision. Someone who has registered twice and attended nothing is not a reminder problem and will not become one by receiving a seventh email. Ask them directly with a one-question message, or stop counting them in the forecast. Both are reasonable; adding volume is not.

And the no-shows you still get are not lost. They are a segment with a known interest and a known reason to hear from you, which is the entire premise of the follow-up window. The replay send to that segment is where a missed session turns back into something — and the no-show follow-up pattern applies to any booked time, not just webinars.

Show-up rate is low. Work these in order.

The instinct after a thin room is to rebuild the sequence. Almost always the cause is further up the list, cheaper to fix, and boring. Run the questions in this order and stop at the first honest yes.

1. 01Did the T−10 minute send actually go out? Check it left rather than checking it existed. A scheduled email that stayed in draft, a sequence that was never activated, a send that went out to a segment which had emptied itself — the most common cause of a bad show-up number is not a strategy failure, it is a send that did not happen. Confirm it before you conclude anything.
2. 02Does the join path work from the real email, on a phone? Not from the editor, not from your desktop with the room already open in another tab. From the actual reminder, on a phone, on cellular data. This takes four minutes and it is where install prompts, expired links and login walls announce themselves.
3. 03How long is the gap, and where is the promotion weight? If most registrations arrive twelve days out and nothing reminds them for a week, intent has to survive a week of everything else. Concentrating more of the promotion in the last two days shortens the gap for a large part of the room without shortening the window.
4. 04Is there a calendar entry, and is the join link inside it? An email is a reminder competing with every other email. A calendar block is the schedule. If the entry does not exist, or exists with a link to the registration page rather than to the room, this is the cheapest fix on the list.
5. 05Is there a true reason to be there live? If the honest answer is no — the same value is available from the replay, and everyone knows it — then reminders are being asked to do a job the format cannot support. Add the live element or accept the model and stop optimising for it.
6. 06Does the number look the same for every source? Split it before you conclude anything about the whole. One weak source can pull a blended number down far enough to make you rebuild a sequence that was working perfectly for everybody else.

Only after those six is it worth questioning the topic or the time — and by then you will usually have found the answer somewhere in the first three. The list below is sorted the same way: by what actually moves the number, rather than by what feels like effort.