# News

## 2026 May 11th

DialoX 4.1 was released two weeks later than planned due to staff availability. 

### Highlights

<table><thead><tr><th width="100.58203125">Ticket</th><th width="147.00390625">Skills</th><th>Change</th></tr></thead><tbody><tr><td>DSA-221</td><td>Base skills</td><td><strong>Lookup node: fuzzy matching improved</strong><br>Fuzzy matching will be more precise in selecting a sensible match instead of choosing something anyway.</td></tr><tr><td>DSA-218</td><td>Agent skills</td><td><strong>Improved no input behaviour on chat channels</strong><br>Causing the bot to gracefully handle no input instead of keeping reminding the user to respond.</td></tr><tr><td>DSA-131</td><td>Agentic Studio helpdesk 2.0</td><td><strong>Studio Helpdesk 2.0</strong><br>A completely new version of the DialoX helpdesk studio widget that has access to the developer and user documentation. The studio helpdesk agent is able to provide detailed answers about both bot development as flow designing and will point to the relevant documentation. When it fails to be helpful and users ask to be forwarded to a human, it will still escalate to a human operator</td></tr><tr><td>DSA-225</td><td>Shomi</td><td><strong>Shomi to write summary in UK english</strong><br>Instead of US english</td></tr><tr><td>DSA-189</td><td>Shomi</td><td><strong>Push to CRM using Contact Connect improved</strong><br>Now Shomi will explain to which CRM the summary is pushed and if it succeeded or failed. If it succeeded, it will even provide a link to it in the specific CRM (if supported by that CRM)</td></tr></tbody></table>

## 2026 March 31st

With the DialoX version 4.0 release the platform is deemed to be ready to start supporting the introduction of Agentic capabilities to Enreach Contact based Smart App extensions.&#x20;

In the coming period the DialoX team will be bringing these capabilities to partners and customers by introducing the **AI Agent** skill that enables agentic capabilities to flow based bots. Currently this skill is only available to selected beta partners before making it generally available later this year. &#x20;

### New functionality

<table><thead><tr><th width="100.58203125">Ticket</th><th width="147.00390625">Skills</th><th>Change</th></tr></thead><tbody><tr><td>DSA-132<br>DSA-174<br>DSA-171<br>DSA-142</td><td>AI Agent 0.5<br><br>Agent Knowledge Base 0.2</td><td><strong>Iterate agent node</strong><br>Introducing Agentic behaviour to SmartApps that can respond and use tool call tasks autonomously.<br>The platform provides built in Agent Prompt templates for an Agentic Receptionist and an internal Colleague Router.<br><mark style="background-color:yellow;">currently a beta feature, only available on request</mark></td></tr><tr><td>DSA-158</td><td>Base Flows 3.4</td><td><strong>Lookup table node</strong><br>To allow flows to use a custom lookup table, this way a Smart App could find a subsdiary with a city name, or a phone number with a department name.<br><a href="https://manuals.dialox.ai/studio/flows/nodes/lookup-table">https://manuals.dialox.ai/studio/flows/nodes/lookup-table</a></td></tr><tr><td>DSA-166</td><td>Phone Flows 3.4</td><td><strong>Lookup extension node</strong><br>To allow Smart Apps that use the Grid adapter to find a specific extension based on the name or number of the extension returning information like presence, wait time, callers in queue, etc<br><a href="https://manuals.dialox.ai/studio/flows/nodes/lookup-extension">https://manuals.dialox.ai/studio/flows/nodes/lookup-extension</a> <br><mark style="background-color:yellow;">currently only available for native Enreach Contact customers (no Swyx) that are migrated to the Grid Adapter</mark></td></tr><tr><td>DSA-127</td><td>Phone Flows 2.4</td><td>Add built in variables for <code>callee</code> and <code>prefix</code> <br><mark style="background-color:yellow;">currently only available for native Enreach Contact customers (no Swyx) that are migrated to the Grid Adapter</mark></td></tr></tbody></table>

### Bugs fixed

<table><thead><tr><th width="101.421875">Ticket</th><th width="145.703125">Skill</th><th>Fix</th></tr></thead><tbody><tr><td>DSA-175</td><td>Shomi</td><td>Improved Shomi summary LLM timeout behaviour with longer timeout and retry mechanism</td></tr><tr><td>DSA-180</td><td>Shomi</td><td>Shomi translation issue DK</td></tr><tr><td>DSA-182</td><td>Shomi</td><td>Participants in Shomi summary are missing often for live transcriptions</td></tr><tr><td>DSA-193</td><td>Shomi</td><td>Push to CRM bug: timeStopped is required for Microsoft Dynamics</td></tr><tr><td>DSA-170</td><td>Base skill 3.4</td><td>Add locale specific texts for numbers in ask:language for Hungarian</td></tr><tr><td>DSA-194</td><td>Platform</td><td>Described all roles and permissions in DialoX<br><a href="https://staging.developer.dialox.ai/platform/roles_and_permissions/">https://developer.dialox.ai/platform/roles_and_permissions/</a></td></tr></tbody></table>


---

# Agent Instructions: 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:

```
GET https://manuals.dialox.ai/start/readme.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.