> 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/example-screener-teasers.md). # Example screener teasers Your teaser is intended to provide participants with a general idea about the topic of your study. The best teasers include: * Details about your project's goals * The amount of time and number of activities your project entails * The reward participants who complete your project can expect * Any specific requests you'll make during your screener. For example, if your study is about how participants play with their pets, and you require them to take a picture of their pet in your screener, let participants know they need to be around their pet when they apply. ### Good teaser examples * "We'd love you to take us on a tour of your refrigerator in an upcoming study that pays $20. Make sure you're at home before starting this application, because we'll ask you to answer a few questions and take a quick video of your fridge!" * "It's getting to be that festive time of year again, and we're planning a special project that will last from Thanksgiving to New Years. Apply now for the chance to participate! If selected for this project, you'll share a little about what life is like for you over the holidays in a series of 6 activities over the next 8 weeks. Participants who complete this project will earn $300!" * "Have you ever looked at something you use, own or wear and thought of a neat way to improve it? Now is your chance to share these ideas with product designers! Apply now for the chance to make $15 by completing a 1-Activity study all about making better stuff. You will need to record a 30-second video as part of this application." --- # 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/example-screener-teasers.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.