---
title: "Event Registration Email Template: 6 Confirmation Examples"
description: "Event registration email templates for B2B events — what a confirmation email must include, six copy-paste examples, and subject lines that get opened."
canonical: "https://attendir.com/blog/event-registration-email-template"
updated: "Oct 5, 2026"
---

# Event Registration Email Template: 6 Confirmation Examples

An event registration email template is a ready-to-edit confirmation message sent the instant someone registers. A good one states the event name, date and time with the time zone, the venue address or join link, add-to-calendar links, what happens next, how to cancel or transfer, and who to contact — before anything promotional.

The confirmation email is the one event message the recipient is actively waiting for. They just filled in a form and want proof it worked. Too often that attention goes to an auto-generated receipt: an order number, a logo, and the event details buried under legal text.

This guide covers what a registration confirmation email must contain, six copy-paste templates for B2B formats — a conference, a webinar, an invite-only executive dinner, a trade show booth meeting, a waitlist and a group registration — the subject line patterns that work, the technical basics that get the email delivered, and why the confirmation is the best moment to ask someone to tell their network they are going.

## What a Registration Confirmation Email Must Contain

Treat this as a checklist.

| Element | What to include | Why it matters |
|---|---|---|
| Event name | The full name, exactly as on the landing page | Confirms they registered for the right thing |
| Date and time | Day, date, start and end time, with the time zone spelled out | "2pm" means nothing to a distributed audience |
| Location or join link | Full street address as a maps link, or the personal join link | The detail people search their inbox for later |
| Add to calendar | Links for Google Calendar, Outlook and an .ics file | A registration that never becomes a calendar entry is easy to forget |
| What happens next | When reminders arrive, when the agenda is published, whether there is a recording | Sets expectations so later emails are recognized, not ignored |
| Cancel or transfer | One link to cancel, and how to send the seat to a colleague | Frees seats early instead of leaving empty chairs |
| Contact | A real person's name and a reply-to address that is monitored | Questions go to someone who can answer them |

Order matters as much as content. Put the event name, time and access details in the first screen, the calendar links directly under them, and everything else below.

Two details are easy to miss: offer a second time zone if the audience spans regions ("2:00pm ET / 7:00pm BST"), and put the join link or address inside the calendar event itself.

## Template: In-Person B2B Conference

> **Subject:** You're registered: [Event name], [Month Day], [City]
>
> Hi [First name],
>
> You're confirmed for **[Event name]**.
>
> **When:** [Day, Month Day], 8:30am–6:00pm [time zone]
> **Where:** [Venue name, full address] — **[Open in maps]**
> **Your ticket:** [Ticket type] — show this email or your name at check-in
>
> **[Add to Google Calendar]** · **[Add to Outlook]** · **[Download .ics]**
>
> **What happens next:** The full agenda goes live on [date]. We'll send logistics one week out and again the morning of the event.
>
> **Can't make it?** [Transfer your ticket to a colleague] or [cancel your registration].
>
> Questions? Reply to this email — it comes to me.
>
> [Host name], [Title], [Company]

The transfer link is worth the extra line: a ticket handed to a colleague is an attendee you keep.

## Template: Webinar or Virtual Event

> **Subject:** Confirmed: [Session title], [Day] at 2pm ET
>
> Hi [First name],
>
> You're registered for **[Session title]**.
>
> **When:** [Day, Month Day], 2:00pm ET / 7:00pm BST (45 minutes)
> **Join link:** **[Your personal join link]** — this link is unique to you, please don't forward it
>
> **[Add to Google Calendar]** · **[Add to Outlook]** · **[Download .ics]**
>
> Can't attend live? Stay registered — everyone who signed up gets the recording.
>
> [Host name]

Keep the join link here even though reminders will repeat it — some registrants will search their inbox for it five minutes before start. For the reminder sequence that follows this email, see the [event reminder email guide](https://attendir.com/blog/event-reminder-email); for the whole webinar lifecycle, including the follow-up after the session, see the [webinar email templates](https://attendir.com/blog/webinar-email-templates).

## Template: Executive Dinner or Roundtable (Invite-Only)

Invite-only events need two emails, because a request to attend is not yet a seat.

**Variant 1 — Request received (approval pending)**

> **Subject:** We received your request — [Dinner name], [Date]
>
> Hi [First name],
>
> Thanks for requesting a seat at **[Dinner name]** on [Day, Month Day] in [City].
>
> Seating is limited to [number] guests, so we confirm each place personally. You'll hear from me by [date] either way.
>
> Nothing to do in the meantime. Please hold the evening if you can.
>
> [Host name]

**Variant 2 — You're confirmed**

> **Subject:** You're confirmed — [Dinner name], [Day] at 7pm
>
> Hi [First name],
>
> Good news: your seat is confirmed.
>
> **[Restaurant name], [address]** — 7:00pm for a 7:30 sit-down
> **Topic:** [Discussion topic]
> **Guests:** A table of [number] [role descriptor, e.g. heads of RevOps]
>
> **[Add to calendar]**
>
> If plans change, just reply. We keep a short waitlist and would rather pass the seat on than leave it empty.
>
> [Host name], [direct phone number]

Send both from a named person, not a no-reply address.

## Template: Trade Show Booth Meeting Confirmation

> **Subject:** Confirmed: [Your name] + [Company] at [Show name], Booth [number]
>
> Hi [First name],
>
> Looking forward to meeting at **[Show name]**.
>
> **When:** [Day, Month Day], [start time]–[end time] [time zone]
> **Where:** Booth [number], [Hall name] — **[Floor plan link]**
> **Who you'll meet:** [Rep name], [Title] — [mobile number] if you're running late
> **Agenda:** [One line on what you'll cover]
>
> **[Add to calendar]**
>
> Need to move it? **[Pick a new time]** — the show floor gets busy, so earlier slots fill first.
>
> [Rep name]

Include the mobile number; on a show floor, email is too slow.

## Template: Waitlist Confirmation

> **Subject:** You're on the waitlist for [Event name]
>
> Hi [First name],
>
> [Event name] is at capacity, and you're on the waitlist.
>
> **How it works:** When a seat opens, we offer it to the next person on the list by email. You'll have [48 hours] to accept before it moves on.
>
> **Event details, in case you get in:** [Day, Month Day], [time and time zone], [location or "online"].
>
> You don't need to do anything now. If you'd rather come off the list, [remove me from the waitlist].
>
> [Host name]

Leave calendar links out of waitlist emails; an entry for an event they may not attend only confuses.

## Template: Group or Colleague Registration

For one person registering several colleagues, send a summary to the booker and an individual confirmation to each attendee.

**To the booker**

> **Subject:** [Number] seats confirmed for [Company] — [Event name]
>
> Hi [First name],
>
> You've registered [number] people for **[Event name]** on [date]:
>
> [Name 1] — [email]
> [Name 2] — [email]
> [Name 3] — [email]
>
> Each person gets their own confirmation and calendar invite. To swap a name, use **[Manage your group]**.
>
> [Host name]

**To each attendee:** use the conference template above, with one added line under the greeting: "[Booker name] registered you for this event."

That line prevents the "why did I get this?" reply.

## The Confirmation Email Is the Best Moment for the Share Ask

The person reading a confirmation email has just said yes. Their intent is rarely higher than it is in that minute: they have chosen the event, cleared the time and told a form who they are. That makes the confirmation the natural place to invite them to tell their network they are going.

Add one line under the logistics, never above them:

> Going with colleagues in mind? **[Tell your network you're going]** — it takes one click and includes a ready-made LinkedIn post.

The link should open a personalized share page, not a bare event URL they have to copy and caption themselves.

The economics explain why this one line is worth placing well. Attendee-advocacy programs tend to land in a 20-40% share-rate band when the ask is built into the flow rather than left to chance. Each share delivers roughly 50-150 impressions into a professional network that overlaps your audience, and individual LinkedIn posts out-engage brand pages by roughly 8x. Advocacy-driven registrations cost in the $4-18 range against $30-90+ for paid acquisition, and Snoball's published benchmark for share-referred click-to-registration is 31.9%. How that last step is measured is covered in the [share-to-registration glossary entry](https://attendir.com/glossary/share-to-registration).

Keep the ask out of waitlist and approval-pending emails. Asking someone to promote an event they have not yet secured a seat at reads badly.

## Registration-Drive Emails: The Other Meaning

Some people searching for an event registration email template want the opposite message: the email that persuades someone to register in the first place. That is an invitation, and it follows different rules — a reason to attend, social proof, and a single register button. The [event invitation templates](https://attendir.com/blog/event-invitation-templates) cover the copy, and the [event registration strategies guide](https://attendir.com/blog/event-registration-strategies) covers the email sequence and the other channels that drive sign-ups.

Do not reuse invitation copy in the confirmation. The reader is already convinced.

## Subject Line Patterns

Confirmation subject lines need to be recognizable at a glance and searchable later.

- **Status-first:** "You're registered: [Event name], [Date], [City]"
- **Time-first** for virtual: "Confirmed: [Session title], [Day] at 2pm ET"
- **Pending:** "We received your request — [Event name]"
- **Meeting:** "Confirmed: [Rep] + [Company] at [Show], Booth [number]"
- **Waitlist:** "You're on the waitlist for [Event name]"

Put the event name in every subject line, since that is what people search for on event day. Skip emoji and anything that sounds like a promotion.

## Deliverability and Technical Basics

A perfect template does nothing if it lands in spam or arrives an hour late.

- **Send instantly from a transactional sender.** Route confirmations through your transactional email service, not the marketing platform's batch queue. The registrant is watching their inbox right now.
- **Authenticate the sending domain** with SPF, DKIM and DMARC.
- **Include a plain-text version.** Some clients and security filters prefer it, and it guarantees the logistics are readable everywhere.
- **Avoid image-only emails.** Put the time, place and links in live text. Blocked images should never hide the join link.
- **Use a monitored reply-to.** Registrants reply to confirmations with questions.
- **Test the calendar files.** Open the .ics in Outlook and Apple Calendar and the Google link in a browser before launch, and check the time zone survives.

## Frequently Asked Questions

### What should an event registration confirmation email include?

It should include the event name, the date and time with the time zone written out, the venue address or personal join link, add-to-calendar links for Google, Outlook and .ics, what happens next, a link to cancel or transfer the registration, and a real contact. Put the time and access details in the first screen and keep anything promotional below them.

### When should you send an event confirmation email?

Send it immediately after registration, within seconds rather than minutes. The registrant is usually still looking at their inbox for proof the form worked, so a delayed confirmation can lead to duplicate registrations and support emails. Route it through a transactional sender rather than a scheduled marketing send.

### What is a good subject line for a registration confirmation email?

Lead with the status and the event name, then the date: "You're registered: [Event name], [Date], [City]" works for in-person events, and "Confirmed: [Session title], [Day] at 2pm ET" works for webinars. Keep the event name in the subject so the email is easy to find by search on event day.

### Should a confirmation email ask attendees to share the event?

Yes, as one line placed below the logistics, linking to a personalized share page rather than a bare event URL. The registrant has just committed, which makes the confirmation the highest-intent moment in the sequence. Leave the ask out of waitlist and approval-pending emails, where the person does not yet have a seat.

### What is the difference between a registration email and an invitation email?

An invitation persuades someone to register and ends at the register button, while a registration confirmation email follows the sign-up and gives the attendee everything needed to show up. The invitation sells; the confirmation reassures and informs. Reusing invitation copy in a confirmation wastes the reader's attention on someone already convinced.

If you run multi-track B2B conferences and want every confirmation to carry a tracked share page, see how Attendir works for [B2B conferences](https://attendir.com/use-cases/b2b-conferences).