> ## Documentation Index
> Fetch the complete documentation index at: https://docs.os.default.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Messages

> Reusable email, SMS, and Slack message templates for meeting notifications and reminders, plus email styling.

Messages is your workspace's library of meeting message templates. A template defines what
gets sent (email, SMS, or Slack), to whom, and when; [events](/events) then assign templates
to their triggers and reminders. Because templates are reusable, you write a booking
confirmation once and every event that assigns it stays consistent.

<Note>
  Open the **Scheduling** app from the **Dock**, then use the **Messages** group in the
  Scheduling sidebar. Messages is admin-only; members won't see the group. The tabs are
  **All messages**, **Meeting notifications**, **Meeting reminders**, and
  **Email templates**.
</Note>

There are two kinds of template:

| Kind             | When it sends                                                       | Example                                    |
| ---------------- | ------------------------------------------------------------------- | ------------------------------------------ |
| **Notification** | When something happens: booking, cancellation, reschedule, no-show. | A booking confirmation email to the guest. |
| **Reminder**     | Before or after a meeting, at a scheduled time.                     | An SMS to the guest 15 minutes before.     |

## The library

**All messages** lists every template; **Meeting notifications** and **Meeting reminders**
scope the list by kind. Switch between grid and list view, search with **Find messages**,
and filter by recipient (**All recipients**, **Guest**, **Host**) and status
(**All status**, **Active**, **Inactive**).

Each template shows its kind (**Notification** or **Reminder**), its recipient (**Guest**
or **Host**), icons for its enabled channels, when it was last modified, and an active
switch. A template's row menu has **Edit**, **Duplicate**, and **Delete**. Deleting warns
you that events using the template fall back to org defaults.

## Create a message

Select **New message**, then answer the dialog's prompts:

1. **Who is this for?** Choose **Guest** (the person who booked) or **Host** (the meeting
   host).
2. **What kind of message?** Choose **Notification** or **Reminder**.
3. For a notification, **What's the trigger?** Choose **Meeting booked**,
   **Meeting cancelled**, **Meeting rescheduled**, or **No-show meeting**.

Select **Create** to open the new template in the editor.

## Edit a template

The editor shows the template's settings on the left and a live **Preview** on the right.
Name the template in the header (for example `Booking confirmation`), and use the **Active**
switch to control whether events can send it.

A template can send on up to three channels, each with its own tab: **Email**, **SMS**, and
**Slack**. Channels you haven't enabled show an **Add** pill; Slack is available only on
host templates, since it messages your team, not guests.

* **Email**: write the **Subject** and **Body**, pick a **Format** (**Branded HTML**, styled
  with your organization branding, or **Plain text**), and control delivery with
  **Reply to settings** (add **CC recipients**) and **Email sender** (choose
  **Use workspace default**, **Send from meeting host's inbox**, or
  **Send using custom email**; sending from a host inbox or a custom address requires a
  verified sending domain).
* **SMS**: write the **Message** sent when the recipient has a phone number.
* **Slack**: write the **Message** posted to the host.

Each channel also has a **Fallback message** for when personalization can't be rendered.

For reminders, set **When to send**: pick **Before** or **After** the meeting and a preset
or **Custom** amount of time. Events can override this timing per event.

### Variables

Insert variables to personalize a message: guest fields, host fields, meeting fields, and
action links (**Meeting link**, **Reschedule link**, **Cancel link**). For example,
`Hi {{ guest.first_name }}, your meeting is confirmed.`

The **Variables in use** panel lists every variable in the current channel and lets you set
ordered fallback attributes, so a blank variable at send time falls back to the next
attribute in its chain instead of sending an empty gap.

## Email templates

The **Email templates** tab controls how every templated email looks, workspace-wide. The
**Branding** controls set the **Background Color**, **Text Color**, and **Link Color**, plus
the **Button Color** and **Button Text Color**; the logo is synced from your workspace
settings. The **Powered by Default Footer** switch controls the footer line.

Under **Layout**, choose a **Header style** (**Logo**, **Text**, or **Minimal**) and an
**Accent color** (**Blue**, **Green**, **Amber**, **Neutral**, **Purple**, or **Red**) for
the top gradient tint in branded emails.

The **Preview** pane renders a sample meeting confirmation as you edit, with a desktop and
mobile toggle.

## How events use templates

Templates don't send anything on their own. An event's **Messages** section assigns a
template to each notification trigger and reminder rule; see
[Events: Messages](/events#messages). If an event doesn't assign a template for a trigger,
Default's org defaults apply.