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

# February 2025

This month, we're making research faster and easier—boost collaboration and simplify your setup.

## What's new?

### MANAGE

* ### Introducing question banks

  Building research projects just got easier! With [question banks](https://help.dscout.com/hc/en-us/articles/32198835510420), you can **save, organize, and reuse** your most effective questions (and answer options) in one convenient place. No more starting from scratch—now, you and your team can focus on insights, not setup.

  #### Why use question banks?

  * **Save time** – Quickly pull in your best questions when creating Express or Recruit missions.
  * **Ensure consistency** – Standardize the questions that drive reliable insights across projects.
  * **Enable collaboration** – Share vetted questions with your team to build a collective library of go-to research questions.

  Whether you're running a quick study or building a complex research project, question banks help you work faster and more efficiently.

  *Available in Plus and above plans.*

  ![](https://content.gitbook.com/content/wiBgwLWKwWLRYLRUhxPD/blobs/lj8mWmrWtlBM46vVPeDk/34731767102996)


---

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