Customizing Email Templates

Hi.Events sends automated emails to attendees at key moments — order confirmations, ticket deliveries, and more. You can customize these to match your brand and include event-specific details.

How to Get There

Email templates can be customized at two levels:

  • Organizer level — Organizer Settings → Email Templates (applies to all events by default)
  • Event level — Event Settings → Email & Templates (overrides organizer defaults for this event)

Before you can edit templates you must verify your account email and connect a Stripe account — a Connect Stripe button is shown inline if you haven’t.

Available Templates

  • Order Confirmation — sent immediately after a successful purchase
  • Attendee Ticket — the email containing the ticket with QR code
  • Date Cancellation — sent to attendees when a date of a recurring event is cancelled

Date Cancellation is always available at organizer level, but at event level it only appears for recurring events.

Editing a Template

  1. Select the template you want to customize
  2. Set the Subject (required)
  3. Edit the Email Body using the rich text editor
  4. Insert tokens for dynamic data using the { } button in the toolbar — for example {{ event.title }}
  5. Set the Call-to-Action Button label (required) — the button’s link is set automatically
  6. Use the Preview tab to see how the email will look
  7. Leave Template Active on so the template is used
  8. Save your changes

The token menu in the editor lists every available token with a description and an example value — always insert tokens from that menu. Malformed token syntax will show an error when you save, but a well-formed token that isn’t on the list saves without complaint and simply renders as blank in the sent email, so double-check token names against the menu.

Removing a Customization

Each template you save is an override. Deleting it reverts that email to the organizer template (at event level) or to the Hi.Events default.

Tips

  • Keep emails concise — attendees scan for essential information
  • Always preview before saving to catch formatting issues
  • Event-level templates override organizer-level defaults for that specific event