event-attendee-email-sequences

Designs and writes dated attendee email sequences for technical events from announcement to post-event follow-up.

1|Updated Sep 6, 2026
One-click install
npx skills add https://github.com/samber/dev-event-organizer-skills --skill event-attendee-email-sequences-samber
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: event-attendee-email-sequences
Source: https://github.com/samber/dev-event-organizer-skills/tree/main/skills/event-attendee-email-sequences
Command: npx skills add https://github.com/samber/dev-event-organizer-skills --skill event-attendee-email-sequences-samber

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Event organizers either over-email attendees with SaaS-style drip campaigns or under-communicate logistics, causing no-shows, confused arrivals, and burned mailing lists. This Skill produces a dated send map and the actual copy for every attendee email, grounded in what real event organizers send. ## Core Features & Use Cases - Dated send map: Maps a fixed arc (announcement, confirmation, agenda release, last call, know-before-you-go, day-before nudge, post-event thank-you) onto the dates handed down by the marketing plan, with one job per email. - Sourced cadence and segmentation menus: Picks sequence depth, reminder cadence (2-4 sends, not a drip), and segmentation depth from ranked menus with explicit promotion and deletion conditions. - Know-before-you-go builder: Builds the week-before email against a sourced 14-section structure, with code of conduct and accessibility as non-negotiable sections. - Consent and list hygiene checks: Verifies per-address opt-in provenance before any send, treating a ticket purchase as transactional consent only. - Use Case: A first-time conference organizer asks how many emails to send before doors open; the Skill rejects a 10-touch nurture sequence, proposes the five-send core arc mapped to fixed dates, and drafts humanized copy for each. ## Quick Start Ask the assistant to plan the attendee email sequence for your event, giving it the announcement date, agenda-release date, doors date, and where your mailing list addresses came from.

Frequently Asked Questions about event-attendee-email-sequences

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How many emails should I send attendees before an event?

Send roughly 2 to 4 reminder emails across the whole pre-event arc, not a SaaS-style drip. The default core arc is five sends: announcement, registration confirmation, know-before-you-go one week out, a day-before nudge, and a post-event thank-you.

What goes in a know-before-you-go email for a conference?

It follows a 14-section structure covering code of conduct, check-in walkthrough, location, schedule, food, transit, accessibility, and contact routes. Code of conduct and accessibility sections are never cut for length because they decide whether someone attends at all.

Can I email last year's ticket buyers about this year's event?

A ticket purchase is consent to transactional messages only, not marketing. You need a documented per-address opt-in and sign-off before reusing a prior edition's list; an unsubscribe link is not a substitute for consent.

Should event reminder emails use open and click tracking to branch?

No. Every send moment in an event arc is a fixed calendar date, never a per-recipient behaviour. Behavioural branching needs marketing-automation tooling a volunteer-run event does not have and targets the wrong mechanic for a dated arc.

What is a good open rate for conference attendee emails?

No valid benchmark exists for event attendee email; published figures blend unrelated senders and predate mail-client privacy changes. Measure binary gates instead: know-before-you-go completeness and per-segment cap compliance, plus self-set signals like desk questions already answered in the email.

When should I not build an attendee email sequence at all?

When the event has no registration, there is no attendee list and nothing to sequence. Publish the practical information once on the event's own page and send a single announcement through existing channels instead of constructing a list.