Learn which emails attach to an event, when automated sends schedule, how HQ templates differ from the event Emails tab, and what dropped status labels mean.
After you publish an event, Bevy can attach two kinds of marketing email to it: newsletters you write, and automated emails HQ already configured. System emails such as ticket confirmations are separate and do not appear on the event Emails tab.
Use this article to understand what those emails are and why a send might show as dropped. For card-by-card preview, edit, reschedule, and cancel steps on one event, see Use the event Emails tab.
Note: Choosing among event emails, social share, homepage callout, calendar invites, and cohosting? Start with Promote an event to pick the right surface — then return here for the full steps.
Types of event emails
| Type | What it is | Who edits the content | Where organizers manage sends |
|---|---|---|---|
| Newsletter | A one-time email an organizer writes for an event audience (announce, remind, thank attendees) | Chapter organizers (subject and body) | Chapter Dashboard → Emails to create; event Emails tab to preview, edit, schedule, or cancel that send. See Send a chapter newsletter and Use the event Emails tab. |
| Automated | A marketing email HQ configured with a trigger (for example a reminder before Event Start) | HQ in Admin Dashboard → Emails → Automated emails. Organizers do not edit the template. | Event or chapter Emails list: preview, reschedule, or cancel a scheduled send. See Automated emails. |
| System | Transactional messages such as ticket confirmations | HQ / Bevy (system templates) | Not listed on the event Emails tab. To resend a ticket email for one registrant, use Resend event email on Registrations. |
Note: For a community-wide comparison of newsletters, automated emails, and system emails, see Understanding Bevy email types.
When automated emails schedule
When HQ enables an automated template that uses an event trigger (for example Event Start or Event End), Bevy schedules a send for qualifying published events. A common example is a reminder a set time before the event starts.
- Enabling a template can schedule it for qualifying events without republishing each event. Bevy still checks at send time.
- Unpublished events do not get a non-canceled automated send.
- Hidden events stay silent unless Allow automated emails is on for that event (see below).
If you expected an automated email on the event Emails tab and it is missing:
- Ask your administrator to confirm the automated email is enabled in Admin Dashboard → Emails → Automated emails.
- Confirm the event is published (and not hidden without Allow automated emails).
- On some communities, the event list shows newsletters only — ask your administrator if automated rows are available for your chapter.
Tip: Post-event survey sends are configured with the survey, not only as a generic automated template. See Configure a post event survey email.
Templates vs the Emails tab
Organizers manage sends for one event on the event Emails tab. HQ manages automated templates in the Admin Dashboard.
| Task | HQ / Admin Dashboard | Organizer / Event Emails tab |
|---|---|---|
| Create or edit an automated template (subject, body, audience, trigger, enable) | Yes — Admin Dashboard → Emails → Automated emails | No |
| Write a newsletter for an event | Not required | Yes — Chapter Dashboard → Emails → New email (not from the event tab) |
| Preview a scheduled send for one event | — | Yes — event Emails tab |
| Reschedule or cancel a scheduled automated send | — | Yes — when the action is available on the card |
| Edit, schedule, send now, or cancel a newsletter | — | Yes — when permissions allow |
Step-by-step actions on the tab (including the Delete email confirmation when you cancel) are in Use the event Emails tab. Chapter-wide create and filter steps are in Use the chapter Emails page.
Allow automated emails on hidden events
By default, hidden events do not send automated emails. To allow them for a specific event:
- Open the event in the Chapter Dashboard.
- Select Hide this event on public pages (or the equivalent hidden-event control your community shows).
- Select Allow automated emails.
- Save or publish the event.
For the rest of hidden-event visibility, see Create and configure events.
What a dropped email means
A status that starts with dropped means Bevy did not send that scheduled email. The label after the dash explains why. Exact wording can vary slightly by community.
| Status label | Typical meaning |
|---|---|
| dropped - event not live | The event was canceled or otherwise not live before the send (for example a post-event email for an event that never went live). |
| dropped - event is hidden | The event is hidden and Allow automated emails was not selected (common for test events). |
| dropped - bad schedule | The publish time conflicted with the template’s trigger window (for example a 48-hour reminder for an event published with a start time today). |
| dropped - task timed out | The send could not finish because required event details for that email were missing or the task timed out. |
| dropped - empty link | The rendered message had an empty link — often a missing survey URL in a post-event survey template, or an empty post-event survey on the event. |
| dropped - no content | The email rendered with no usable content for the language being sent. |
| dropped - departed | The intended recipient was no longer associated with the event or organization when the email triggered. |
| dropped - event invalid | Event data was invalid or incomplete, so Bevy could not generate or send the email. |
| dropped - no recipients | There were no valid recipients (for example everyone unsubscribed, bounced, or otherwise could not receive the message). |
| dropped - order canceled | The order tied to that email was canceled, so the related message did not send. |
Note: On cohosted events you may also see cohosting-related dropped labels (for example that a chapter is no longer cohosting, or that cohosting emails are not enabled). Those apply to cohost-specific automated sends, not every event email.
Dropped status explains why a send did not go out. It does not delete the event or remove attendees. To stop a send that is still scheduled, cancel it from the event Emails tab.