> For the complete documentation index, see [llms.txt](https://helpdocs.conducttr.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocs.conducttr.com/release-notes/2026/may-2026.md).

# May 2026

**Release Date:** 23 May 2026

### What's in This Release

This release includes a set of small fixes and improvements across Communications Manager, Colibri, and other features.

#### Communications Manager:

* **Reply preview in email** – The reply preview for email is now displayed in Composer.
* **Groups - Collapse button position** – The collapse button for groups has been moved to the right to avoid overlapping with other interface elements.
* **Exercise Description copy** – Fixed an issue where the Exercise Description was not being carried over to the Exercise, ensuring content is preserved as expected.
* **Persona channel handle** – The persona's channel handle is now properly shown in Communications Manager.
* **Auto-response column restriction** – Users are no longer able to create a column with auto-response settings where it shouldn't be allowed.
* **Scheduled messages** – Fixed an issue where scheduled messages were not appearing in Communications Manager.

> **Please note:** Scheduled messages are currently only available for Microblog and Articles/Websites channels. Only new content can be scheduled - scheduling replies is not supported at this time.

#### Colibri

* **Msngr Plus channel availability** – Msngr Plus is now available as a channel, allowing designers to use it as part of Colibri exercises. 
* **Player message style changes** – Fixed an issue where edits to player message style in Configuration were not reflected in the preview window.

#### Other improvements:

* **Persona Attributes – Apply Influence** – Resolved an issue where the Apply Influence action was not working correctly within Persona Attributes.
* **Teams CSV Upload** – Improved error handling during Teams table imports via CSV, now showing a clear message when invalid passwords are detected.
* **Editor – Teams Table import** – When importing a new teams list, users can now choose to add to or replace the existing teams, eliminating the need to manually delete entries one by one.
* **Impersonation widget red dot** – Improved the red dot indicator on the impersonation widget, particularly for Microblog/Instagram channels.
* **Smartwords – Button behaviour** – Clicking a smartword in the text editor now opens the Smartwords widget with that smartword selected and in focus. A tooltip also displays the smartword's value on hover.
* **Scenario Editor – Data Point Name validation** – The colon character ":" is now restricted from being used in Data Point names, preventing conflicts with internal reserved characters.
* **Scenario Editor – Tables in log injects** – Users can now add tables when writing log injects in the Scenario Editor.
* **Scenario Editor – Exercise Name** – Fixed an issue where changes to the Exercise Name in Exercise Setup would revert to the original name instead of saving correctly.
* **Teams list email format support** – The teams list upload now accepts a broader range of email address formats, including those with non-standard domain extensions such as .financial or .london.
* **Telegraph support** – Telegraph has been added as a supported channel in Social Graph.

### Bug fixes <a href="#id-1.4-bug-fixes" id="id-1.4-bug-fixes"></a>

Other bug fixes have been applied across the platform to improve usability and overall user experience.

<br>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://helpdocs.conducttr.com/release-notes/2026/may-2026.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.