Event Email Templates

Every transactional email your attendees receive starts from a platform-wide default. This screen lets you override the wording and layout of that email for one event only, without touching the default or any other event. Reach it from Event → Manage → Attendee Comms → Email Templates.

What you can do here

• Eleven overridable templates — Booking Confirmed, Pending, Approved, Rejected and Cancelled; Refund Processed; Waitlist Promoted and Waitlist Rejected; Event Reminder (24h); Event Cancelled Notice and Event Updated Notice. Every one of them is a real email that really goes out.
• Visual block designer — header, text, button, image, divider, spacer, alert and footer blocks, dragged into place and edited in a properties panel on the right.
• Variable pills — the placeholders each template can actually fill, listed for that template. They differ per template, because each email knows different things.
• Preview — renders the template as an attendee would actually see it, including the unsaved draft you are looking at.
• Send Test — emails the saved template to your own address, so you can check it in a real inbox.
• Reset — deletes your override for that one template, reverting the event to whatever the platform default currently is.

How to customise a template

1. Open Attendee Comms → Email Templates and pick a template. The index marks the ones you have already customised.
2. The editor loads your existing override if you have one, otherwise a copy of the current default.
3. Add, remove or reorder blocks, and edit each block's content in the properties panel. Insert placeholders from the variable pills rather than typing them.
4. Use Preview to check the result, and Send Test to see it in your own inbox.
5. Save. This creates (or updates) a per-event override; the default and every other event are unaffected.

Good to know

• A placeholder the email cannot fill is refused on save, and the error names the offending ones. This is deliberate: one unfillable placeholder discards the whole design, so the attendee would silently receive the standard body under your subject line — and you would have no way to tell from this screen.
• Certain lines are added back whatever your design says: the payment button on a paid approval, the refund-right sentence when an event changes, and your own note on a refund. Those are obligations, not decoration.
• Resetting a template does not restore what you had before you started editing — it reverts to the default as it stands right now, which can be newer than the version you originally copied.
• An override only ever applies to the one event it was created on. Rolling the same wording out to several events means repeating the edit on each.
• The subject line is a plain string; the body is built from blocks (or raw HTML if you switch out of the block designer), not a WYSIWYG document, so exotic HTML/CSS pasted in from elsewhere will not carry over.

Troubleshooting

• My changes did not show up in the email attendees received — check you edited the right template for the right event; each template and each event is a separate override. If the index marks the template “not in use”, it is an old design carrying a placeholder nothing can fill; open it and save it to see which.
• Save is refused over a placeholder — that placeholder is not one this email knows. Use the variable pills for the template you are editing; the set is not the same for all of them.
• “Can I send the test to a colleague?” — no. The test goes to your own verified address only. The body is your own HTML sent from EventMann’s domain, so accepting any address would make this a way to send arbitrary mail from our reputation.
• Send Test never arrived — it goes to the address on your own account. Check there first, then your sending setup under Sender Identity if you use your own mail server.

Related

• Who your emails are sent from
• Attendee Announcements
• Ticket Design