> For the complete documentation index, see [llms.txt](https://docs.aisera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aisera.com/product-release-notes/2026/aisera-product-release-notes-august-18-2026.md). # Aisera Product Release Notes - August 18, 2026 ## Analytics ### What's New #### Voice Metrics in Analytics Tab You can now see metrics from your Interactive Voice Response (IVR) applications/bots in the Pre-Built Analytics window of the Aisera Admin UI. The Voice tab has been added to the Pre-Built Analytics window to display metrics such as Total IVR Calls, Average Call Duration, Escalation Rate, Drop-off Rate, and Call Outcomes (by resolution). See the link at the end of this section for the complete list of captured metrics. **To See the Voice Tab:** 1. Select **Analytics > Pre-Built** in the Aisera Admin UI. 2. Choose the **Voice** tab on the right top of the **Pre-Built Analytics** window. [The Voice Tab](https://docs.aisera.com/aisera-platform/analytics/analytics/pre-built-analytics#voice-tab) ## Conversations ### Fixes * Fixed an issue where the Request page was displaying errors about Conversation Feedback. * The introductory Welcome Message in chat has been fixed so it is now localized based on the users selected preferred languageintro welcome in chat is now localized based on the users selected preferred language. * Fixed an issue where the Fulfillment Source was not populated when using AI Lens with a Conversation 2.0 application/bot. The fulfillment source is now correctly set to ReasoningEngine for this scenario.\ \ [Fulfilment Source](https://docs.aisera.com/aisera-platform/ai-workbench-optimize-conversations/ai-lens#fulfillment-source-per-application-bot-version)
## Flows ### What's Changed #### Description validation required for Workflow and Hyperflow registration The **Description** is a required field for Workflows and Hyperflows in Aisera 2.0 applications, and is used in the flow search and registry. The platform now validates that Workflows and Hyperflows include the **Description** before they can be added to the flow registry. This change prevents incomplete metadata from introducing execution and discovery issues. When administrators attempt to register Workflows or Hyperflows to an Aisera 2.0 application all available flows are selectable. Before registration is complete the system validates that each selected flow contains a Description. If one or more flow is invalidated, those flows will not be registered and an error message will identify the affected flows. Flows with no errors will be registered successfully. This change is backwards compatible with existing flow search and registration experiences. Existing flows without descriptions are now removed from the flow registry. #### Hyperflows without functions cannot be published or executed The Aisera Platform now validates that a Hyperflow contains at least one function before allowing it to be published. If a Hyperflow lacks a function, publishing is prevented and a clear message explains why, preventing non-functional automations from failing at runtime. Testing a draft Hyperflow is blocked when no functions are configured. ### Fixes * Fixed an issue where the Send Notification action sent messages to the phone number in the user profile instead of the number provided in the node’s **Cell Number** field. The C**ell Number** field now correctly takes priority over the user profile cell number when provided. * Fixed an issue in the **Workflow Inport** feature where OAuth-based integrations referenced through Workflow User Input nodes during import appeared alongside standard action-node integrations in the mapping screen, causing provider ID mismatches and post-import errors. A dedicated OAuth Provider section now appears in the mapping experience for these integrations. * Fixed an issue where users would occasionally see an outdated draft version of a Workflow after stopping a test session. Previously, users might have occasionally noticed recent Workflow changes appear to be missing after clicking Stop Test. ## Ingestion and Connectors ### What's New #### Token Authentication added to the Freshworks and Freshdesk connectors The **Freshworks** and **Freshdesk** connectors now support a dedicated **Token** authentication type. API keys entered in the new token field are masked in the UI and encrypted at rest, providing a more secure setup for your integrations. Existing connections using **Basic** authentication will continue to work without disruption, but it is recommended to use the new **Token** authentication type moving forward. [Freshworks Connector](/aisera-platform/adding-data-to-your-tenant/integrations-and-data-sources/connectors/freshworks-connector.md), [FreshDesk Connector](/aisera-platform/adding-data-to-your-tenant/integrations-and-data-sources/connectors/freshdesk-connector.md) #### OAuth 2.0 credential encryption at rest Sensitive OAuth 2.0 credential fields are now encrypted at rest, with encryption and decryption handled at the data layer. There are no changes to how you configure OAuth-based connectors. This provides an additional layer of protection so that stored credentials remain secure even if the underlying data is accessed without authorization. #### Credential expiration and authentication failure notifications for integrations Tenant Admins can now configure email alerts for credential health problems across all integrations from a new section in **Settings > Configuration > Credential Notifications**. Global settings define who receives notifications, the digest cadence (daily or weekly), and which credential event types generate alerts, including runtime authentication failures, OAuth token refresh failures, mTLS validation failures, and proactive expiration reminders. Per-integration settings allow Admins to set a known credential expiry date, schedule reminders up to 30 days before expiry, and override the tenant-level recipient list for integrations owned by a different team. Credential issues auto-resolve from future digests once an Admin updates the affected credentials. [Credentials Notifications](/aisera-platform/adding-data-to-your-tenant/integrations-and-data-sources/creating-a-connector/configuring-credential-expiration-alerts.md), [Configuring Credential Expirations Alerts](/aisera-platform/adding-data-to-your-tenant/integrations-and-data-sources/creating-a-connector/configuring-credential-expiration-alerts.md) ### Fixes * Fixed an issue where text formatting in Slack was not rendering correctly. Text formatted using MD syntax would directly render the syntactic symbols rather than formatting the text. ## Tickets ### What's New #### Feedback Summary in Ticket Details Window The **Ticket Details** view now includes a **Feedback Summary** section showing the number of agents who interacted with a ticket alongside the total thumbs up and thumbs down responses received. Navigate to **SOR > Tickets** in the Aisera Admin UI and then open a **Ticket** in the list to see the **Ticket Details** window. The **Feedback Summary** is in the lower part of the window, within the **Wrap-Up** section. This summary gives teams a quick snapshot of agent engagement and resolution confidence at a glance. [Feedback Summary](https://docs.aisera.com/aisera-platform/adding-data-to-your-tenant/data-ingestion/what-data-is-ingested/tickets#feedback-summary) ## Miscellaneous ### What's New #### Manage Multiple Tenants in a Single Browser You can now stay logged into multiple tenants at the same time, within a single browser - no more juggling separate browsers or private windows. Each tenant session is fully independent. Logging out of one tenant has no effect on your other active sessions, and sessions can be revoked individually per tenant. #### Model provider update The underlying model provider for Conversational AI has been updated. No action is required and no changes to product functionality are expected. ### Fixes * Fixed an issue where updating permissions from `restricted` to `read` or `write` caused unexpected behavior. * Fixed an issue where users were unable to update existing channels and integrations. Users who did not have administrator privileges were unable to edit existing channels and integrations.