> 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/studies/confirmation-emails.md).

# Confirmation emails

Private Panels takes away the manual work of sending confirmations and reminders.

## Confirmation Emails

Once you have scheduled a Participant for a study, it's great practice to send them a confirmation email with the Date & Time, Session Location, and any other necessary information.

{% stepper %}
{% step %}
Update the **Study Scheduling Confirmation Email** section

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

{% step %}
Navigate to the **Study Overview Scheduled tab**, and select the Participants you want to send the confirmation email to

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

{% step %}
From the Send email dropdown, select Send scheduling confirmation and send the email

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

Your participants will receive this email, and be asked to click the **Confirm** button. If they click the button, this event will be tracked in Private Panels, and you will see a checkmark in the Confirmed column next to their name in the study.

{% 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/studies/confirmation-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.