> 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/2026/readme.md).

# September 2026

What's been released, changed, and improved across the Dscout platform

{% updates format="full" %}
{% update date="2026-09-30" tags="improvement" %}

## Read “Other” write-in responses without opening every submission

When a choice question includes an “Other (tap to type)” answer choice, you can now read the write-in responses directly from the aggregated chart in your study’s Responses view—no more opening each participant’s submission one at a time to find what they typed.

Click the chevron beside the **Other** row to expand a list of write-ins, each showing the participant and their typed response, with a link through to that participant’s full response. The **Other** choice now also stays at the bottom of the chart regardless of how you sort it.

#### Other improvements

* Support hours now show on your account overview and workspace balances only if your account has purchased support hours. If your subscription doesn’t include support hours, the section is hidden rather than showing an empty balance.
  {% endupdate %}

{% update date="2026-09-25" tags="improvement" %}

## More AI-powered analysis and media tools in the Dscout MCP

The Dscout MCP now supports even more tool calls, so you can do more with your study data without leaving your favorite AI tool. You can now:

* Pull AI-generated analysis—summaries, themes, notable moments, and emerging themes—into your conversation (`discover_analysis_artifacts`, `list_analysis_artifacts`, `get_analysis_artifact`).
* Review and create tags, and see how they've been applied across a study (`list_tags`, `create_tag`, `create_tag_group`, `apply_tag`, `unapply_tag`).
* Export session recordings, transcripts, and other study data, and download individual media files (`create_media_export`, `get_media_export`, `create_media_download`, `create_media_composition`, `list_media`).
* Build and share highlight reels from existing clips (`create_reel`, `list_reels`, `get_reel`).
* Review timeline events like click activity, flagged moments, and interview markers, and page through long session transcripts (`list_timeline_events`, `get_transcript_window`).
* Bulk-set fit ratings on a standalone recruit screener's applicants (`rate_applicants`).

For the full list of available tool calls, see [Dscout MCP tools](/dscout-ai/dscout-mcp/dscout-mcp-tools.md).
{% endupdate %}

{% update date="2026-09-23" tags="improvement" %}

## Upgraded study templates

Screener and study templates have gotten an upgrade, offering mix-and-match functionality between screeners and studies. Now, you can standardize recruitment approach and study objectives while still remaining flexible.

For more information, see [Study templates](/study-basics/study-templates.md).

## Clearer role names

To make it easier to understand what each teammate can do in your account, we've renamed two Dscout user roles:

* "Researcher" is now called "Editor".
* "Contributor" is now called "Collaborator".

Collaborators can also now only build the following study types using templates, not from scratch:

* Usability tests.
* Media surveys.
* Intercept studies.
* AI moderated studies.

For more information, see [User roles and permissions](/getting-started/dscout-quickstart-guide/user-roles-and-permissions.md).

#### **Other improvements**

* PDF exports now show a consistent randomization indicator ("Choices," "Stimuli," or "Stimuli and choices") for every question type that supports it, including card sort questions.
  {% endupdate %}

{% update date="2026-09-15" tags="improvement" %}

## Streamlined terminology for clearer research

We're moving away from a few Dscout-specific terms to help you run research faster, using language you're already familiar with.

You'll see the following language changes throughout the Dscout platform:

* "Missions" are becoming "studies".
* "Live missions" are becoming "interview studies".
* "Express missions" are now identified using their specific methodology: "usability tests", "media surveys", "intercept studies", and "AI moderated studies".
  {% endupdate %}

{% update date="2026-09-01" tags="improvement" %}

## Smoother invites in diary and interview studies

<figure><img src="https://3203039664-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwiBgwLWKwWLRYLRUhxPD%2Fuploads%2FAgsAXn82Zq2NkJivZkgO%2FInvite%20fow%201.jpg?alt=media&#x26;token=315b760a-50b1-402a-98aa-685545300a58" alt=""><figcaption></figcaption></figure>

When adding participants to launched diary or interview studies, they are now automatically invited to the study. Previously, participants were first added to an "invite queue" without invites actually being sent, which required an additional step.

For more information, see [Add participants from a screener to a study](/recruit-participants/what-are-dscout-screeners/add-participants-from-a-screener-to-a-study.md), [Add participants to a diary study](/diary-studies/manage-a-diary-study/invite-participants-to-a-diary-study.md) or [Add participants to an interview study](/interview-studies/create-an-interview-study/invite-participants-to-an-interview-study.md).
{% endupdate %}
{% endupdates %}


---

# 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/2026/readme.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.