> 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.05.20.md).
# Helvia.ai Release 2026.05.20
## 1. Schedule Automated Session and Survey Exports
You can now automate the delivery of session and survey exports by scheduling recurring reports directly from the platform. Exports are sent as spreadsheet attachments to selected recipients, with customizable email subject lines and body content for easier distribution across teams.
**Why it matters:** Previously, session and survey exports had to be generated and shared manually, creating repetitive work for operations and reporting teams. With scheduled exports, stakeholders automatically receive the latest data at the desired frequency without requiring Console access.
**Example use case:** A customer experience manager schedules a weekly survey export to be automatically emailed to regional team leads every Monday morning, ensuring teams always have up-to-date feedback data for performance reviews and planning.
**How it works:** Configure a scheduled export from the Reports section by selecting the export type (Sessions or Surveys), defining the delivery frequency, adding recipients, and customizing the email content. The platform automatically generates the spreadsheet and sends it as an email attachment on the scheduled interval.
## 2. Customize the Floating WebChat Button Experience
The floating WebChat button can be customized with configurable icons and animations, making it easier to align the chat experience with your brand and interaction style. New options include custom open/close icons, animation variants, hover effects, and configurable icon transition behavior.
**Why it matters:** Previously, customizing the floating chat button required CSS overrides or custom implementations, limiting flexibility and increasing maintenance effort. With these new built-in settings, you can create a more polished and branded WebChat experience directly through configuration—without affecting existing deployments.
**Example use case:** A retail brand replaces the default chat icon with a branded assistant avatar, adds a subtle bounce animation to attract attention, and enables a hover zoom effect to make the chat entry point more interactive and visually aligned with the website design.
**How it works:** In WebChat bubble mode, you can now configure separate icons for the open and close states using image URLs or inline SVGs. Additional animation settings allow you to control idle behavior (pulse, bounce, or none), hover effects, and icon transition animations when the chat opens or closes. All new settings are optional, and existing deployments continue to behave exactly as before by default. To enable and configure these customization options for your deployment, please contact your Helvia.ai Account Manager.
## 3. Filter Chat Sessions by User Interaction
You can now filter chat sessions in the Observatory using the new Contains User Interaction filter. This makes it easier to focus only on sessions where end users actively engaged with the agent, improving analysis and troubleshooting workflows.
**Why it matters:** Previously, the sessions table included all sessions, including those without meaningful user activity. This made it harder to identify relevant conversations during operational reviews or debugging. With this filter, teams can quickly isolate sessions that contain actual user interactions.
**Example use case:** A support operations team reviewing chatbot engagement can filter out inactive or system-generated sessions to analyze only conversations where users interacted with the agent.
**How it works:** In the Observatory → Sessions table, enable the Contains User Interaction filter to display only sessions that include at least one user interaction event. The filter works alongside existing Observatory filters for more targeted analysis.
---
# 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://docs.helvia.ai/resources/release-notes/helvia.ai-release-2026.05.20.md?ask=&goal=
```
`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.