Launch checklist

FullHouse only insists on a validated video and a schedule before you publish. Everything else on this list is up to you, and it’s what separates a webinar that works from one that converts.

Account and sending

• Your email sender has a From name and a Reply-to you actually read.
• You’ve checked your daily email limit against your expected volume. One registrant can get up to six emails on a default webinar, and emails over the limit fail rather than wait. For bigger launches, connect your own provider.
• Your branding is set, including a legal footer with your business name and address.
• Two-factor authentication is on.
• Anyone else helping with the launch has their own login on your team.

Video

• The video passed validation, with no warnings you haven’t read.
• You’ve watched it through from a phone as well as a computer.
• Captions are uploaded, if you use them.

Schedule

• The schedule shows the times you expect, and the timezone is right.
• Holidays and days off are added as blockout dates.
• Allow joining in progress and Late join grace match how strict you want to be.

Registration and emails

• The registration page reads well on a phone, and you’ve looked at the preview.
• You’ve chosen a short, readable URL slug. Old links keep working if you change it later, but your ads and pages should use the address you mean to keep.
• Consent wording suits where your audience lives.
• The thank-you page message, calendar buttons and any redirect are what you want.
• Reminder and follow-up emails are in your voice, and you’ve sent yourself a test of each.

In the room

• The waiting room note and points read well.
• Offers appear at the right moment, and their links go to the right checkout.
• Polls and handouts are placed and working.
• You’ve chosen a chat mode and decided who watches the room if chat is shared.
• AI answers are tested, if they’re on, and the context includes what people really ask.
• The exit redirect, if you have one, goes to the right page.

Afterwards

• Replay timing and expiry are what you intended.
• Automations and webhooks have fired for a test registrant, and you’ve seen the result in your CRM.
• Tracking pixels fire on the real public page. They don’t run in the preview.

For a challenge

• Every day has a working video and a real Title, not the one it started with.
• The sign-up page’s label, button and consent text talk about a challenge, not a webinar.
• The challenge emails are rewritten for each day.
• You’ve decided when to pause sign-ups. They don’t close by themselves.
• Your pixels are in the challenge’s Tracking section for the sign-up page and hub, and in each day’s own Tracking step for its room.

The final test

Publish, then go through it as an attendee, using an address you can check.