> 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/summer-2025-webinar.md). # Summer 2025 webinar ![](https://content.gitbook.com/content/wiBgwLWKwWLRYLRUhxPD/blobs/lfyRWtpfKKFcOyrtQLUP/40509143291284) This keynote will showcase how AI is transforming research, not by replacing researchers, but by accelerating their impact. You’ll also get a first look at major platform updates designed to streamline your workflow and expand your reach. During the session, you’ll hear about: * **Smarter, AI-powered research**\ We've up-leveled Dscout AI so you can analyze faster, think more strategically, and uncover insights with ease. From tagging to summarizing and theme generation, you’ll see how our AI makes sense of raw data instantly. * **A faster, cleaner Dscout experience**\ We’re unveiling a redesigned UI that makes navigating projects smoother and more intuitive. Plus, we’re rolling out top-requested features to help you move faster—like improved workflows, cleaner visuals, and simplified navigation. * **Expanded participant access and partner flexibility**\ Get a live demo of our new Respondent integration to see how Partner Panels fit seamlessly into your process. {% 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/summer-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.