System Emails

This article will explain what system emails are used for and how to configure them.

System Emails

System Emails are templated and created by Bevy. The copy can be edited in the Admin Dashboard.

System emails are considered transactional emails, not marketing emails. Event registrants will receive these emails regardless of whether they are a chapter member and/or subscribed. 

System emails are triggered when a specific action occurs and cannot be turned off within the system.This way you can ensure that all registered event guests receive important information, like a ticket confirmation. However, if the trigger is not in use the emails will not send. For example, if you don’t use sponsor invoicing or the blog on Bevy, those emails will not send.

As Admins/HQ, if you want to receive System Emails (e.g. Event Published), email us at help@bevy.com.

Configuring System Emails

To configure System Emails, follow the steps below:

  1. Select Emails from the left sidebar of the Admin Dashboard
  2. Select the tab for System Emails
  3. Click on any System Email you’d like to configure. The copy and structure of the email can be edited from this page.  
  4. If you make changes to the copy, scroll to the bottom of the email and click the checkbox for System Email Enabled
  5. Click Save and OK in the confirmation modal
 Note: System emails will send regardless of whether System Email Enabled is checked or not. This ensures vital information is sent to your community. If you make edits to the system emails, make sure you check the box and save.

Standard System Emails

  • Blog Post Approved
    • Blog Post was approved to go live
    • Audience: Writer
  • Blog Post Rejected
    • Blog Post rejected and returned for feedback
    • Audience: Writer
  • Blog Post Submitted
    • A Blog post was submitted and needs Admin approval
    • Audience: Super Users, Admin Users, Editors 
  • Chapter Contact Message
    • An incoming query from a chapter member is received
    • Audience: Team members of chapter (all roles)
  • Event Published
    • Event is published and live for attendees to view
    • Audience: Team members of chapter (all roles)
  • Event Wrap Up
    • Reminder to Wrap Up event with videos, images, RSVP lists, and more
    • Audience:  Chapter team members with permissions to publish events
  • Order Notification
    • New ticket purchase was made for an event
    • Audience: Chapter team members with permissions to publish events
  • Order Refund Confirmation
    • An attendee is provided the order summary for their ticket refund
    • Audience: Chapter team members with permissions to publish events
  • Signup Welcome
    • A 'welcome to the community' email
    • Audience: new member of specific chapter
  • Sponsor Invoice Paid
    • Notification when the invoice for designated amount is paid by the sponsor
    • Audience: Chapter team members with permissions to publish events
  • Sponsor Invoice Published
    • Invoice for designated amount is attached and ready to send to Sponsor
    • Audience: Chapter team members with permissions to publish events
  • Ticket Confirmation
    • Notification when an individual has RSVP'd or purchased a ticket for an event
    • Audience: Attendee that purchased the ticket (not all ticket holder, only the purchaser of the tickets if more than 1)

Frequently Asked Questions

What audience receives the event wrap up system email?

The wrap up system email is sent to all chapter team roles who have permission to view events. Typically this includes any chapter organizers, team members, and check-in staff.

Still need help? Contact Us Contact Us