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

# Spring 2025 webinar

![2025 Spring Product Update - Resource Library Hero - 2056x683.jpg](https://content.gitbook.com/content/wiBgwLWKwWLRYLRUhxPD/blobs/w1yQyXXUn6K0nUfREIoK/37752791685524)

Hear from Dscout product leaders in **Dscout’s Spring 2025 Product Update**, where our product leaders walk you through the latest releases—and give a peek at what’s just around the corner. You’ll get a live look at the newest ways we’re making research faster, easier, and more impactful.

During the session, you’ll hear about:

* **A smoother, more flexible experience** We’ve added and refined features to give you more control and improve your flow—whether you’re launching, moderating, or analyzing.
* **Expanded participant access + better recruiting insight** We’re making it easier to connect with the right people—and see where they’re dropping off.
* **Smarter support from AI** We’re building tools that work *with* you, not just for you.

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


---

# 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/spring-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.