> 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/what-are-dscout-screeners/screener-webpages.md). # Screener webpages Webpages are automatically created for screeners you're sending to your own participants. These webpages offer all the information your applicants need to know about the opportunity. You can also add custom messaging to the exit screens your externally recruited participants will see when they either successfully complete the screener or get knocked out from the screener. This is helpful in giving participants more information about your study. When designing questions in the Screener tab of your screener, you can customize text in the "Thank you" section. Edit the Completion message for qualified applicants, and/or the Knockout message for disqualified participants. ![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/M2z1K8mLaH6sLVsAlJLr/34717343140756) Before launching, you can check out what your webpage will look like from a participant's perspective by finding the Private share link at the top of the Overview tab and clicking **View**. Here, you'll also be able to preview your completion and knockout messaging. The previews will show the most up-to-date copy you’ve added. Here's what a screener splash page looks like when a participant first opens it:
Potential participants who've never used Dscout will be able to apply by simply providing their first name, last name, and email address. Read more in [Private screener onboarding flow for first-time Scouts](/recruit-participants/what-are-dscout-screeners/screener-flow-for-bring-your-own-participants.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/recruit-participants/what-are-dscout-screeners/screener-webpages.md?ask=&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.