> 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/guides/recruiting-with-confidence.md).

# Recruiting with confidence

Welcome to **Recruiting with confidence**! Recruiting the right participants can make or break a study. So, let's walk through how to do that in Dscout, focusing on participant sources, recruitment approaches, and screener design.

**In this course, you'll learn about:**

* Participant sources in Dscout.
* Recruitment styles in Dscout.
* Designing strong screeners.
* Writing smart screener questions.
* Selecting the right participants.

Each lesson builds on the one before it, so we'd recommend working through them in order if this is your first time recruiting on Dscout.

{% hint style="success" %}
**A note on terminology:** Throughout this course, you may see “Scout” used to refer to participants recruited from Dscout's own panel as well as the general "participant" for anyone taking part in your research, including those you recruit outside of Dscout.
{% endhint %}

Start with lesson one: [Participant sources in Dscout](/guides/recruiting-with-confidence/participant-sources-in-dscout.md).


---

# 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/guides/recruiting-with-confidence.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.