> For the complete documentation index, see [llms.txt](https://help.getmobly.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.getmobly.com/help-center/host/sending-emails.md).

# Sending emails

Sending is the runtime counterpart to building email templates. You build the design and metadata once in [Email templates](/help-center/host/creating-email-templates.md), then this is where you actually push them — to your full guest list, a filtered segment, or a single person.

Common patterns:

* **Initial invitation blast** — your invitation template goes out to everyone who hasn't been invited yet
* **Reminder to a subset** — your reminder template goes only to guests who confirmed but haven't downloaded their ticket
* **Resend to a specific guest** — they lost their confirmation, send them another copy
* **Update notice** — venue changed, blast everyone with a notice

You access email sending from the left menu: **Mailing**.

## Bulk mailing — send to many guests at once

This is the primary send surface. It works for everything from "send to everyone" to "send to a single specific person" via the Custom condition filter.

1. Go to **Mailing** in the left menu.
2. Click **New mailing** in the upper right corner.
3. Choose the template you want to send. A summary appears.
4. In the right pane, select your recipients. You have two options:
   * **Pre-defined options** — quick filters like "all confirmed guests," "all guests who haven't responded," etc.
   * **Custom condition** — precise targeting. Examples: "all confirmed guests in Group A," "all guests where their email is X," "everyone who registered after a specific date."
5. (Optional) Click **Edit** to adjust the subject, sender's name, or reply-to email for this send only — without changing the underlying template.
6. Click send.

> The **Custom condition** option is what turns this into a flexible resend tool. To resend to a single registrant, set a condition that matches just them (e.g., `Email → equals → name@company.com`) — works the same as sending to a thousand.

## Sending to a single guest from their record

If your Host setup includes a **Guests** tab in the left menu, you can send directly from a guest's record:

1. Go to **Guests** in the left menu.
2. Click the specific guest you want to email.
3. Click the **Send email** button.
4. Pick the template, then **Send**.

> Some Mobly Host orgs don't expose the Guests tab (the guest list is replaced by Mobly's leads — see the [Host overview](/help-center/host/host.md)). If you don't see a Guests tab in your Host left menu, use the Bulk mailing path with a Custom condition matching just that one guest — same result.

## What gets sent vs. what's stored

The send action uses the template's current state at the moment of send:

* **Template content and design** — whatever's in the Builder right now goes out
* **Subject / sender / reply-to** — pulled from template settings, optionally overridden per-send
* **Attachments** (PDF ticket with QR, ICS calendar file, custom files) — included if configured on the template
* **Visibility conditions on sections** — applied per-recipient, so the same template can render different content to different guests

Once a send goes out, the recipient's record in Host shows that email in their history. If you're using Mobly's CRM-side sync, the engagement also flows there (see the [CRM comparison](/help-center/integrations/crm/comparison.md#activity-logging)).

## Related articles

* [Creating email templates](/help-center/host/creating-email-templates.md) — designing the templates you'll send
* [Preparing the event page](/help-center/host/preparing-the-event-page.md) — the registration page guests land on from your invitation
* [Getting started with Host](/help-center/host/getting-started-with-host.md) — launching Host for an event


---

# 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://help.getmobly.com/help-center/host/sending-emails.md?ask=<question>&goal=<endgoal>
```

`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.