The registration page, the confirmation and reminder emails, the calendar invite.

This playbook covers a recurring event — a monthly pitch event, mastermind, or capital connections session that runs on the same page every month with a new lineup.

What Gets Built

Piece What it does
Evergreen landing page One URL that never changes. Hero, this month's lineup, registration form, past-event proof.
Registration form Name, email, phone. Feeds the event workflow and tags the registrant with the month.
Confirmation email Fires instantly. Contains the join link and the add-to-calendar link.
Calendar invite Sent on registration so the event lands in their calendar, not just their inbox.
Reminder sequence 24-hour and 1-hour reminders, both carrying the join link.
Follow-up Separate paths for attended vs. registered-but-didn't-show.
Monthly reset Custom Values swap the date, lineup, and join link. The page and automations are untouched.

The Monthly Reset (5 minutes)

Do this once per month. You are only changing values — never rebuilding the page.

  1. Settings > Custom Values — search your event name and update Event Date, Event Time, Join Link.
  2. Swap this month's lineup block on the landing page (headshots, bios, links). Then publish the funnel — saving alone does not push it live.
  3. Open the page in an incognito window and confirm the new date and lineup appear.
  4. Submit one test registration with your own email. Confirm you get: confirmation email, calendar invite, and that the reminder workflow shows you enrolled.
  5. Check the registration tag is set to the new month so this month's registrants aren't mixed with last month's.

Gotchas We Have Actually Hit

Every one of these came out of a real support ticket on a live event page. Check them before you report a bug — the fix is usually one of these five.

Your edit doesn't appear on the live page. Saving is not publishing. Go back into the funnel and publish, then reload in an incognito window. If it still doesn't show, tell us — the section may be inside an element that didn't re-render.

Form edits won't save and revert to the old version. Close every other tab and session that has the form open, then edit in one place only. Two open editors overwrite each other. If it still reverts after that, send us the form name and we'll take it.

A form field only accepts numbers. Custom fields default to a number type when created quickly. Open the field, set the type to single-line text, and re-publish. Worth checking every field before you launch a form that outside applicants will fill in.

Buttons or cards stack on top of each other on mobile. A row with several people in it collapses into one column on phones. Each person needs their own row (or a stack-safe column setting) so their button stays attached to them. Always open the page on an actual phone before you announce the event.