---
name: event-invite-sequence
description: Writes registration and attendance email sequences for B2B events. Covers invites, last-chance emails, confirmation, calendar invite text and reminders for webinars, virtual events, field events, executive dinners and conferences, with versions for prospects, customers and target accounts, sales rep personal invite templates and a dated send schedule. Use for event promotion emails, invitation copy, webinar reminders, driving registrations or improving show-up rate.
license: MIT
metadata:
  author: eventmarketingsoftware.com
  version: "1.0"
  category: promotion
  source: https://eventmarketingsoftware.com/skills/event-invite-sequence
---

# Event Invite Sequence

Writes the full email program around one event: the promotion emails that get people to register and the confirmation and reminder emails that get them to show up. Output is a dated send schedule plus ready-to-load drafts, segmented by audience, with personal invite templates sales reps can send from their own inbox.

Two jobs, two audiences. Invites go to people who haven't registered. Confirmation and reminders go only to registrants. Never mix them, and always suppress registrants from the remaining invites.

## Intake

If the user has an `event-context.md` file, read it first and don't ask for anything it already answers (company, ICP, sender names, tone, CRM).

Ask for whatever is missing in ONE message:

1. Event title, format (webinar, virtual event, field event, executive dinner, roundtable, conference or user conference, trade show booth or party), date, start time and time zone, length, location or join method.
2. Why someone should come: the problem it solves, 3 things they'll learn or get, speakers and their titles, any customer speaker.
3. Audience segments to write for (default: prospects, customers, target accounts) and roughly how many invitees per segment.
4. Registration link placeholder, capacity limit or approval step (common for dinners), and whether there's a replay.
5. Sender: the brand, a named person, or the account owner. Rep invites needed? (yes by default for dinners, roundtables and target accounts.)
6. Today's date or the date promotion can start.
7. Optional: last event's registrations and show-up rate, if they want the sequence tuned.

Work with partial answers. Use clear placeholders like `[REG LINK]`, `[SPEAKER 2 TITLE]` instead of inventing facts.

## Data sources (connectors optional)

- If a HubSpot or Salesforce connector is available, you may read the campaign, list sizes or the invite list to count segments. Only create draft emails or draft lists after an explicit yes. Never schedule or send.
- If a Google Sheets connector is available, offer to write the send schedule to a new tab.
- Otherwise, work from pasted text, an uploaded CSV or XLSX invite list, or plain answers, and return Markdown plus a downloadable CSV of the send schedule.
- Never require a paid service. Never fetch URLs, including the registration page.

Sample invite list for testing: [assets/sample-invite-list.csv](assets/sample-invite-list.csv).

## Method

0. **Check the list (only if one is shared).** Dedupe on lowercased email, set aside rows with no email, remove anyone already registered, unsubscribed or marked competitor, then count by segment and by sender. Flag EU and UK rows without a clear opt-in (see Privacy). Report rows in, rows set aside and why, and rows out per segment. Don't rewrite the list itself.
1. **Pick the cadence for the format.** Use the patterns in [references/sequence-patterns.md](references/sequence-patterns.md). Defaults:
   - Webinar or virtual event: 3 invites over 2 to 4 weeks, plus a last-chance email the day before or morning of.
   - Field event, dinner or roundtable: rep personal invite first, then 2 brand invites, then a waitlist or last-seats note. Start 4 to 6 weeks out.
   - Conference or user conference: announcement, early-rate deadline, agenda reveal, speaker highlight, final push. Start months out; ask for the key dates.
   - Trade show presence: a "meet us" email offering a booked meeting or session, not a booth number alone. Point the user to a meeting outreach workflow for 1:1 asks.
2. **Count backward from the event date.** Turn every relative day into a real date and weekday in the event's time zone. Avoid weekend sends for B2B unless the user says otherwise. Flag any send that lands on a public holiday you know of in the audience's main country and ask.
3. **Segment the copy.** Same facts, different angle:
   - Prospects: lead with the problem and the takeaway. No product talk.
   - Customers: lead with what's new, peer learning or roadmap access. Say "as a customer" once.
   - Target accounts: shorter, personal, names the account's likely priority if the user gave one. Usually sent by the account owner.
   - Partners or speakers' networks: give them a share-ready version.
4. **Write each invite with one job.** Each email adds something new: invite 1 is the promise, invite 2 is the agenda or speaker angle, invite 3 is a proof point or a question the session answers, last chance is short and plain. One primary call to action per email. Subject lines under about 50 characters, no all caps, no fake "RE:" or "FWD:".
5. **Write the registrant track.** Confirmation (immediately, with calendar text and what to expect), reminder 1 day before, reminder about 1 hour before (webinars) or morning of (in-person, with address, parking, check-in and a contact number), and a "we're live" or "starting now" email for webinars. For dinners add an RSVP reconfirmation 3 to 5 days before so you can release seats to the waitlist.
6. **Write calendar invite text.** Title, plain-text description with the join link or address, time zone stated, and a one-line agenda. Keep it under about 600 characters so it shows fully in most calendars.
7. **Write rep templates.** 2 to 3 short plain-text versions (cold-ish prospect, open opportunity, customer) under 90 words, written as the rep, with one personal line to fill in.
8. **If they shared a show-up problem,** diagnose it with the checklist in [references/sequence-patterns.md](references/sequence-patterns.md#show-up-checklist) and rewrite the reminders. Compare to the dated ranges in [references/benchmarks.md](references/benchmarks.md) only if the user wants context, and say which denominator each source uses.

Domain rules that matter:
- Suppress registrants from later invites and suppress anyone who unsubscribed or is a competitor.
- Invites to people without marketing consent should go from the account owner as a 1:1 note, or not at all, depending on the user's policy and region (see Privacy).
- Every email needs the event date, time with time zone and format in the first two lines. Webinars: show the time in the audience's two biggest time zones, and recheck the offset when a daylight saving change falls between regions (US and Europe switch on different weekends in March and in October to November).
- Don't promise a replay unless the user confirms one. If there is one, mention it in the last-chance email, not the first invite, so it doesn't lower live attendance.
- Track registrations by source: give each email and each rep template its own UTM content value, e.g. `utm_content=invite-2-prospect`.

## Output templates

Full examples: [references/email-examples.md](references/email-examples.md).

**1. Send schedule** (also as CSV):

| # | Send date | Weekday | Time (TZ) | Track | Email | Segment | Sender | Subject | Preview text | CTA | UTM content | Suppress |
|---|---|---|---|---|---|---|---|---|---|---|---|---|

Track is `Invite` or `Registrant`. Suppress lists who must not get it (e.g. "Registrants, unsubscribes, competitors").

**2. Each email draft:**

```
Email: Invite 2, Prospects
Send: Tue 3 Mar, 10:00 ET
From: [Sender name], [Company]
Subject: [option A] / [option B]
Preview text: [up to about 90 characters]

[Body, 60 to 150 words for invites, plain paragraphs, one CTA]

CTA button: [label] -> [REG LINK]?utm_content=invite-2-prospect
```

**3. Calendar invite text.** **4. Rep personal invites.** **5. Notes and open questions** (every placeholder and assumption listed).

## Validation checklist

- [ ] Every send date is a real date with weekday, in order, and none falls after the event (except post-event, which belongs to a follow-up workflow).
- [ ] Invite track and registrant track are separate; registrants are suppressed from later invites.
- [ ] Date, time with time zone and format appear in the first two lines of every email.
- [ ] One primary CTA per email, each with a unique UTM content value.
- [ ] No invented facts: speakers, numbers, prizes and replay claims all came from the user or are placeholders.
- [ ] Subject lines are under about 50 characters and differ from each other.
- [ ] House style: contractions, plain words, no hype, no dashes as punctuation.

## Approval gates

- Return drafts only. Never send, schedule or create campaigns in a CRM or email tool without showing the exact content and getting a clear yes.
- Before creating any list or draft in a connected tool, show the list criteria and counts and ask.

## Privacy

- If you see the invite list, flag contacts in the EU or UK (by country field, or by email domain like `.de`, `.fr`, `.co.uk` when country is missing) who lack a recorded opt-in. EU ePrivacy rules with GDPR, and the UK's PECR with the UK GDPR, often require prior consent for marketing email, and the rules for business addresses differ by country. Recommend a 1:1 rep note or excluding them, and let the user decide with their legal team.
- Flag rows with no consent field at all instead of assuming consent.
- Keep the list in the user's tools. Don't repeat personal data in the output beyond counts and the flagged rows' IDs.

## Related skills

event-landing-page (registration page copy), event-social-kit (social promotion), webinar-run-sheet (running the session), no-show-recovery and event-follow-up-sequences (after the event).
