> For the complete documentation index, see [llms.txt](https://docs.podplay.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podplay.app/events/create-an-event/waitlists-and-customer-messaging/email-event-attendees-or-waitlist.md). # Email Event Attendees or Waitlist Customers Use **Email** to send a formatted message (including links and images) to people signed up for an Event or Class, or to Customers on the waitlist. This is helpful for last-minute updates like schedule changes, location reminders, promo codes, or alternative open play options. ### Email Event Attendees * Navigate to the Event you want to message * Open the attendee list (Manage Customers) * Click the **Email** button \[SCREENSHOT NEEDED: Event attendee list view showing the “Email” button] \[] ### Email the Waitlist * Navigate to the Event you want to message * Open the **Waitlist** panel * Click the **Email** button above the waitlist list \[SCREENSHOT NEEDED: Event drawer open to the Waitlist panel with the Email button visible above the waitlist list] \[] **PLEASE NOTE:** The **Email** button only appears when the waitlist is not empty. If it is disabled, none of the waitlisted Customers have an email address on file. ### Choose who receives the email When the email composer opens (**Email to Attendees** or **Email to Waitlist**), the **Edit Recipients** panel is selected by default (everyone with an email address on file). * Click **Edit Recipients** to expand the recipient list * Use **Select all** to quickly include or exclude everyone * Check or uncheck individual recipients as needed \[SCREENSHOT NEEDED: Email composer modal with Edit Recipients panel expanded and a few recipients selected] \[] **PLEASE NOTE:** Only Customers with an email address can be selected. If someone has no email on file, they will be shown but cannot be selected. ### Write the subject and message * Enter a **Subject** * Under **Body**, write your message using the editor tools: * Bold, italic, underline * Font size * Alignment (left/center/right) * Bulleted and numbered lists * Links * Images (uploads JPG/PNG) \[SCREENSHOT NEEDED: Email composer modal showing Subject + Body editor toolbar (including link and image buttons)] \[] ### (Optional) Send a copy to your company email If your location has a company email configured, you’ll see a checkbox: * Leave **BCC company email** enabled to send a copy to your company email address * Turn it off if you do not want a copy sent \[SCREENSHOT NEEDED: “BCC company email” option visible with the company email address shown] \[] ### Send the email * Click **Send** After sending, you’ll see a confirmation showing how many recipients received the email. If some recipients were skipped, it’s usually because they were missing an email address or were excluded from email recipients. ### Tips * If you’re including an image, use a simple JPG or PNG and keep file sizes small (large images can load slowly in email). * Before sending to a large group, double-check the **Edit Recipients** count at the top of the modal. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.podplay.app/events/create-an-event/waitlists-and-customer-messaging/email-event-attendees-or-waitlist.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.