---
title: "Launch checklist"
description: "Everything to check before you send real traffic to a webinar or challenge."
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.meetfullhouse.com/llms.txt
> Use this file to discover all available pages before exploring further.

# 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](/workspace/email) has a **From name** and a **Reply-to** you actually read.
- [ ] You've checked your [daily email limit](/workspace/plan-usage) 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](/workspace/email).
- [ ] Your [branding](/workspace/branding) is set, including a legal footer with your business name and address.
- [ ] [Two-factor authentication](/workspace/account-security) is on.
- [ ] Anyone else helping with the launch has their own login on your [team](/workspace/team).

## Video

- [ ] The video [passed validation](/webinars/video), with no warnings you haven't read.
- [ ] You've watched it through from a phone as well as a computer.
- [ ] [Captions](/webinars/video) are uploaded, if you use them.

## Schedule

- [ ] The [schedule](/webinars/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](/webinars/registration-page) reads well on a phone, and you've looked at the preview.
- [ ] You've chosen a short, readable [URL slug](/webinars/details#set-the-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](/webinars/thank-you-page) message, calendar buttons and any redirect are what you want.
- [ ] [Reminder](/webinars/reminder-emails) and [follow-up](/webinars/follow-up-emails) emails are in your voice, and you've sent yourself a test of each.

## In the room

- [ ] The [waiting room](/webinars/waiting-room) note and points read well.
- [ ] [Offers](/webinars/offers) appear at the right moment, and their links go to the right checkout.
- [ ] [Polls](/webinars/polls) and [handouts](/webinars/timeline) are placed and working.
- [ ] You've chosen a [chat mode](/webinars/chat-questions) and decided who watches the room if chat is shared.
- [ ] [AI answers](/webinars/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](/webinars/replay) timing and expiry are what you intended.
- [ ] [Automations](/webinars/automations) and [webhooks](/connect/webhooks) have fired for a test registrant, and you've seen the result in your CRM.
- [ ] [Tracking pixels](/webinars/tracking) fire on the real public page. They don't run in the preview.

## For a challenge

- [ ] Every day has a [working video](/challenges/days) and a real **Title**, not the one it started with.
- [ ] The [sign-up page's](/challenges/registration-hub) label, button and consent text talk about a challenge, not a webinar.
- [ ] The [challenge emails](/challenges/emails) are rewritten for each day.
- [ ] You've decided when to [pause sign-ups](/challenges/publish-manage#pause-or-stop-sign-ups). They don't close by themselves.
- [ ] Your pixels are in the challenge's [Tracking](/challenges/registration-hub#tracking-on-these-pages) section for the sign-up page and hub, and in each day's own [Tracking](/webinars/tracking) step for its room.

## The final test

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

1. **Register**

   Register from the public link on your phone, with UTM tags on the link so you can see them come through in [the report](/run/overview-report).
2. **Check the emails**

   Check that the confirmation email arrives, isn't in spam, and that its link opens your waiting room.
3. **Sit through a session**

   Watch the room, send a question, answer a poll, click an offer, and leave a rating on the end-of-session page.
4. **Check it landed**

   See your test on the [Registrants](/run/registrants) tab, its question under [Questions](/run/questions), and any failures under [Debug](/workspace/debug).
5. **Watch the replay**

   Open the replay link once it's available.

:::note
Your test registrations count in your numbers until you remove them. [Delete each one](/run/registrants#delete-a-registrant) from the **Registrants** tab before real traffic arrives, and it leaves your counts and reports.
:::

Source: https://docs.meetfullhouse.com/start/launch-checklist/index.mdx