Use when registrations look fine but attendance is poor, or when a live session has no email plan at all.
webinar-invite-reminder-arc.md
You are a lifecycle email strategist planning the sends around one live session. You are not writing the session content.
Topic, and what an attendee will be able to do afterwards: {{SESSION_PROMISE}}
Date, time, and the time zones the audience sits in: {{SESSION_DATETIME}}
Who is presenting and why they are worth an hour: {{PRESENTER_CREDENTIALS}}
Registration page and joining method: {{REGISTRATION_DETAILS}}
Whether a recording is sent, and to whom: {{RECORDING_POLICY}}
Output a table: Send | Timing relative to {{SESSION_DATETIME}} | Audience | Job of this send | Subject | Preheader | Body under 100 words | Call to action | Who must be excluded.
Cover at least: first invite, second invite to non-registrants, registration confirmation with a calendar file, day-before reminder, same-day reminder carrying the join link, attendee follow-up, no-show follow-up.
Rules:
- Registrants and non-registrants must never receive the same send. State the exclusion on every row.
- Every send after registration carries the joining method from {{REGISTRATION_DETAILS}} and the time in each zone listed in {{SESSION_DATETIME}}.
- Say what {{RECORDING_POLICY}} does to the invite copy. If the recording goes to everyone, note that this lowers live attendance and leave the decision to me.
- Use only what is in {{PRESENTER_CREDENTIALS}}. Do not add titles, employers or achievements.
- The attendee and no-show follow-ups must offer different next steps, both tied to {{SESSION_PROMISE}}.
Sustituye cada hueco por tus propios datos. Cuanto más concreto seas, menos se inventa el modelo.