> 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/fall-2025-webinar.md).

# Fall 2025 webinar

![](https://content.gitbook.com/content/wiBgwLWKwWLRYLRUhxPD/blobs/bdVXmmsw0OpbIo2cWovP/44503946286356)

In Dscout’s 2025 Product Keynote, Bridget Bidlack (Chief Product Officer), Jonathan Fairman (VP of Emerging Products), Lauren Madura (Director of Product Design), and Jessica White (Director of Product Management) unveil a year of transformational progress, and a bold vision for 2026. From AI-powered insights to fully agentic recruiting and flexible, dynamic research workflows, Dscout is redefining how research gets done.

Plus, the team walks through a redesigned home page, updated capabilities, and enhanced recruitment.

Also, get a behind-the-scenes look at Explore Your Data, Canvas, and our upcoming AI moderator—each designed to keep researchers in control while accelerating impact. Hear from the product minds behind these innovations as they explore how Dscout is becoming more intelligent, integrated, and human than ever.

{% embed url="<https://www.youtube.com/watch?v=PMwrhsnWHGI>" %}


---

# 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/fall-2025-webinar.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.