> 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/product-updates/product-webinars/winter-2025-webinar.md). # Winter 2025 webinar ![](https://content.gitbook.com/content/wiBgwLWKwWLRYLRUhxPD/blobs/evGT0HbitmPFT9zYWSQK/35223682211604) Hear from Dscout product leaders in **Dscout’s Winter 2025 Product Update**, where they unveil the latest innovations designed to uplevel your research experience. Get a firsthand look at the latest features making research faster, easier, and more impactful. During the session, you’ll hear about: * **Optimized user experience:** We’re rolling out top-requested features to make Dscout smoother and more intuitive. Expect improvements like question banks, external video uploads, and post-launch edits. * **Expanded participant access:** We’re enhancing recruitment with expanded recruiting quotas, a better Bring Your Own experience, and improved Private Panels management. * **Innovation that moves research forward:** AI-driven features like our interactive Research Assistant and automated usability test insights redefine research efficiency. {% embed url="" %} --- # 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/product-updates/product-webinars/winter-2025-webinar.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.