> For the complete documentation index, see [llms.txt](https://docs.ubiquity.co.nz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ubiquity.co.nz/documentation/how-to/sending-an-email.md).

# Sending an email

Build, test, and send email campaigns with confidence, including key checks before sending.

UbiQuity offers several ways to send email depending on your use case - from one-off campaigns to automated lifecycle emails and transactional messages. All email sending is managed through the Email module.

***

### Before you send

Make sure your account is ready before sending your first email. See First Time Setup for details on configuring your database for email.

***

### Ways to send email

**Mailouts** - The standard way to send a one-off email campaign to contacts in your database. You step through a wizard to build your content, apply filters to target the right contacts, and schedule your send. Best for newsletters, announcements, and regular campaigns.

**Automated Mailouts** - Set up emails that send automatically on a recurring schedule, triggered by date-based conditions in your contact data. Best for lifecycle messaging such as birthday emails, renewal reminders, and welcome programmes.

**Transactional Targeted Mailouts** - Send emails driven by records in a transactional database rather than your contacts database. Best for keeping customers informed as their request or account moves through a process - for example, sending a status update each time a record changes.

**Service Messaging** - Send critical service communications to contacts even if they have opted out of marketing emails. Best for essential notifications such as order confirmations, appointment reminders, and password resets where delivery is required regardless of marketing preferences.

**Advanced Scheduling** - Two additional scheduling options for automated mailouts. Event-based scheduling triggers a send when an API import with a matching tag completes. Personalised email scheduling sends to each contact at a specific time defined in a date and time field in your database.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ubiquity.co.nz/documentation/how-to/sending-an-email.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
