Introduction to Email Documentation

Email in BackOps is designed to keep event communication centralized instead of buried across personal inboxes and disconnected threads. Every event has its own dedicated email address, so communication relevant to that event can be collected in one place and shared with the team members who have access.

How Event Email Works Today

At the current stage, event email works as a shared intake channel.

Copy your event email address

Open your event and copy that event's dedicated BackOps email address.

CC the event on threads you already manage

Add the event email address to the Cc line on any email thread you are part of and want captured inside BackOps.

View those emails inside the event

Emails sent on those threads appear in the event inbox so your team can review communication history in one shared place.

This makes it easier to keep vendor, partner, and production communication visible to the right people without forwarding chains or chasing context.

Where Email Is Going

Event email is an early stage of a larger communications direction in BackOps.

The long-term goal is to make BackOps more than a place where event emails are collected. The vision is a place where communications can be actively managed end to end. That future direction includes:

Managing event inbox activity directly in BackOps
Sending mass communication from BackOps
Using event data you have already collected to target and personalize communication workflows

As this area evolves, the focus remains the same: keep event communication centralized, collaborative, and connected to the rest of your event operations.