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

# Custom Email Templates

With custom email templates you can create a list of prewritten email content that can be used to replace the default email template when sending emails from the system.

For example, you may have a standard sales email that you would like all users to use when sending introductory emails to clients.&#x20;

{% hint style="warning" %}
The Admin Area is only accessible if your user account has been granted the Administrator permission.
{% endhint %}

To get started, navigate to **Admin->Settings** then select the **Custom** Tab.

<figure><img src="/files/W7q1KSkufS1aWVaMja7F" alt=""><figcaption><p>Admin Settings Custom Email Templates</p></figcaption></figure>

Press the![](/files/Djt8J56TdNIvrUpAeotH)button to display the custom email template dialog.

<figure><img src="/files/bf6Il24Hlvw0P7IZkfdY" alt=""><figcaption><p>Add Email Template Dialog</p></figcaption></figure>

Compose the email then press the![](/files/dzNgk1a9qsgnDYjxIfUt)button.

{% hint style="info" %}
The items surrounded with **\[%.....%]** are place holders, also known as merge fields.&#x20;

These items will be replaced with your agency and users information when sending the email.
{% endhint %}

### Place Holders

You can use the following place holders in your email content.

| Placeholder                 | Description                                    |
| --------------------------- | ---------------------------------------------- |
| \[%FULL\_NAME%]             | Full name of the email recipient               |
| \[%FIRST\_NAME%]            | First name of the email recipient              |
| \[%USER\_EMAIL%]            | The user's email address                       |
| \[%USER\_NAME%]             | The full name of the user sending the email    |
| \[%USER\_JOB\_TITLE%]       | The job title of the user sending the email    |
| \[%USER\_PHONE%]            | The phone number of the user sending the email |
| \[%AGENCY\_NAME%]           | Your agency company name.                      |
| \[%AGENCY\_PHONE%]          | Your agency main phone number                  |
| \[%AGENCY\_LOGO%]           | Your agency logo image                         |
| \[%USER\_EMAIL\_SIGNATURE%] | The users email signature                      |

### Usage

You can select an email template to use when sending an email from the system.

<figure><img src="/files/wssjDLiQqr4OaQNSpVNr" alt=""><figcaption><p>Send Email Dialog - Use Custom Template</p></figcaption></figure>

Press the ![](/files/hCEEYbEU3ZzrbaynNgnr)to choose a template.

<figure><img src="/files/o8i7n7DILplQrFQclzsZ" alt=""><figcaption><p>Select Custom Email Template Dialog</p></figcaption></figure>


---

# 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.kisrec.com/administration/settings/email-templates/custom-email-templates.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.
