Aisera Product Release Notes - July 13, 2026
Review what's new and changed, and the fixes and limitations for the Aisera platform in the upcoming release.
Conversational AI
What's New
IVR Channel - Select Workflow to Trigger After Initial Message
You can now initiate execution of a custom workflow after the IVR application/bot plays the initial welcome message. This is especially useful if you need to execute special tasks before the application/bot can help the caller. For example, if you want to authenticate the bot user before they request information from the bot.
To set the post welcome message flow:
Create an Aisera Workflow or decide on a workflow that performs the pre-processing task.
Navigate to Settings > Channel in the Aisera Admin UI.
Select the IVR Channel that you want to associate this specific flow.
Choose a Workflow from the Post Welcome Message Flow pull-down list, as shown below.
Every time a post welcome message flow is specified, the Aisera GenAI platform invokes the flow after it plays the welcome message is played and the caller starts the conversation.
At the end of this flow, the normal execution continues.
The workflow must end with a message asking the user, "How can I help you?" to ensure the response is treated as a new request after the post welcome message flow.
Step 2 of IVR Channel Configuration Parameters
New System Job for Summary Backups
A new automatic maintenance job, Neural Search RAG - Summary Backfill, now runs every Sunday to ensure all documents in your knowledge base have the context needed to deliver accurate search results.
Occasionally, the indexing process may fail to generate a summary due to a temporary service interruption. When this happens, affected documents return less accurate answers without any visible indication. This job automatically detects and fixes those gaps with no additional steps required.
What to expect
The Neural Search RAG - Summary Backfill System job runs automatically every Sunday
This job only re-indexes documents missing summaries all other documents are untouched
If all documents already have summaries, the job completes with no changes
If you do not want to wait for the Sunday run, and you have the appropriate permissions, you can trigger the job manually anytime by choosing it as a Generic new Systems Job in the Aisera Admin UI
If a document was updated since it was last indexed, the backfill job will pick up the latest version ensuring your bot always reflects your most current content.
Option to Choose Neural Search Models in Tenant Configuration
This release includes a new Tenant Configuration option that allows you to choose the neural search summarization model, with valid options limited to gpt-5.1 and llama-3.3-70B.
This option is part of the Tenant Configuration > Neural Search parameters.
How It Works
When the tenant configuration is set to
llama-3.3-70B, neural search summarization uses the Llama model for summary generation.When the tenant configuration is set to
gpt-5.1, neural search summarization continues to use the GPT model and existing GPT summarization prompt.The implementation supports specifying or overriding a Llama-specific summarization prompt when required.
Prompt selection logic correctly switches between GPT and Llama prompts based on the configured summarization model.
Existing tenants that do not configure a summarization model continue to receive the current default summarization behavior without requiring migration or manual changes.
LLM model used for document summarization in Neural Search
Enhanced User Awareness
Aisera applications/bot can now extract input parameter values directly from the application/bot user's request and prior conversation history. This reduces the need for application/bot users to repeat information that they have already provided.
If a user mentions a value in their request (such as, "What is the leave policy in Greece?"), the country value Greece is automatically bound to the relevant input variable in any workflow that requires it, without asking the user again.
If the same or a related value was provided in an earlier sequence of the conversation, the application/bot retrieves it from the conversation history and uses it for slot filling in subsequent workflow interactions.
Enhanced Contextual Awareness
When your application/bot cannot determine a direct answer to a request, it will respond by providing relevant contextual information in addition to the existing fallback options.
When an application/bot user lacks access or no exact information is available for their request, the application/bot will display the reason the request is not fulfilled.
For example, it might return: "You do not have access to this information; however, I found some related topics that might help." instead of displaying the configured static fallback response.
The application/bot responds with any related information that might still be useful, providing more context before presenting the fallback options.
By delivering related information with the configured fallback, the application/bot describes why the primary information is unavailable while still offering helpful alternatives.
What's Changed
IVR Channel - Voice Request Playback for Caller Audio
If you’re using the Interactive Voice Response (IVR) channel with your bot, and you're using the Cisco WebEx Universal Harness, you can now opt in to record each audio request and save a transcript on the Request History page.
Customer admin users can play these recordings on the Requests page next to the user chat bubble. These recordings are used to verify transcription accuracy and train live agents.
This functionality is already available to customers using SIP trunk transfer to send voice calls to Aisera voice bot.
SSO-OAuth 2.0 Setup Using Auth0 Supports Authentication within Webchat
You can now configure SSO authentication to occur within the webchat widget by setting the following parameter in the Authentication tab of the Edit window for the Webchat channel.
The new parameters include:
ACS URL
The identity provider's SSO URL used by Aisera to authenticate
Issuer
The Aisera Entity ID. If none specified, it is generated based on the cluster
IFrame embedding
If checked, then the SSO authentication form is displayed in the same window instead of opening a separate one. You need to configure the identity provider to allow iframe embedding,
Skip compression
If checked, the SAML request from Aisera will not be compressed.
x509 Certificate
Signing Certificate
Limitations
You need to configure the identity provider in the iframe embedding parameter.
Aisera Webchat SSO-SAML and OAuth2-SSO Integration with Auth0
Limitation for multi-intent queries: If any single intent can be fulfilled, the bot will display that successful response and ignore the other intent if it triggers a fallback. However, if both intents trigger a fallback, the bot will surface the contextual fallback for both intents simultaneously.
Flows
What's New
Improved Workflow Publish Error Messaging
Workflow publish validation now returns clearer error messages when a Workflow contains missing metadata, circular dependencies, or invalid draft subflows, making it easier to identify and resolve configuration issues before publishing.
List Approvals V2: Full Approval Context in Response
The List Approvals V2 Action now returns the full approval message and all contextual fields configured in the AskApproval node, giving approvers the complete context they need to review and act on pending approvals without additional lookups.
What's Changed
Sensitive data handling enhancements in Workflows
Workflows now provide stronger protection for sensitive data throughout execution. Sensitive variables retain their protection when transformed or passed between nodes, propagate their sensitivity to derived variables, and maintain full protection when nested fields are accessed. User-provided inputs no longer expose sensitive values, and the platform preserves sensitive data protections across parallel branches.
Workflows also now differentiate between encrypted values, such as secure form inputs, and sensitive plain-text values, such as outputs from authentication actions. The platform decrypts encrypted values before use and passes sensitive plain-text values through directly, reducing the risk of runtime errors caused by improper handling of sensitive data.
Sanitize Hyperflow Prompt setting removed
The Sanitize Hyperflow Prompt setting has been removed from Settings > Configuration > Hyperflows. The platform detects HTML-formatted prompts and converts them to Markdown without additional configuration.
Fixes
Fixed an issue where a subflow created and edited under one application or bot could be incorrectly reassigned to a different application or bot during publish or update operations. This caused the workflow to appear missing from its original application or bot in both draft and published views.
Fixed an issue where the Campaign Insights total users count displayed an incorrect value when one or more campaign delivery attempts failed.
Fixed an issue where publishing a new Workflow / Hyperflow version overwrote the metadata of the previously published version, causing the version history to display incorrect publish timestamps, and Published By attribution.
Limitations
Hyperflows currently do not support streaming
Hyperflows currently do not support streaming. Workaround: Navigate to Configuration > Hyperflows and disable Stream Hyperflow Response Outputs. The models will continue to work normally with streaming turned off.
Miscellaneous
What's Changed
New Restricted privilege level for role-based access control
A new Restricted privilege level is now available in the Features & Permissions tab of the role configuration window, alongside the existing Read, Write, and None options. Restricted applies to the following features: AiseraGPT, Data Sources, Integrations, Channels, AI Workflows, and Privacy Access.
When a feature is set to Restricted, it behaves like None by default, blocking access to the feature entirely. Admins can then open the feature's dedicated tab in the role window and assign Read, Write, or None permissions to individual entities within that feature. This allows admins to grant users access to specific bots, data sources, or workflows without exposing the full list of entities in the tenant.
Built-in roles have been updated so that features in the above list that were previously set to None are now set to Restricted by default.
Aisera Platform Roles and Permissions
Optional tenant ID validation for Remote Executor
The Remote Executor now supports an optional tenantId field in configuration.yaml. When provided, the Remote Executor validates at startup that the apiKey and tenantId are consistent. If a mismatch is detected, an error is surfaced immediately rather than allowing the issue to surface silently at runtime.
This enhancement is fully backward compatible. Existing configuration.yaml files that do not include tenantId will continue to work without modification.
Issues Resolved in the Release
The following table includes bugs that were fixed in this release.
A20-63395
Conversation
Teams Streaming Drops Image-Only Adaptive Card Updates
A20-62983
Voice bot is timing the request with a hard limit of 25 seconds
A20-62982
Cisco Voice - Deepgram STT Integration "Lexicon" field doesn't support words with spaces
A20-62283
Slack channel is not responding with a response when the Size limit exceeds when its in Silent mode enabled
A20-60936
Formatting issue in displaying the Hyperlinks in RAG answer using teams channel in Netapp Tenant
A20-60577
Feedback message isn’t rendering correctly when the RAG action node is used
A20-59841/ GEM-8933
RAG response Formatting issue in Webex channels when its being sent through Adaptive cards
A20-60815
Bot failing to render KMS article Markdown formatting and images
A20-62034
Workflows and Hyperflows
Generic error message instead of actionable messages on Publish failure
A20-63458/ GEM
Different bot_id is introduced with same flow definition id (ai_flows.id)
A20-63009
Remote Executor API Key validation failures
A20-58950
Campaigns: Notification failures & Count Mismatch in Insights
A20-58830
Cisco -- Version History shows incorrect version name after publishing the Workflow
A20-40435
Analytics/Test Suite
Node Names are not displayed properly in Workflow Analytics for specific Flow types
Last updated
Was this helpful?