> For the complete documentation index, see [llms.txt](https://help.dscout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.dscout.com/private-panels/emailing-and-sms/email-templates.md).

# Email templates

Email templates are handy for creating and re-using common things you'd want to send to your panelists.

{% stepper %}
{% step %}
To create a new Email Template, go to **Settings Email Templates**.
{% endstep %}

{% step %}
Then click **New Email Template**, and enter a **Title** and **Subject**.
{% endstep %}

{% step %}
Make sure to select either [WYSIWYG](#wysiwyg-templates) or [HTML](#html-templates) for the **Template Type** (More information on these types below)
{% endstep %}

{% step %}
From there, you'll be able to update the email body, which automatically saves.
{% endstep %}

{% step %}
In the future, when you want to use this template, follow [this guide](/private-panels/studies/email-editor.md).

![](https://content.gitbook.com/content/T7fhyut5rrQHwe5QRGot/blobs/BfNXBfcIxej74A904xWk/37914096181524)
{% endstep %}
{% endstepper %}

## WYSIWYG Templates

WYSIWYG templates are exactly that, "what you see is what you get". The text, buttons, and images that you add will be shown to the recipient exactly as you have added them.

![](https://content.gitbook.com/content/T7fhyut5rrQHwe5QRGot/blobs/yeS1jq87xSKi6itokwHF/37062217358228)

The **+** sign will allow text, buttons, and images to be added to the email template.

![](https://content.gitbook.com/content/T7fhyut5rrQHwe5QRGot/blobs/GF2PntN6KbEWJamH4ccz/37062217359636)

## HTML Templates

Choosing the HTML template type allows a user to write HTML that will be translated to human readable text, buttons, and images. This gives you more control over the style properties as well, including button color.

Private Panels comes with a right side rendered screen that shows a preview of what the HTML will display to the recipient. See example below

![](https://content.gitbook.com/content/T7fhyut5rrQHwe5QRGot/blobs/SbInOkIANUDmL9ibwtsp/37062211336852)

Additionally, the GDPR "unsubscribe link" and "right to be forgotten" can be added to the HTML form by using the Merge Tag menu, or manually writing **{unsubscribe\_link}**.

![](https://content.gitbook.com/content/T7fhyut5rrQHwe5QRGot/blobs/Ih1qLFDqt502TUryAUNu/37062211338132)

{% hint style="info" %}
Private Panels was previously managed outside of Dscout, so you may see a different logo and URL in some places. If you have any questions, contact <support@dscout.com>.
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.dscout.com/private-panels/emailing-and-sms/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 `automate deployments from our CI pipeline` 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.