> 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/panel-management/panelist-welcome-emails.md).

# Panelist welcome emails

To build a great relationship with your panelists, you can start with an automated **Welcome to the panel** email.

To set up an automated welcome email:

{% stepper %}
{% step %}
Navigate to **Panels All Panels.** If you have multiple panels, select which panel you would like to create a Welcome Email for.
{% endstep %}

{% step %}
Under General, click the Welcome Email dropdown, and select an existing **Email Template** to send to your new panelists. To create an Email Template, [follow this guide](/private-panels/emailing-and-sms/email-templates.md).
{% endstep %}

{% step %}
Select the Email Template you want to use, and it will automatically be saved.

![](https://content.gitbook.com/content/T7fhyut5rrQHwe5QRGot/blobs/jTp6Jp3KSFXqLmc3o2Of/38062365321236)
{% endstep %}

{% step %}
These are the events when the emails are sent:

* Panelist manually added on the Panel page.
* Panelist signs up directly via the panel form.
* Respondent is automatically added to the panel after answering a study screener.
  {% endstep %}

{% step %}
These welcome emails are sent about 1 minute after the respondent signs up.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
**Note:** 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/panel-management/panelist-welcome-emails.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.