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

# Templates

> Reusable subject and body for manual message sends. Variables resolve per recipient at send time.

Message templates are the saved subjects and bodies that show up in the **Template** picker when you compose a manual message. They live alongside system templates (booking confirmations, receipts, password resets) at **Settings > Communication > Templates**, but the compose picker only surfaces templates with `type = message`.

Use them when you find yourself retyping the same welcome note, class reminder, or promotional blurb every week.

## What a template stores

Each template carries four fields:

* **Name** - shown in the picker and the list.
* **Subject** - used when the template is applied to an email send.
* **Content type** - `html` (rich text) or `text` (plain).
* **Content** - the body, either HTML or plain text.

The list also shows an **Active / Inactive** chip and the created date. Inactive templates stay in the database but disappear from the compose picker.

Templates carry a `type` of `message` (manual sends), `transactional` (system emails like password resets), or `receipt` (invoice receipts). The compose picker only shows `message` templates; the others are picked up by the server when those flows fire.

## Creating a template

From **Settings > Communication > Templates**, click **Add template**. A dialog asks for name, subject, content type, and content. Save and the template becomes available in the compose picker immediately.

To duplicate a template for a variation, hit the **Copy** action on the row. A copy opens in the dialog with `(Copy)` appended to the name; tweak it and save.

## Variables

Write variables as `{{variableName}}`. They are substituted at send time using the recipient's contact record and your organization's settings.

For `message` templates, the server validates that every `{{...}}` token in your subject and body is in the allow-list below. Saving a template with an unknown variable returns an "invalid variable" error. The complete allow-list:

| Variable                | Description                              |
| ----------------------- | ---------------------------------------- |
| `{{contactName}}`       | Recipient's full name                    |
| `{{contactFirstName}}`  | Recipient's first name (for greetings)   |
| `{{contactEmail}}`      | Recipient's email                        |
| `{{organizationName}}`  | Your organization's name                 |
| `{{organizationEmail}}` | Your organization's contact email        |
| `{{organizationPhone}}` | Your organization's phone number         |
| `{{senderName}}`        | The staff member sending the message     |
| `{{subject}}`           | The message subject (handy in body copy) |
| `{{messageDate}}`       | The send date                            |

That's the complete list for manual sends. Booking-specific tokens (`{{entityName}}`, `{{bookingDate}}`, `{{accessPin}}`) and membership-specific tokens (`{{planName}}`, `{{renewalPrice}}`) are only valid on **transactional** templates, where a booking or membership record is bound to the send. For trigger-based messages that use those tokens, see [Automations](/marketing/automations).

## Welcome email example

```text theme={null}
Subject: Welcome to {{organizationName}}!

Hi {{contactFirstName}},

Welcome to {{organizationName}}! We're glad to have you.

If anything comes up, reply here or reach us at {{organizationEmail}}.

Thanks,
The {{organizationName}} team
```

## Using a template

In [compose](/messaging/compose), open the **Template** picker above the subject. Selecting a template fills in both subject and body. You can edit either freely after applying; the saved template is not touched.

The picker only appears for admin and manager roles. Instructor-only inboxes hide it.

## System vs manual templates

If you want to customize the email a member receives when their booking is confirmed, when their membership is about to expire, or when a payment receipt is generated, you are looking for **system templates** (type `transactional` or `receipt`) on the same Templates page. Those expose the booking and membership variable sets, plus a customize-vs-override workflow keyed to a stable `systemTemplateKey`.

The manual `message` templates described above are for the ad-hoc sends you fire from the messaging inbox.

## Related

* [Compose](/messaging/compose) - Where templates are applied to outbound messages.
* [Settings overview](/settings/overview) - System templates for transactional emails live under Settings > Communication.
* [Automations](/marketing/automations) - Automated trigger-based sends with booking and membership variables.