How do you write an event invitation email sequence?

Seven emails, one stop rule, two follow-ups.

What is the full sequence, and when does each email go out?

An event invitation sequence is not one email sent three times. It is seven emails with seven different jobs, and the list of people who receive each one shrinks as registrations come in. The table below is the timeline we use for a webinar, a roundtable, a conference meetup or a dinner. Shift the dates for your event; keep the order and the jobs.

Three things in the table are easy to miss. The nudge is a plain email from a named person, not a designed campaign. The confirmation goes out the moment someone registers, not in the next batch. And the two follow-ups are separate emails to separate lists, not one email with a line that says "if you could not make it".

How do you write the invite itself?

Most invites are written around the venue, the date and the host. None of those is a reason to give up an evening or an hour of a workday. The two things a busy person actually weighs are who else will be there and what they will walk away with. Lead with those, and put the logistics after.

"Who else" does not mean name-dropping. It means titles and company types: "twelve finance leaders from Series B and C software companies" is enough. "What they leave with" should be concrete: a benchmark they cannot get elsewhere, a decision they are stuck on, or three peers they can call next quarter. If you cannot write either sentence, the event is not ready to be invited to.

The invite checklist

Every invite email in the sequence should contain all seven of these.

The agenda reminder uses the same checklist with a different lead: the first line names the specific questions or sessions, because by then the people who were sold on the room have already registered. You are now writing for the people who need a reason tied to the content.

Who gets a personal note, and who gets the broadcast?

Split the list before the first send. The broadcast goes to everyone who fits the event: the right function, a company of the right size, in a region that can actually attend. The personal nudge goes to a much shorter list, usually the titles you most want in the room and the accounts your sales team is already working. For a 40-seat webinar that might be 30 people. For a 12-seat dinner it is the whole list.

The nudge is short, in plain text, from the host or a senior person, and it references something true about the recipient: their role, a post they wrote, a problem their company is known to have. It should read like it took two minutes to write for that one person, because it did. Templates help with the structure; the first line is written by hand. If the host also sends a LinkedIn message, send it the same day as the nudge and say the same thing, so the two channels confirm each other rather than compete. The executive dinner article goes deeper on that pairing.

When do you stop sending invites to someone?

The moment they register. This is the stop rule, and it is the single most common mistake in event email. A person who signed up on the first invite and then receives the agenda reminder, the nudge and a "last chance" email learns that your list is not paying attention. Some of them mark it as spam. Google asks senders to keep the spam rate in Postmaster Tools below 0.10% and never to reach 0.30%, and a mis-sent event series is a fast way to drift toward that line.

Set the rule up as a suppression in your email platform before the first send: anyone with the registration tag is excluded from the invite, agenda and nudge audiences, and is added to the confirmation, day-before and follow-up audiences. Re-check the audiences before each send, because registrations arrive between sends.

Keep the confirmation email clean

The FTC's CAN-SPAM guide draws a line between commercial content and transactional content. An email whose only purpose is to confirm something the recipient already agreed to is transactional, and that kind of email is exempt from most of the Act's rules. Your confirmation and logistics email should stay on that side of the line: the seat, the calendar file, the address or the join link, what to bring, who to contact. Do not add a pitch for your product. Google's sender guidelines make the same point from a deliverability angle: do not mix different types of content in one message, and send each category from a consistent From address.

What do you send after the event?

Two emails, to two lists, within a day. Both carry the same payload: the recording, or for a dinner or a roundtable with no recording, a one-page set of notes with the three or four points that came up. The difference is the opening and the ask.

People who registered and did not attend are not cold. They told you the topic matters and the day did not work. Treat that list the way you would treat the warmest segment in a re-engagement sequence: one useful message, one clear next step, then back into normal cadence.

What should you measure?

Not opens, and not total registrations. Three numbers tell you whether the sequence did its job: registrations from your target titles, the share of registrants who attended, and the number of meetings booked in the two weeks after the event. The first one tells you whether the invite was aimed well. The second tells you whether the confirmation and the day-before email did their work. The third is the only one that connects the event to revenue.

Expect attendance to vary a lot with format. A free webinar on a Tuesday afternoon and a seated dinner with a confirmed seat behave very differently, and the right comparison is your own last event of the same type, not a benchmark from a vendor. One dinner campaign Sawa ran with Chameleon Collective in 2026 shows the shape, without the send dates: a target of eight seats, less than a month to fill them, roughly 30 target buyers mapped through the network for introductions, personalised LinkedIn invitations alongside, and a second outreach wave that moved the reply rate from 1% to 6% once the audience was narrowed to ecommerce leaders. The campaign brought in nearly 15 signups. Attendance was not confirmed to us, and a reply is not a seat. A run like that, laid against the timeline above, shows where registrations actually arrive: usually a wave on the first invite, a smaller one on the agenda reminder, and a third from the personal nudges.

Does this change for a dinner or a small roundtable?

The order is the same. Three things change. The personal nudge becomes the main event rather than a supplement, because every seat matters. The confirmation often goes out as a calendar invite from the host, which carries its own accept and decline links. And the day-before email names who is coming, by title, because at a dinner the guest list is the product. Sawa's public CTO dinner case study is an example of the small-room version.

For the opposite case, a launch where the list is large and the ask is a demo rather than a seat, see the product launch sequence. Both sit inside the broader guide to B2B email campaigns, which covers when an event is the right campaign at all.

Need help with this? See how Sawa handles event and launch campaigns, or book an intro call.