What Should a Conference Registration Confirmation Email Contain?

A conference registration confirmation email should carry six things: who the ticket is for, the ticket itself with a QR code and a number a human can type, the date, venue and door time, a calendar file, what was paid with the VAT line, and a way back to the ticket later. The booker and each delegate need different versions.

What Does a Delegate Need on the Morning of the Conference?

They need to prove who they are and know where to stand, in that order. Everything else in the email is decoration until those two jobs are done. The Event Technology Portal's piece on why confirmation emails matter (4 July 2025) puts the event name, date, time, location and the ticket or QR code at the top, so nobody has to hunt through links while a queue forms behind them. Vendor documentation agrees on the shape: Happenee's help page on its confirmation email describes a PDF ticket with a QR code and a calendar file as the standard payload.

So the first screen of the email, the part visible on a phone before any scrolling, should read like a boarding pass:

• The delegate's name and the pass they hold (delegate, speaker, exhibitor staff).

• The event name, the date, and the time registration opens, which is rarely the time the first session starts.

• The venue with the entrance to use. A big exhibition centre has several doors a long walk apart, so "West entrance, Level 1" beats the venue name alone.

• The QR code, and under it a ticket number that can be read out loud when the screen brightness, the cracked glass or the venue signal lets the code down.

Sessions, parking, dress code and the FAQ link come after that. They matter, but nobody has ever been turned away from a congress for not knowing the dress code.

Who Should Get the Email: The Booker or Each Delegate?

Both, and they should not get the same thing. The person who books five places for the team needs a record of the order. Each of the five people needs their own ticket in their own inbox, because the booker will be on annual leave on the day. It is practically a law of nature.

This is the part of the confirmation that goes wrong most often on group bookings, so it is worth knowing how your platform splits it. On eventcloud, everyone whose details were filled in gets their own confirmation and ticket, and when a ticket asks for attendee details each person needs their own email address. The person who books always gets an order confirmation with the order summary and full totals, listing who each ticket went to. Coming soon: invoices. Need one for a delegate's finance team? Tell us what it has to show.

If your registration covers several audiences, write the confirmation per audience too. A speaker wants the green room and the AV deadline; an exhibitor's stand staff want build-up times. Our conference setup checklist from ticket groups to badges walks through how those groups are set up in the first place, and the confirmation wording follows the same split.

What Do Registration Platforms Put in the Confirmation?

Most carry a ticket and a calendar entry; they differ on money and language. The table below is read from each vendor's own help pages, with the page date where one is shown: EventsAir's confirmation merge docs article, Webex Events' registration messaging article and the Happenee page above. "Not stated" means that page did not say, and nothing more.

EventsAir also lists an Add to Wallet component that saves the QR code to Apple or Google Wallet. Coming soon: Apple and Google Wallet passes on eventcloud. Want them for your delegates? Tell us about the event.

Two things in that table deserve a second look. A calendar file is the simplest guard against a forgotten date, since the event then sits in the delegate's diary with the venue attached, and on eventcloud it also carries each session the delegate holds a place in. And language is more than courtesy: a German delegate at a Frankfurt trade fair who receives an English email with an English PDF will forward it to a colleague to ask what it says. In eventcloud, each ticket group's confirmation can be published in a version per language, and the PDF ticket follows.

What Should the Subject Line and the Sender Say?

Write the subject line for the search box, because that is how the email will be found. Nobody scrolls back three months at the registration desk. They type the event name into their mail app with one thumb while holding a coffee in the other hand.

That makes the rules short. Put the event's name in the subject exactly as it appears on the lanyard and the website, followed by "your ticket" or "your registration". Send it from a name the delegate will recognise, which is the event or the organising body and never "noreply". If your platform lets you send from your own domain, use it: eventcloud gives each organisation one custom sending domain for email, so the confirmation arrives from the association or the organiser the delegate signed up with.

The same test applies to the PDF. A file called "ticket.pdf" is unfindable in a downloads folder by lunchtime; the event name belongs in the first line of the page so a preview shows what it is.

What Happens When a Delegate Cannot Find It?

Plan for it, because someone will arrive with a dead phone or a new work email address. The fix should not involve a member of your team scrolling a spreadsheet. Three things make the missing email a ten-second problem:

• A way for the delegate to fetch the ticket themselves. On eventcloud the attendee portal does this: the delegate signs in with an emailed link, then views and downloads their tickets.

• A number that can be typed. The nine-digit ticket number on every eventcloud ticket can be typed at check-in or at the Badge Kiosk, so a delegate who wrote it on their hand still gets in.

• A help desk away from the main queue, so one lost ticket does not hold up forty found ones.

What Should You Leave Out?

Leave out anything that turns a ticket into a newsletter. The confirmation is a transactional message, and the moment it carries sponsor banners and a "while you are here" survey, the QR code slides off the first screen and the email starts to look like marketing to the delegate and to their spam filter alike.

Be careful with other people's details too. A booker's order confirmation reasonably lists who each ticket went to, since the booker supplied those names. A delegate's own confirmation has no business showing the rest of the party's email addresses. And keep consent questions on the registration form, where the delegate can answer them, instead of burying a marketing opt-in in the footer of a ticket.

How Do You Test It Before Registration Opens?

Book the awkward order yourself. A single ticket to your own address proves almost nothing, because single tickets to the booker's address are the one case every system handles. Run this instead, the week before registration opens:

1. Book three delegate places as one person, with three different email addresses you can read.

2. Check all three inboxes and the booker's. Does each delegate have their own ticket? Does the booker have the totals and the VAT line?

3. Open each email on a phone. Is the QR code on the first screen, and is there a number under it?

4. Open the calendar file. Is the venue in it, and the right time zone?

5. Repeat one booking in each language the event offers, and read the PDF as well as the email.

6. Type one ticket number at your check-in page, then scan one code, on the phone your door staff will use.

The registration page shows how each ticket group gets its own form and confirmation. Fix whatever surprised you, then send the same test order to the colleague least interested in events and ask them where the entrance is.