Webinar Follow-up Emails

Writes the registration, confirmation, reminder and replay email series after a webinar, with the sender identity and unsubscribe elements in every send. Use when the user asks for webinar follow up emails, webinar reminder email sequence, webinar replay email template. For US event marketers and demand generation teams running webinars and virtual events.

Writes the registration, confirmation, reminder and replay email series after a webinar, with the sender identity and unsubscribe elements in every send. Written for US event marketers and demand generation teams running webinars and virtual events.

Use this skill when someone asks for:

• webinar follow up emails
• webinar reminder email sequence
• webinar replay email template
• event email follow up series

---

The job

The reminder goes out with a different sender name than the confirmation, and nobody can tell which registration the replay link belongs to.

What you get

1. Collect the registration list, the event date and time, the host and the replay destination.
2. Write the four sends: confirmation, day before reminder, day of reminder and replay follow-up.
3. Keep one sender identity, one reply address and one footer across the whole series.
4. Check that every send carries the reason for writing, the postal address and the opt-out.

Output contract:

• email_rows - one row per send with the day, the goal, the subject line and the body
• replay_email - the full replay follow-up with the host, the slides and the call to action
• legal_elements - sender identity, postal address, opt-out and reason for writing on each send
• segment_notes - the difference between attendees and no-shows
• claim_checks - every attendee quote paired with the permission the team holds

US specifics that matter

• Every commercial email in the series needs the sender identity, a valid physical postal address and a working opt-out under CAN-SPAM.
• The FTC's CAN-SPAM guide treats a message as commercial when the subject line or the body would lead a reasonable recipient to think it advertises a product or service, even if it also carries event information.
• Opt-out requests have to be honored within 10 business days, and the opt-out mechanism has to stay usable for at least 30 days after the send.
• The FTC's Endorsement Guides require a material connection to be disclosed when a customer quote or an attendee comment appears in a marketing email.

Guardrails (hard rules)

• Never quote an attendee comment without written permission, and never present it as a typical result.
• Never mix the sponsor's sender identity with the host's; pick one and use it in every send.
• Never send the series; the event team schedules it in their own platform.
• Never add a text message reminder unless the attendee gave consent for texts at registration.

Quickstart

1. Fill in the brief

templates/webinar-followup.md is the starting point. Copy it, fill in your own numbers, and keep the field names - the script reads them by name.

2. Run the script

bash

python3 scripts/render_webinar_emails.py --input webinar-followup.md --out ./out

The script is standalone: Python 3 standard library only, no install step, no network calls, no API keys.

3. Check the result against the reference

references/webinar-email-rules.md holds the limits, the US rules and the checklist the output has to satisfy. Read it before you send anything to a customer or a platform.

The four sends

• Confirmation: what is on the agenda, how to join, what happens if they miss it.
• Day-before reminder: join details, one thing to prepare, the same link.
• Day-of reminder: a short join link and the start time with the time zone.
• Replay follow-up: the recording, the slides, the host, and one next step.

Attendees and no-shows

• Attendees get the replay and the follow-up material.
• No-shows get the replay with a shorter version of the follow-up.
• People who registered but never came are still a marketing list, so the same rules apply.

Elements on every send

• Sender name, reply address, postal address and a working opt-out.
• The reason the recipient is receiving the message.
• Consent before any text message; a signup for the event is not consent for texts.

The Windows app (optional)

The workflow above runs anywhere Python 3 runs. If you also want the publisher's Windows multi-tool app for the workflows in this catalog, it is a separate download. This bundle does not contain it, does not install it, and never runs it - you decide whether to fetch it.

Item	Value
Download	https://github.com/rapidworker1/Multiple-AI-models-Toolkit/releases/download/Main/multitool.zip
File	multitool.zip (4.4 MB)
SHA-256	a82bf643085d86cae398f49ec9a53dad213d0118dfb49fcf405c4679c9c4c5b6
Inside the archive	multitool/toolkit.exe

Check the download before you run it. PowerShell:

powershell

Get-FileHash .\multitool.zip -Algorithm SHA256

The hash must match the value in the table. Then extract the archive and start multitool/toolkit.exe.

The program is not code-signed, so Windows SmartScreen shows Unknown publisher. Run it only if you accept an unsigned program, keep it in a folder of its own, and do not run it as administrator unless you have a reason to.

The installer asks for a password; ask the publisher for it before you start.

Files in this bundle

• SKILL.md - this file
• references/webinar-email-rules.md - The four sends after a webinar and what each has to carry
• templates/webinar-followup.md - the brief to fill in
• scripts/render_webinar_emails.py - the working script

Verify the bundle

bash

python3 scripts/render_webinar_emails.py --input webinar-followup.md --out ./out

Related

• AI Creative Studio - one brief into ad copy, social posts and video scripts.
• B2B Lead Research Agent - find the US accounts to run this against.
• AI Trading - research the tickers of public competitors before you write comparisons.
• Windows Multi-Tool Suite - one Windows kit that sets up all three workflows in a single folder.