> For the complete documentation index, see [llms.txt](https://docs.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.distro.so/scheduling/email-templates.md).

# Write and preview meeting messages

Open **Messaging** to create reusable guest or host templates. Templates are attached to events as status messages or reminders.

## Write a template

Choose **Used for** and **Written for** where shown, then write its name, subject and body. Insert supported placeholders using the picker rather than guessing variable names.

Use **Used placeholders** to review the values in your message. Supported fallback expressions let a message use another value when the first is blank. Preview with representative sample values before saving.

## Configure email behavior

Choose Styled or Plain text appearance. Add Cc recipients deliberately; they can receive guest information. For Replies, use **Workspace sender** or **Host replies**.

Host replies changes Reply-To to the host. Distro still sends from the workspace's configured identity. It does not send From a personal host mailbox or offer a per-template custom From address.

Use [Sending domain](/settings/sending-domain.md) and [Workspace branding](/settings/branding.md) for shared delivery and appearance settings.

## Attach and test

Attach the template to the event with the intended audience and timing. Preview Desktop and Mobile layouts. A preview never sends a message.

Make a controlled booking and verify the delivered message when testing live. Slack channels shown as preview-only are not an active delivery channel for that template.

Duplication gives you a separate template to edit. Check where a template is used before deleting or changing shared wording.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.distro.so/scheduling/email-templates.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 `build a script that syncs our docs to a CMS` 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.