> 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/recruit-participants/dscout-scout-panel/programming-insight.md).

# Programming insight

When recruiting participants, it can be useful to see where applicants are most often being disqualified. In screeners, usability tests, and media surveys, you can see exactly how many applicants were disqualified by each of your knockout questions. Then, you can use that data to update your knockout logic to either be more or less inclusive depending on your needs.

{% hint style="info" %}
Programming insight is only available when auto-recruiting from the Dscout Scout panel.
{% endhint %}

Once you launch your screener or study, you'll find programming insights on the **Overview** tab:

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/CPJERknDybCKjPK22ue6/35527443273108)

{% hint style="info" %}
If your participant numbers are low and one question is disqualifying most of your applicants, consider whether your requirements for that question can be more flexible.
{% 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/recruit-participants/dscout-scout-panel/programming-insight.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.