Every registration on your event can be emailed from the same place. Whether you're messaging three people or three hundred, you'll end up in the same composer, choosing from the same templates and the same merge fields. This article walks through both routes in, group and individual, plus what happens after you hit send.

Choose Who Gets the Email

Start on your event's Registrations tab. Tick the checkbox beside any row and a bulk selection bar switches on above the list, showing how many you've selected out of the total. That bar is where Email Group lives, alongside Change Status and Export view, so a selection can go three different directions from the same spot.

Click Email Group and the composer opens as a panel down the right-hand side. To shows the number of recipients you selected, and From is your account's sending address, fixed here and set elsewhere (see "Express: Understanding the Emails Tab" for sender identity). Across the top sits a strip of layouts. Choose one of these before you write a word, because switching layouts after you've started throws your draft away.

Choose an Email Template

The layouts you see first are system templates: Minimal, Info, Action, VIP, Standard, and a few more, each a different tone rather than a different feature. They're there so you can get a message out quickly without building one from scratch.

Click Browse All and the full Email Template Gallery opens. Starter is where those system templates live. Saved is your account's own library, the templates you or your team have built and reused across events. Recent lists whatever you've used most recently, so you're not hunting for the same template twice.

If you're writing something worth reusing, click Save as Template in the top right of the composer.

Give it a name and an optional description, the description is for the colleague who has to pick the right template out of a long list later. Then choose who can see it: Just me keeps it private, Shared with team puts it in the library everyone on your account can reuse.

One thing worth remembering here: the template isn't saved until you click Save. Close the composer or send the email first, and whatever you typed is gone.

Write the Message

Selecting a template writes the message for you: a subject line and a few short paragraphs, with merge fields sitting in double curly braces wherever a piece of recipient data belongs. Edit that starting point based on who you're writing to and why. The Header/Hero toggle beneath the subject line belongs to the template rather than to anything you've written, so turn it off when you want a plainer, more personal-looking note and leave it on for the fully branded version.

Click More fields to see everything Express can drop into a message for you. It's organized into three groups: Personal details like first name, last name and organization, Event details like the event name and its dates, and Registration details, which is where Registration Code and Registration Link live. Click any chip and it drops that token wherever your cursor is sitting.

Below the message, a CTA Button toggle adds a call-to-action button to the email. Turn it on and two fields appear: a button label and the link behind it, which can be a plain URL or the {{Registration Link}} token.

Underneath that, the Event Details Block drops your event's date, time and location straight into the email, pulled from the event itself so you never type them in by hand. It only shows up on templates built to carry it. Switch to a plainer layout like Minimal and the toggle disappears entirely, which is why the template gallery lists each template's included blocks before you commit to one.

Before you send, click Preview at the top of the composer to see what the message looks like as an actual registrant, tokens and all resolved into real names and dates. You can also send a test copy to your own inbox with Send Test to Me, useful for a final look before it goes to a real list. When everything checks out, click Send.

Email One Person

Sometimes one message to one person is all you need, and Express handles that the same way. Open that person's record from the registration list and go to the Communicate tab.

The communication log starts empty: Start of History, then No Communications Sent, with a note that emails to this attendee will appear here automatically. You don't add anything to this log by hand. It fills itself in only once mail actually goes out, which is what makes it trustworthy. To write to this person, click Compose Email.

It's the same composer you've already used: the same layouts, the same merge fields, the same preview. This time, though, no layout is selected, and that's perfectly fine. A plain note with no header block and no button is often the right call when you're writing to one person about one detail. Use the {{First Name}} token in the greeting anyway, even for a single recipient, so the same message stays reusable the next time you need it.

Once you send, the composer closes, and the Communicate tab might still read No Communications Sent. Don't read that as a failure. That panel doesn't refresh itself after a send, and reloading the page would fill it in, but the record that updates immediately is one tab across: click Timeline instead. It now leads with Email sent, followed by your subject line, and the entry underneath spells out exactly what happened: the subject, the event it belonged to, and how many people received it.

Export Log, in the corner of that same Timeline tab, pulls this whole activity history out as a file, in case you need a record outside Express.

Give a Registrant Their Attendee Hub Link

Back on the Details tab, the bottom of the panel holds the registration code, the date the record was created, and a button most people never press: Generate Attendee Link. It's another way to help someone directly, a private page you can hand to a registrant so they can see and complete their own details.

Once generated, that button becomes an Attendee hub row: the link itself, and three small icons beside it. None of them are labeled, so it's worth learning them before you go clicking around. The first copies the link to your clipboard. The second opens the hub so you can see exactly what the attendee sees. The third, a paper plane, doesn't share the link at all, it resends the confirmation email to this person immediately, with nothing asking you to confirm first. In a row that otherwise revolves entirely around a link, that's an easy one to hit by accident.

Open the link and you'll see the hub exactly as the attendee does. It leads with a welcome banner by name, their organization and title, their status, and their registration code. Below that, Your profile, badged "From your account," carries the message that these details follow the person across every event they attend, so they won't be asked again. Each field carries its own badge: green Confirmed for what's already known, amber Needed with "Not on profile" in place of a value for anything missing. A line underneath lets them expand a couple of fields that aren't required for this particular event. Further down, This event needs your input lists questions specific to this event alone, questions that never travel back to the profile, each one marked with its own requirement badge.

Further down still sits an Event details card, badged "This event," carrying the event name, its dates, and its location. That's the whole idea of the hub captured on one screen: what a person carries with them everywhere, and what this one event still needs from them.