> For the complete documentation index, see [llms.txt](https://docs.yoplanning.support/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yoplanning.support/en/yoplanning-academy/yoplanning-parametrage/communication-client/guide-pour-modifier-les-modeles-demails-sur-yoplanning/detail-des-variables-disponibles-dans-les-emails-clients.md).

# Details of variables available in customer emails

Variables in Yoplanning's email templates allow you to personalize your communications by automatically integrating information specific to each client or reservation. Here is a list of available email templates and the variables you can use for each of them.

### 1. **Reminder Email**

This email is sent to remind the customer of the details of their reservation. Here are the variables available for this type of message:

* **%session\_title%**: The title of the booked session or activity.
* **%start\_date%**: The start date and time of the session.
* **%client\_first\_name%**: The client's first name.
* **%client\_last\_name%**: The client's last name.
* **%location%**: The location of the activity.
* **%meeting\_point%**: The meeting point for the activity.
* **%post\_booking\_message%**: A personalized message added after booking.
* **%staff\_first\_name%**: The first name of the supervising staff member.
* **%staff\_last\_name%**: The last name of the supervising staff member.
* **%staff\_phone\_number%**: The phone number of the supervising staff member.

### 2. **Order Email**

This message is used to confirm an order or reservation. The available variables are:

* **%client\_first\_name%**: The client's first name.
* **%client\_last\_name%**: The client's last name.
* **%post\_booking\_message%**: A personalized message added after booking.

#### 3. **Payment Link and Payment Link Reminder Email**

These emails are sent to allow the customer to pay for a reservation online. The available variables are:

* **%client\_first\_name%**: The client's first name.
* **%client\_last\_name%**: The client's last name.
* **%payment\_link%** : The direct link to make the payment.
* **%amount%**: The amount to pay.

### 4. **Email Post Activity**

This email is sent after the customer has participated in an activity. Available variables are:

* **%client\_first\_name%**: The client's first name.
* **%client\_last\_name%**: The client's last name.
* **%session\_title%**: The title of the session or activity.
* **%start\_date%**: The start date and time of the session.
* **%staff%**: Information on the supervisory staff.

### 5. **Refund Email**

Used to notify the customer of a refund, this email may contain the following variables:

* **%client\_first\_name%**: The client's first name.
* **%client\_last\_name%**: The client's last name.
* **%order\_reference%**: The reference of the refunded order.
* **%amount%**: The amount refunded.

### 6. **Session Email**

This email is sent as a blind carbon copy (BCC) to multiple recipients to share general information about a session. No custom variables are available, as the email is not nominative.

### 7. **Email Fees**

This email is used to inform a client of the fees associated with a service. The available variables are:

* **%client\_first\_name%**: The client's first name.
* **%client\_last\_name%**: The client's last name.
* **%source\_team%**: The name of the team (entity) that charges the fees.

### Simplified Explanation

Each email template can use a set of variables to automatically insert information specific to each client or booking. This allows you to personalize messages without having to manually enter every detail. For example, using `%client_first_name%` will automatically insert the client's first name into the email. Note that some variables are specific to one email type and are not available in others.

**Finally, for emails sent in blind carbon copy (BCC), such as session emails, it is not possible to use custom variables, because these messages are identical for all recipients.**


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.yoplanning.support/en/yoplanning-academy/yoplanning-parametrage/communication-client/guide-pour-modifier-les-modeles-demails-sur-yoplanning/detail-des-variables-disponibles-dans-les-emails-clients.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.