Set up and edit the automated emails that run when chapters collaborate on a cohosted event—Chapter Team Collaboration Notification, New Event Published for collaborating chapter members, and an optional chapter-team post-event survey.
Note: These emails apply only when event cohosting is enabled for your community (Admin Dashboard → Settings → General → Enable event cohosting), the specific event is marked as cohosted (Make this a cohosted event on the event Cohost tab), and cohosted event emails are enabled for your instance. For how host and collaborating chapters work, see About cohosted events. For enablement steps, see Enable event cohosting.
Before you start
A cohosted event is one event owned by a host chapter, with other chapters listed as collaborators. Bevy can send dedicated automated emails when collaboration starts, when collaborating chapter members should learn about a newly published event, and when you want chapter teams to complete a post-event survey.
This article covers those cohosted-specific automated emails. Broader rules for who can email attendees or newsletter subscribers on a cohosted event are in About cohosted events.
| Who receives it | When it sends | |
|---|---|---|
| Chapter Team Collaboration Notification | Chapter team members of chapters added as collaborators (not regular members or attendees) | When a collaborating chapter is added to a cohosted event |
| New Event Published (for collaborating chapters) | Members of the collaborating chapter | After the event is published and that chapter is (or becomes) a collaborator—see timeline below |
| Chapter-team post-event survey (custom automated email) | Event Chapter Teams audience (host and collaborating chapter teams, when cohost filtering applies) | On or after event end, based on the trigger you configure |
Chapter Team Collaboration Notification
Chapter Team Collaboration Notification is an automated email that alerts chapter team members that a cohosted event was added to their chapter. It is not a chapter newsletter, and it is not sent to regular chapter members or event attendees.
- Go to Admin Dashboard → Emails → Automated emails.
- Open Chapter Team Collaboration Notification.
- Edit the subject and body to match your community voice.
- Save your changes. Keep the email enabled so collaboration alerts continue to send.
Add dynamic content
In the automated email editor, type * in an editable field to open mentions (dynamic fields). For this email, useful mentions include:
- Person adding cohost event — the user who added the collaborating chapter(s)
- List of collaborating chapters — chapters included in that collaboration transaction
- Select an edit box in the email content.
- Type
*to open the mentions list. - Start typing Person (or List) and select the matching mention.
Tip: Use the mentions picker (*) in the HQ automated email editor. Do not paste legacy style merge tags (for example *|collaborating_chapter_list|*) into the same procedure—those tags are for a different template path.
If a recipient belongs to several of the collaborating chapters in that transaction, the list of collaborating chapters can include up to 30 chapter names for that person.
New Event Published for collaborating chapters
When cohosted event emails are enabled, Bevy can also schedule the community’s standard New Event Published automated email for each collaborating chapter’s members—not only for the host chapter. Chapter Team Collaboration Notification is separate: it goes to chapter teams when collaboration starts; New Event Published goes to chapter members to announce the event.
When this email can send
For a collaborating chapter to receive New Event Published, all of the following must be true:
- Event cohosting is enabled for the community (Admin Dashboard → Settings → General → Enable event cohosting).
- The event is marked as cohosted (Make this a cohosted event on the event Cohost tab).
- Cohosted event emails are enabled for your instance.
- The event is published (not still a draft) when Bevy evaluates the schedule—or it becomes published after collaborators were already added (see scenarios below).
- The New Event Published automated email itself is enabled in Admin Dashboard → Emails → Automated emails.
How scheduling works for collaborating chapters
Bevy picks the later of (a) the schedule based on the event’s publish timing and (b) the schedule based on when that chapter’s collaboration started. In practice:
| Situation | How New Event Published is scheduled for that collaborating chapter |
|---|---|
| Event is already published, then a chapter is added as a collaborator | Bevy schedules from when collaboration started (so that chapter’s members still get an announcement, even though publish already happened for the host). |
| Collaborators are added while the event is still a draft, then the event is published | Collaborator schedules follow the publish timing—same idea as the host chapter—because collaboration started before publish. |
| A chapter is added as a collaborator on an event that is already completed | Bevy does not schedule New Event Published for that collaborating chapter. |
Example timeline (collaborator added after publish):
| Example time | What happens |
|---|---|
| 10:00 a.m. | An event is created and published in the New York (host) chapter. |
| 11:00 a.m. | The New Event Published email is sent to New York chapter members (host chapter schedule). |
| 1:00 p.m. | Cape Town is added as a collaborating chapter. |
| 2:00 p.m. | The New Event Published email is sent to Cape Town chapter members (collaborator schedule keyed off when they joined, after publish). |
Note: Each chapter’s New Event Published metrics stay with that chapter. The host does not see collaborating chapters’ send metrics for the same event.
Chapter team post-event survey email
You can create a dedicated automated email that sends the post-event team survey link to chapter teams on a cohosted event—including collaborating chapter teams when cohost filtering applies.
Before you create the email
- Confirm Post Event Team survey form is enabled (HQ cannot enable it—contact CSM/Bevy Support if needed).
- Decide whether to keep any older wrap-up automated email that already includes a team survey link. You can leave that older email enabled if you still want a separate wrap-up send, or disable it once this dedicated survey email is ready.
Create the automated email
- Go to Admin Dashboard → Emails → Automated emails.
- Create a new automated email.
- Enter a Title and Subject.
- Set the audience to Event Chapter Teams. That audience includes host and collaborating chapter team members for the event (when cohost filtering applies)—not regular chapter members or attendees.
- Leave the content area empty for now.
- Set the trigger to send on event end, and schedule it after the event ends (immediately or with a delay). Do not schedule it before the event ends.
- Save the email. Saving once before you add rich-text content helps the editor load event-scoped mentions correctly.
Add the survey link and button
- Open the email you just saved.
- Drag a rich text block into the content area.
- Type your message. Use
*to insert mentions such as first name as needed. - Add call-to-action text (for example, Fill in the form).
- Select that call-to-action text.
- From the link/mention options, choose Post event team survey URL (editor label may appear as Post Event Team Survey URL).
- With the text still selected, use the square control in the rich text toolbar to turn the link into a button.
- Select Enable automated email.
- Save.
Tip: Always save the email shell (audience + event-end trigger) before adding rich text. The Post event team survey URL mention is event-scoped and may not appear until after that first save.