Write Tiered Event Follow-Up Emails

Drafts post-event follow-up emails by lead tier, with a personalized first line from each lead's booth notes and send dates timed for the 24 to 48 hour window.

Example prompts

Once the skill is added, start a chat with one of these and attach your file if you have one.

  • Write follow-up emails for our A, B and C leads from the show. A leads get a personal note from the rep using their notes column.

  • Draft a 3-email sequence for people who visited the booth but didn't have a real conversation. Keep it short and not salesy.

  • Turn these 30 rep notes into one-line personalized openers I can merge into the follow-up email.

What this skill does

Generic "great to meet you at the show" blasts are easy to ignore. This skill writes follow-up the way a good rep would: A leads get a short personal note from their owner that picks up the actual conversation and proposes the next step, plus a call opener and a social note. B leads get the asset they asked about and a light three-email sequence. C leads get one useful touch.

Every opening line comes from that lead's notes and nothing is invented. Send dates are calculated from the event end date, EU and UK contacts without opt-in are kept out of marketing sequences, and the result is draft copy plus a merge file you can load into your email tool or CRM.

When to use it

  • The show just ended and you need follow-up out within 24 to 48 hours
  • Reps took notes and you want every email to use them
  • You need different follow-up for hot leads, warm leads and scan-only contacts
  • You want a post-show email cadence with send dates and subject lines
  • Someone asked for thank-you-for-visiting emails that don't sound like a blast

How it works

  1. 1IntakeReads your event context file, then asks once for the lead list, the offer or asset, senders and the event end date.
  2. 2Check the listCounts leads by tier, sets aside excluded leads and holds EU or UK contacts without opt-in out of marketing sequences.
  3. 3PersonalizeWrites a short opening line per lead from their notes and marks each one as specific, light or generic.
  4. 4Write sequencesDrafts the A, B and C emails with subject lines, word limits and one ask each, plus call and social variants for A leads.
  5. 5Schedule and hand offCalculates send dates in business days and returns the copy and a merge file. It never sends anything.

What you'll need

  • Lead list with lead tier, owner and notes (ideally from the event lead scoring skill)
  • Event name, dates and booth or session theme
  • The asset or offer to share and the meeting ask
  • Sender names and tone

What you get

Draft email copy for each lead tier with subject lines and send days, a call opener and social note for A leads, and a merge-ready CSV with each lead's personalized first line, sequence, sender, asset and send dates. A short plan summary lists counts by tier, held contacts and every placeholder you still need to fill, such as the asset and booking links.

Tips

  • Score the list first with the event lead scoring skill so each lead lands in the right sequence.
  • Better notes make better first lines. The booth notes to CRM skill can pull notes from Slack or voice memos.
  • Send A emails from the owner's own mailbox, not a marketing platform, so replies go to a person.
  • Keep one ask per email. A specific time beats "let me know when you're free".
  • Log campaign member statuses before the first send so replies and meetings are attributed to the event.

What's in the download

  • event-follow-up-sequences/SKILL.md7.8 KB
  • event-follow-up-sequences/assets/sample-tiered-leads.csv6.5 KB
  • event-follow-up-sequences/references/benchmarks.md1.3 KB
  • event-follow-up-sequences/references/email-examples.md3.0 KB
  • event-follow-up-sequences/references/sequence-playbook.md2.8 KB
  • event-follow-up-sequences/references/shared-terms.md6.6 KB
Read the SKILL.md
---
name: event-follow-up-sequences
description: Writes post-event follow-up email sequences for trade show, conference, field event and webinar leads, split by lead tier A, B and C. Personal one-to-one notes from the owner for A leads, asset-led emails for B leads and one light touch for scan-only C contacts. Uses each lead's booth notes for a personalized first line, sets send dates inside the 24 to 48 hour window and returns mail-merge-ready copy. Use for follow-up emails, a post-show email cadence, thank-you-for-visiting emails or personalized notes after an event.
license: MIT
metadata:
  author: eventmarketingsoftware.com
  version: "1.0"
  category: leads-and-follow-up
  source: https://eventmarketingsoftware.com/skills/event-follow-up-sequences
---

# Event follow-up sequences

Draft follow-up for every event lead by lead tier, using what was actually discussed. A leads get a short personal note from their owner, B leads get a useful asset and a light sequence, C leads get one touch. Output is draft copy plus a merge file; nothing is sent.

Lead tier, flags and timing follow [references/shared-terms.md](references/shared-terms.md). The ideal input is the scored file from event-lead-scoring. For registrants who didn't attend, use no-show-recovery instead.

## Intake

1. Read `event-context.md` (or `event-program-context.md`) if present: company, product one-liner, sender names, tone, assets, booking link placeholder.
2. Ask for anything missing, in one message:
   - The lead list with `lead_tier`, `owner` and `notes` (or a plain list, in which case ask whether to tier it first with event-lead-scoring or treat everyone as one tier).
   - Event name, dates, booth or session theme.
   - The offer: asset to share (guide, recording, case study), demo or meeting ask, any event-only offer.
   - Sender per tier (owner for A, owner or a marketer for B and C) and tone (plain and direct is the default).
   - Event end date and the time zone for send dates.
3. Don't invent links. Use placeholders like `{{asset_link}}` and `{{booking_link}}` and list them in the output.

## Connectors (optional)

- **HubSpot or Salesforce connector**: you may read lead notes and owners. Only create email drafts, sequence drafts or tasks after the approval gate. Never enroll contacts or send.
- **Google Sheets connector**: read the list, write the merge file to a new tab.
- **Otherwise**: return the copy in Markdown and the merge file as a CSV.

## Method

### 1. Check the list
- Count leads by tier. Leave out `Exclude` leads and say how many.
- Find leads flagged `eu_uk_no_optin`. They get only one-to-one emails about the conversation from their owner (A and B). Don't put them in any marketing sequence. For C leads with this flag, hold them in a separate list and ask the user what their privacy lead allows.
- Find leads with an open opportunity (`open_opp` yes): their owner writes, and the note should reference the existing conversation, not introduce the company.

### 2. Personalized first lines
For every A and B lead with notes, write one opening line that:
- Mentions something specific they said or asked ("You asked how routing works when two reps scan the same person").
- Is true to the notes. Never invent details, names, numbers or promises. If the note is vague, keep the line general and set `personalization = light`.
- Is under 25 words, in the sender's voice, and doesn't start with "I hope this finds you well" or "Just following up".
If there are no notes, use a line about the event and the booth or session topic and set `personalization = generic`.

### 3. Write the sequences
Use the cadence and rules in [references/sequence-playbook.md](references/sequence-playbook.md). Defaults:

| Lead tier | Sender | Touches | Timing (business days after the event ends) |
|---|---|---|---|
| A | Owner, one-to-one | Email 1, call or social note, email 2, email 3 | Day 1 (within 24 hours), same day, day 4, day 9 |
| B | Owner or event marketer | Email 1 with asset, email 2 with proof, email 3 soft meeting ask | Day 2 (within 48 hours), day 6, day 12 |
| C | Event marketer | One email with a useful resource, then nurture if consent allows | Day 3 to 5 |

Writing rules for every email:
- Plain text look, short paragraphs, one ask per email.
- A emails under 120 words; B under 150; C under 100.
- Subject lines under 7 words, specific, no clickbait, no fake "Re:".
- Reference the event by name in email 1 and drop it after.
- Use merge fields `{{first_name}}`, `{{company}}`, `{{personalized_first_line}}`, `{{owner_name}}`, `{{asset_link}}`, `{{booking_link}}`.
- No hype words, no "circle back", no guilt in the last email.
- Include an unsubscribe line on B and C marketing emails; A one-to-one emails don't need one but must not be bulk-sent.

### 4. Sales call and social note variants (A leads)
For each A lead, add a 3-line call opener and a social connection note under 300 characters that references the conversation.

### 5. Schedule
Compute send dates from the event end date: skip weekends, send mid-morning in the recipient's time zone if the country is known. For multi-day shows, A leads scanned on day one can go out before the show ends; ask the user.

## Output

**1. Plan summary**

| Lead tier | Leads | Sender | Touches | First send | Excluded or held |
|---|---|---|---|---|---|

Plus the list of placeholders the user must fill and any assumptions.

**2. Email copy per tier**, in this structure:

```
## Lead tier A: personal follow-up (sender: owner)
### Email 1, send day 1
Subject: ...
Body: ...
### Call opener
### Social note
### Email 2, send day 4
### Email 3, send day 9

## Lead tier B: asset-led sequence
...

## Lead tier C: one light touch
...
```

**3. Merge file** (CSV) with columns: `record_id`, `first_name`, `last_name`, `email`, `company`, `lead_tier`, `owner`, `sender`, `sequence`, `personalized_first_line`, `personalization` (specific, light, generic), `asset`, `email_1_date`, `email_2_date`, `email_3_date`, `consent_note`.

To try the skill, use `assets/sample-tiered-leads.csv` (28 scored leads from a fictional show that ended March 11, 2027).

Examples of good and bad emails are in [references/email-examples.md](references/email-examples.md). Why speed matters, with sources, is in [references/benchmarks.md](references/benchmarks.md).

## Validation checklist

- [ ] Every non-excluded lead is in the merge file once, in exactly one sequence.
- [ ] Every personalized line traces back to that lead's notes; nothing invented.
- [ ] A leads' first email is dated within one business day of the event end; B within two.
- [ ] No `eu_uk_no_optin` lead is in a marketing sequence.
- [ ] Leads with an open opportunity are written by the opportunity owner.
- [ ] Every placeholder is listed for the user; no made-up URLs.
- [ ] Word counts are inside the limits.

## Approval gates

- This skill drafts. It never sends email, enrolls contacts in sequences or posts anywhere.
- With a connector, show a preview of the drafts or tasks to be created (who, which template, which date) and get an explicit yes before creating them, and create them as drafts or paused.

## Privacy

Use only the notes and fields the user gave you. Don't look people up online to personalize. Keep personal data in the user's tools. Respect consent flags: EU and UK contacts without opt-in get one-to-one replies only, until the user confirms a lawful basis for marketing.

## Pushback

- "Send the same email to everyone": offer it for C leads only, and show how little extra work A personalization is when the notes exist.
- "Add urgency, say the offer expires tomorrow": only if the offer really does. Don't invent deadlines.

## Related skills

event-lead-scoring (tiers and owners), booth-notes-to-crm (richer notes for better first lines), no-show-recovery (registrants who didn't attend), crm-event-import (log the campaign member status before sending).

FAQ

How soon should you follow up after a trade show?
Common practice is to reach hot leads within 24 hours and everyone you had a real conversation with within 48 hours, while the conversation is still fresh. Scan-only contacts can wait three to five business days. This skill calculates send dates in business days from your event end date so A leads go out first.
What should a trade show follow-up email say?
Open with something specific the person said, offer the next step or resource you discussed, and make one clear ask, such as two possible meeting times. Keep it short, from a real person, and skip hype. Save the event name for the first email only. The skill includes good and bad examples so you can see the difference.
Will the skill send emails for me?
No. It writes drafts and a merge file. If your AI has a HubSpot or Salesforce connector, it can create drafts or paused sequences, but only after you've seen a preview and said yes. Sending stays with you or your reps.
What if the rep notes are empty or vague?
The skill never invents details. When notes are vague it writes a general opener and marks it as light personalization. When there are no notes it uses a line about the event and the booth topic and marks it as generic, so you can see which leads would benefit from a rep adding context first.
Can I email EU or UK booth visitors after the event?
It depends on consent and your lawful basis, so check with your privacy lead. By default the skill keeps EU and UK contacts without opt-in out of marketing sequences and limits them to one-to-one follow-up from their owner about the conversation they had, and it holds scan-only contacts for your decision.