Customize transactional templates Bevy sends when a platform action happens. See who receives each type, then edit the template in Admin Dashboard Emails.
Before you start
System emails are transactional. Bevy sends them because of a platform action, such as a ticket purchase or a password reset. They are not newsletters and they are not the marketing templates on Automated emails.
HQ customizes them at Admin Dashboard → Emails → System emails. They do not appear on the chapter Emails list. Recipients usually cannot unsubscribe.
To tell system mail apart from chapter, global, and automated mail, see Understanding Bevy email types.
Clearing Use customized email template sends the default template again. It does not turn the type off. To stop a system email entirely, contact Support.
Edit a system email
- In the Admin Dashboard, open Emails.
- Open the System emails tab.
- Select a type.
- Edit the subject or body.
- Select Use customized email template to send your version. Clear it to return to the default template.
- Click Save.
The list can show Title, Audience, Trigger set, Status, and Translations. Your community only lists types that exist for that tenant. Sponsor invoice types appear only when sponsors are enabled.
Dynamic tags
Use dynamic tags to insert content that Bevy fills in for that send, such as an event title. In the subject or body, type an asterisk (*) and start typing the tag name. The list is different for each system email.
These are content-builder mentions. They are not newsletter merge tags such as *|first_name|*.
Attendee and account emails
These types go to the person the action is about, not the chapter team.
| Type | When Bevy sends it | Who receives it |
|---|---|---|
| Ticket Confirmation | Someone RSVPs or buys a ticket. | The purchaser on the order. |
| Manually Added Attendee Notification | An organizer adds an attendee with Add attendee. | The attendee who was added. |
| Order Refund Confirmation | An order is refunded. | The purchaser on the order. |
| Sign up Welcome | Someone creates an account. | The new account holder. |
| Magic Link Login Requested | Someone requests a magic-link login. | That user. |
| User Email Updated | Someone changes their email address. | That user. |
| Password Reset Requested | Someone requests a password reset. | That user. |
Ticket Confirmation can include a calendar option. For how attendees add an event to a calendar, see "Event Add to Calendar" Feature.
Sign up Welcome is the account-creation message. A chapter-join welcome is an automated email, not this type.
Chapter and HQ notification emails
These types notify chapter team or HQ. Recipients still get them if they are not chapter members of a marketing list. The action still has to occur. If you do not use the blog or sponsor invoicing, those emails do not send.
| Type | When Bevy sends it | Who receives it |
|---|---|---|
| Blogpost Approved | An editor approves a blog post. | The blog post author. |
| Blogpost Rejected | An editor rejects a blog post. | The blog post author. |
| Blogpost Submitted | A blog post is submitted for review. | Blog editors. |
| Chapter Contact Message | Someone uses Contact, Contact us, or Contact host. | Chapter team members who can view ticket orders. |
| Event Published | An event is published and live. | Chapter team members who can view the event. |
| Event Wrap Up | The event ends. | Chapter team members who can view the event. |
| Order Notification | An RSVP or ticket order is completed. | Chapter team members who can view ticket orders. |
| Sponsor Invoice Published | A sponsorship invoice is published. | The payment lead and sponsorship recipients. Appears when sponsors are on. |
| Sponsor Invoice Paid | A sponsorship invoice is paid. | The payment lead and sponsorship recipients. Appears when sponsors are on. |
Event Wrap Up uses the same audience as Event Published: chapter team members who can view the event. That typically includes organizers, team members, and check-in staff with that permission. It is not limited to people who can publish events.
Other types that can appear
The System emails list can include additional shipped type names. Keep the label you see in the product. Chapter Group Signup is the historical name; do not rename it to “chapter signup” in the UI.
| Type | When Bevy sends it | Who receives it |
|---|---|---|
| Chapter Group Signup | Historical type name that can still appear on the list. Use this label as shown. Do not rewrite it as group in new copy. | Only if this template exists on your community. |
| Chapter Speaker Suggestion | Someone submits a speaker suggestion. | The HQ speaker-suggestion list for your community. |
| Chapter Sponsor Application | Someone submits a become-a-sponsor form. | The HQ sponsor-application list for your community. |
| Feature Attendee Request Notification | Someone asks to be a featured attendee. | Chapter team members who can feature attendees. |
| Ticket Release | A waitlisted person is offered a ticket. | The waitlisted person. |
| Event Thank You | Shipped type name. May appear if the template exists. | Only if this template exists on your community. |
| Event Coming Up Reminder | Shipped type name. Event reminders that HQ configures as automated emails are not this list. | Only if this template exists on your community. |
| Event Coming Up Reminder Without Ticket | Shipped type name. | Only if this template exists on your community. |
| Event Two Week Reminder | Shipped type name. | Only if this template exists on your community. |
| Event Published Announcement | Shipped type name. Separate from Event Published. | Only if this template exists on your community. |
| Event Invoice Submitted | Shipped type name. | Only if this template exists on your community. |
| Comment Notification | Shipped type name. | Only if this template exists on your community. |
| Form Response | Shipped type name. | Only if this template exists on your community. |
| Form Response Copies | Shipped type name. | Only if this template exists on your community. |
Meetup components
Some event templates include Meetup components. Bevy shows or hides them from the event Meetup URL, not from a separate toggle in the email editor.
- If the event has a Meetup URL, Bevy shows the component ruled Show when Event Meetup URL is enabled.
- If it does not, Bevy shows the component ruled Hide when Event Meetup URL is enabled.
Include a QR code on Ticket Confirmation
Support can enable a QR code on ticket emails and PDFs for ticketed in-person or hybrid events. Contact Support to turn this on. If the code is hard to scan in the email body, use the attached PDF.