> For the complete documentation index, see [llms.txt](https://docs.helvia.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.helvia.ai/resources/release-notes/helvia.ai-release-2026.10.07.md).

# Helvia.ai Release 2026.10.07

07 October 2026

## 1. Run Automated Agent Testing With Azure OpenAI

Automated Agent Testing now works with Azure OpenAI, as well as OpenAI. You can link the Automated Agent Testing plugin to the LLM integration your organization already uses, and pick the model that runs your tests.

**Why it matters:** Until now, Automated Agent Testing supported OpenAI integrations only. Organizations that standardize on Azure OpenAI, often for compliance or data residency reasons, can now test their agents without setting up a separate provider.

**Example use case:** An insurance company runs all of its AI workloads on Azure OpenAI. Before launching a new claims agent, the team links its existing Azure OpenAI integration to Automated Agent Testing and runs its regression suite, keeping all test traffic within its approved provider.

**How it works:** Open the Automated Agent Testing plugin settings for your agent, select an Azure OpenAI or OpenAI integration, and choose a model.

<img src="https://604830754-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBM1xs3i59ajeTgi4uVfN%2Fuploads%2FT0sBWBrRvfK4RNyYA3h9%2Funknown.png?alt=media&amp;token=d76bb691-fc8a-4b42-b212-8164a3e6c1b1" alt="" width="563">

## 2. Get Notified When an Integrated Knowledge Base File Fails to Sync

The platform now alerts you when a file from an integrated Knowledge Base, such as one connected to SharePoint, fails to sync. Workspace admins and owners receive a notification that names the file and links straight to the affected Knowledge Base.

**Why it matters:** Manual uploads already show an error when a file cannot be processed. Synced files, however, could fail without anyone noticing, leaving gaps in what your agent knows. You now see these failures as they happen and can act before they affect answers.

**Example use case:** An HR team keeps its policy documents in a SharePoint library connected to its agent's Knowledge Base. A newly added policy file cannot be processed. The workspace admin gets a notification naming the file, opens the Knowledge Base from the link, and replaces the file with a working version the same day.

**How it works:** Notifications appear in the notification center in the console top bar. Only workspace admins and owners receive them. No setup is needed.

<img src="https://604830754-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBM1xs3i59ajeTgi4uVfN%2Fuploads%2FCdZHkqOz3SjDMs1OGnnt%2Funknown.png?alt=media&amp;token=3ce7919b-6b52-4ca9-a72c-a3dd2c59c961" alt="" width="375">

## 3. Choose the Webchat Service for Each Webchat Deployment

You can now choose which Webchat Service powers a Webchat deployment, directly from the deployment form. A new dropdown lists the available apps, such as Europe, Global, or an OBF service. It is available when you create, edit, or clone a deployment. The platform default is pre-selected, so new deployments work out of the box.

**Why it matters:** Some organizations need their agent to run in a specific region, for example to meet data residency requirements. Until now, changing a deployment's service required help from the Helvia.ai team. You now control it yourself, and you can switch quickly if a provider has a regional incident.

**Example use case:** A bank's customer support agent must run on European infrastructure. When creating the Webchat deployment, the administrator selects the Europe service from the dropdown. Months later, a regional outage affects that app. The team temporarily switches the deployment to another service in a few clicks, keeping the agent available to customers.

**How it works:** Open your agent's deployments and create, edit, or clone a Webchat deployment. Pick an app from the new webchat service dropdown. When you change the app on an existing deployment, a confirmation dialog shows both apps and how open sessions are affected. Every change is recorded in the audit log.

<img src="https://604830754-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBM1xs3i59ajeTgi4uVfN%2Fuploads%2FMGYSsu8iC5rze00l0OWT%2Funknown.png?alt=media&amp;token=4f3d805c-331a-405c-8a6b-ecdb44d0b76e" alt="" height="111" width="432">

{% hint style="warning" %}
**Important note:** Changing the Webchat Service on a live deployment interrupts conversations that are in progress. Active chats disconnect and stop responding, so users have to refresh the page and start a new conversation. Plan the change for a quiet period, such as outside business hours, and let your support team know beforehand.
{% endhint %}

## 4. Export Knowledge Bases Created From an Integration

You can now export the articles of a Knowledge Base whose type is Integration, just like other Knowledge Bases. Importing stays unavailable for these Knowledge Bases, since their content is managed by the connected source.

**Why it matters:** Integrated Knowledge Bases previously offered no export option. Checking what the connector actually brought in meant opening articles one by one. Export gives you a full copy of the content in one step.

**Example use case:** After connecting a document library, a content manager wants to review everything the agent will draw on. They export the integrated Knowledge Base and review all articles in a single file, spotting outdated documents to remove at the source.

**How it works:** Open the Knowledge Base and go to its Settings tab, then click Export.

## 5. Pick Existing Tags When Editing Knowledge Base Articles

Tagging Knowledge Base articles is now faster and more consistent. As you type a tag, a dropdown suggests tags already used across your organization's Knowledge Bases. You can still create a new tag at any time.

**Why it matters:** Typing tags by hand made it easy to create near-duplicates, such as "billing" and "Billing ", which split related content apart. Suggestions keep your tags clean, which makes content easier to organize and target.

**Example use case:** A support team tags articles by product line. When a new team member adds an article about refunds, the dropdown suggests the existing "Payments" tag. They select it instead of creating a new "payment" variant.

**How it works:** Open an article in a Knowledge Base and click the tags field. Pick a suggested tag, or type a new one and press Enter. Suggestions build up as your team adds tags in the console.

## 6. One Idle Notification at a Time in Webchat

When you set up several idle notifications for a Webchat deployment, only the latest one is now shown. Each new reminder replaces the one on screen, so they no longer stack up over the conversation.

**Why it matters:** Idle reminders that piled on top of each other made the chat window feel cluttered and forced users to close each one. Users now see a single, current message, and your reminders read as intended.

**Example use case:** A retailer reminds inactive shoppers after 3 minutes and again after 10 minutes. A shopper who steps away returns to find only the 10-minute reminder on screen, rather than both stacked together.

\ <br>