> For the complete documentation index, see [llms.txt](https://support.emarketeer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.emarketeer.com/references/references/email/transactional-sendouts.md).
# Transactional sendouts
A transactional send-out delivers a non-marketing email to a contact regardless of their marketing consent. Learn when to use it and how to enable it.
eMarketeer has a built-in consent management system that tracks who you can send marketing emails to. If a contact has withdrawn consent for marketing emails, the email is stopped and not sent.
In some cases the email you want to send is not a marketing email, and you need the contact to receive it regardless of their consent settings. Examples include:
* Important service information to customers
* Confirmation emails
* Delivery of requested information
To send an email that overrides the consent settings, mark the send-out as **Transactional**.
Sending marketing emails without consent is illegal. Use this setting only if the contact truly needs the information or is waiting for it.
## Sending an email manually from a campaign
You see this setting in the **Consent** panel on step 2, **Send Options**, when you address your email. Choose **Transactional**.
## Sending an email in a Journey
When you add the "Send email" step in a Journey, you also have the option to ignore consent by choosing "transactional email".
To decide whether to use transactional email in a Journey, ask yourself: is the contact expecting or waiting for this email? If yes, you can use a transactional email.
Common scenarios:
* Delivery of requested material, for example an e-book download
* Confirmation of a subscription or registration
* Thank-you emails
When not to use a transactional email:
* Drip campaigns that send several emails over time
* Nurture campaigns
* Typical marketing emails that are unsolicited
---
# 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://support.emarketeer.com/references/references/email/transactional-sendouts.md?ask=&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.
