Are you using the latest version of RingCentral?
Update your app now to enjoy the latest user experience, enhanced security, and optimal call quality.
This page shows the products and features currently planned for the 26.3 release cycle, which begins on 3 August 2026 and ends when the next release begins, which is currently targeted for 25 October 2026. Features are subject to change between now and the end of the release cycle. You may receive these features at different times throughout the release cycle. Remember that you may be required to purchase a license or sign up for a controlled release (CR) program to access some of them.
All new products and features are shown by default. If you want to see only products and features in your Contact Center system, you can clear the checkboxes to remove features you don't need from your display.
Each feature description includes a table that states whether the following details apply to it. ✓ means that the detail applies to the feature and ✖ means that the detail does not apply to the feature.
| Customer Request | The feature was developed by customer request. |
| UI Change | The feature introduces changes to the user interface (UI). |
| Breaking Change | For API features only. If your integration uses the specified API, you must update your integration to avoid disruptions. |
| Impacted Versions | For API features only. The versions of the API that were changed. |
| Web or Desktop Studio | For Studio features only. Whether the feature is supported in web Studio, desktop Studio, or both. |
| Availability | This cell tells you two things about the feature:
|
Learn about the platform requirements and FedRAMP support status for the Contact Center apps you use.
Starting with the 26.3 release, the Contact Center Controlled Release program will be renamed to Public Preview. This change will be reflected in the online help, release notes, and in other communications from Contact Center.
| Customer Request | ✖ | UI Change | ✖ | Availability | N/A |
Managing access keys will become easier and safer with new automatic controls. Admins will be able to set rules to lock keys that are not being used, which will help reduce security risks without needing manual work. The system will also show which keys should be updated based on how old they are, helping you follow best practices. Keys will not be deleted automatically, and admins will still be able to unlock or manage them anytime. These new settings will be available in this release to help keep your system secure and up to date.
The Access Key Settings button will be available only when Security Policy, View and Configure is enabled.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On toggle |
In this release, password updates will be made more secure in User Hub. The Change Password option will be removed from the My Profile section, and users will update passwords only through the Forgot Password option on the login page. User will receive an email with the password reset link, helping protect their accounts from security risks.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On toggle |
Contact Center will soon improve security by adding session IDs (sid) and token IDs (jti) to all login tokens to help you track user sessions from start to finish. These IDs will make it easier to see exactly how and when a session is used, helping with security audits. We are also adding a safety feature that automatically stops access if a security key is disabled. These changes will improve your security monitoring without changing how you log in today.
| Customer Request | ✖ | UI Change | ✖ | Availability | GA On toggle |
The Admin application will include significant accessibility improvements designed to offer a smoother, more inclusive experience for users across a wide range of visual, motor, and cognitive needs.
| Customer Request | ✓ | UI Change | ✖ ✓ | Availability | GA On deploy |
Knowledge Hub documentation has been moved from the Contact Center Help Center to the Expert Help Center. Use the Expert Help Center to access the latest Knowledge Hub documentation.
| Customer Request | ✖ | UI Change | ✖ | Availability | GA On deploy |
CXone Agent will support integration with Epic Healthcare EMR, enabling your agents to access patient and healthcare records directly within the CXone Agent workspace.
This product will be available later in the release cycle.
| Customer Request | ✖ | UI Change | ✓ | Availability | CR On toggle |
Currently, unified quick responses are in controlled release (CR). With the 26.3 release, they will be moved to general availability (GA).
You will be able to configure short messages that agents send to contacts while working in the agent application. Today, these messages must be set up in different areas of ACD, depending on the type of message needed. This makes the configuration process confusing and inefficient. In this release, we will deliver a new, unified Quick Response. This will allow you to create and manage all of these messages in one place.
To make individual quick responses available to agents in the agent application, you will assign them to ACD skills. Previously, the legacy quick responses and rich messages were associated with tags. By associating them with skills, you will be able to easily make quick response options available to agents when they're relevant.
Using quick responses will require permissions at the agent and administrator levels. Agent permissions will allow them to use quick responses and add them to a favorites list. Admin permissions will allow them to view, create, and edit quick responses.
Digital quick responses and rich messages will be automatically migrated. The migration process will take place during the 26.3 release cycle, but the timing may not align with when the 26.3 release deploys to your cluster. This means you could see the Quick Responses page in ACD before your digital quick responses and rich messages are migrated.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
The bulk upload template for ACD skills will be updated with a column for the Telecom Route Override field. This aligns the settings so they can be configured from the platform UI or the bulk upload template. This will prevent bulk uploads from unintentionally overwriting this setting with a null value.
| Customer Request | ✓ | UI Change | ✖ | Availability | GA On deploy |
You will be able to access log files that provide details about the execution of real-time routing rules. The logs will provide you data about each time the system executes a rule to route an interaction. This will allow you to efficiently review system behavior, validate routing outcomes, and troubleshoot issues. You will be able to see:
You will be able to search and filter the log results by ACD skill, status, and metric to find the entries you want.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On toggle |
You will be able to manage primary agent skill assignments using a bulk update template. You will be able to upload and download the template directly from the Primary Skills section in real-time routing rules. You will be able to export current assignments to a file template and upload new assignments for up to 1,000 skills and 5,000 agents at once. This change simplifies the initial setup and management of primary skills, providing better visibility and coverage insights for your routing strategies.
| Customer Request | ✖ | UI Change | ✓ | Availability | CR On toggle |
Real-time routing rules engine will receive enhancements to performance and scalability. The updates will ensure that the system can process up to 25,000 active rules at the same time across the entire cluster. The system stability will be improved, allowing faster rule evaluation, even during times of high interaction volumes.
| Customer Request | ✖ | UI Change | ✖ | Availability | CR On toggle |
Currently, Contact Center does not do compliance checks for manual outbound calls. This means that when an agent dials an outbound call from the agent application, Contact Center does not check Do Not Call lists, time zone restrictions, or do other compliance-related verifications. In this release, you will be able to have these compliance checks performed for manual outbound calls. If the call violates a compliance check, the system will not place the call.
To use this option, you must have Outbound Engagement (SmartReach). You will need to configure the compliance rules in the Outbound Engagement (SmartReach) application.
| Customer Request | ✓ | UI Change | ✖ | Availability | GA On toggle |
Currently, managers who identify agent performance gaps on the Agent Performance Variance page must manually switch to the Coaching application and re-enter the agent and sub-topic details to initiate a coaching session. There is no direct link between the two surfaces, which introduces friction and risks losing context during the hand off.
In this release, you will be able to launch a coaching session directly from the Agent Performance Variance page, with the relevant agent and sub-topic context pre-filled in the Coaching application. This removes the need to switch tools or re-enter information manually. You will be able to:
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
In this release, Actions will be available in the UK Sovereign Cloud environment (UK2), extending regional coverage to customers operating under UK sovereign data residency and compliance requirements. No customer action is required to benefit from this expansion.
| Customer Request | ✖ | UI Change | ✖ | Availability | GA On deploy |
Currently, Data Conversation in Actions supports natural language queries across a set of available data domains, but Quality Management Autoscore data is not included. Managers who need Autoscore insights must navigate separate quality dashboards to find and interpret scoring results.
In this release, you will be able to ask plain-language questions about Quality Management Autoscore data directly within the Data Conversation experience in Actions, without leaving the interface or switching dashboards. You will be able to:
This feature will be available later in the release cycle.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
Currently, the Automation Opportunities and Augmentation Opportunities dashboards display data aggregated across the entire business unit, with no way to isolate results for a specific campaign or brand. Contact centers that manage multiple brands within a single business unit cannot distinguish which brand's interactions are driving specific opportunities.
In this release, you will be able to filter both the Automation Opportunities and Augmentation Opportunities dashboards by campaign, giving you a focused view of opportunities scoped to a specific brand or campaign. You will be able to:
This feature will be available later in the release cycle.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
Currently, Actions maintains conversation history for every user interaction and maps business data attributes that may contain personally identifiable information such as email addresses and phone numbers. There is no automated mechanism to process GDPR Article 17 Right-to-Erasure requests within Actions, meaning data removal must be handled outside the application.
In this release, you will be able to process GDPR deletion requests through Actions automatically, ensuring that patron data stored across conversation history and associated data stores is erased completely in response to a Right-to-Erasure request. You will be able to:
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
Currently, the Observability Dashboard does not apply data restrictions in its initial release. All users with access to the dashboard can view all data across the Copilot dashboard, Autopilot, AI Agents (Cognigy) for Process Automation (Task Assist), and business impact metrics, regardless of their team or skill assignments in User Hub.
In this release, you will be able to assign Global Views to users in User Hub, restricting their visibility in the Observability Dashboard to data associated only with their authorized teams or skills. You will be able to:
Access changes made in User Hub may take up to 15 minutes to be reflected in the Observability Dashboard due to data caching. When a user is assigned multiple Global Views, their combined scope across all views is applied.
| Customer Request | ✖ | UI Change | ✖ | Availability | GA On deploy |
We will soon improve security for Login Authenticator certificates by adding strict validation checks. The system will now only accept valid PEM‑encoded X.509 certificates that use strong encryption, such as RSA 2048-bit or higher and SHA‑256 or better. It will also check for problems like expired certificates, wrong formats, or weak encryption. If there are any issues, it will show clear error messages so they can be fixed easily. This update will help prevent security risks and make sure only safe and secure certificates are used.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On toggle |
The Division Management page will soon have improvements to make it easier for administrators to organize and find resources. You will be able to sort your division list by the Parent Division column. This will give you a clearer view of your Division structure.
New filters for Division Type and Billing Code will also be available. These filters will help you quickly find what you need by enabling faster searches and better grouping of results. These changes will reduce manual work and make Division Management easier to use.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On toggle |
NiCE CXone will extend Divisions to include Locations. This will let administrators link Locations to specific Divisions for better visibility and access control. You will be able to assign Division to Locations when creating them. Existing Locations will be automatically placed in the Default Division. For added security, each Location will be allowed to move only once from the Default Division to another Division.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
The hire date field will become optional in the bulk upload CSV, preventing incorrect default values when no date is provided. If left blank, the system will automatically assign the current date, improving data accuracy.
| Customer Request | ✖ | UI Change | ✖ | Availability | GA On deploy |
CXone will log enable and disable actions for impersonation in the Tenant Audit log, including who made the change and when. This improves traceability and supports compliance by providing clear visibility into impersonation activity.
| Customer Request | ✖ | UI Change | ✖ | Availability | GA On deploy |
Tenant Manager will now support role-based visibility for service accounts, allowing administrators to hide them from most users. This improves user management clarity and enhances security by limiting exposure of non-human accounts.
| Customer Request | ✖ | UI Change | ✖ | Availability | GA On deploy |
The pages in the Admin application will include significant accessibility improvements designed to offer a smoother, more inclusive experience for users across a wide range of visual, motor, and cognitive needs.
| Customer Request | ✓ | UI Change | ✖ | Availability | GA On deploy |
Agent Workspace (Agent) will improve support for assistive technologies such as screen readers, speech-to-text tools, and keyboard navigation to deliver a more accessible, inclusive experience aligned with WCAG 2.2 AA.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
Agent Workspace (Agent) will add a Desktop Profiles setting for Digital channels that will let you choose whether agents see a confirmation prompt when closing a digital interaction. This will help you reduce extra clicks and optimize average handle time while keeping the confirmation safeguard available when needed.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
Agents will receive an alert when a voice call has been on hold for longer than a configured threshold. Administrators will configure this in Desktop Profiles by enabling a Hold Timer Alert and selecting the desired duration.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
Agent Workspace (Agent) will fully support an existing permission in Roles (Hide Caller Phone Number) that lets organizations control whether agents can see caller phone numbers. This setting will be enforced consistently at runtime across relevant Agent views to support privacy-sensitive and public-safety environments.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
Agent Workspace (Agent) will help prevent one-way audio during voice calls by attempting to switch to the next available audio device if the agent’s primary headset or audio device disconnects mid-call. If automatic failover cannot be applied, Agent Workspace (Agent) will provide an in-call option for agents to select an available input and output device.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On toggle |
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
| Customer Request | ✓ | UI Change | ✖ | Availability | GA On deploy |
| Customer Request | ✓ | UI Change | ✖ | Availability | GA On deploy |
Agents will be able to resize the Digital channel response area to make it larger or smaller as needed, providing more space when composing longer messages. This capability is already available for the email channel.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
The email reply bar will be updated so that both Reply and Reply All will automatically address the most recent patron in the conversation, instead of replying to the last message in the thread. Additionally, the Forward button will be removed from the email reply bar.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
For all existing digital channels that support agent-to-patron typing indicators, when agents use Quick Responses, patrons will be able to see typing indicators indicating the agent is actively working on a reply.
| Customer Request | ✓ | UI Change | ✖ | Availability | GA On deploy |
In the App Space and Left Menu, once the apps and their orders are pinned, agents’ preferences will persist even after clearing the browser cache and cookies.
| Customer Request | ✓ | UI Change | ✖ | Availability | GA On deploy |
Agents will be able to warm-transfer an active voice contact to another agent who is already on a call.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
When agents start a new manual outbound digital interaction, the system will create the contact/interaction immediately and update the agent.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
When agents make a manual outbound voice call using an Outbound Engagement skill, they will now be prompted to enter a customer ID and/or postal code when performing a redial from the Contact History app or making a callback on a voicemail contact. This will happen or not based on how administrators have configured Outbound Engagement.
| Customer Request | ✖ | UI Change | ✓ | Availability | CR Other |
The Quick Bar will default to the topmost configured app when agents have no active interactions, based on their configured navigation order. This will also happen when the agent logs in for the first time and no interactions are assigned. This update will help provide a more consistent landing experience.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On toggle |
Users will be able to control group management actions in Internal Chat through configurable role-based permissions. This update will allow organizations to restrict who can create, rename, or modify group memberships, ensuring that team structures remain aligned with organizational governance and operational policies.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
Users will be able to manage their Internal Chat experience with new notification preferences, including the ability to mute and unmute alerts. This feature will help agents reduce distractions and maintain focus during high-priority tasks by providing individual control over notification noise.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
The Conversations application will be rebranded as Internal Chat and feature an updated icon for a more intuitive user experience. Additionally, you will be able to share larger files, with the cumulative file size limit increasing to 100 MB per message.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
Agent Workspace (Embedded) (Agent Embedded) will improve support for assistive technologies such as screen readers, speech-to-text tools, and keyboard navigation to deliver a more accessible, inclusive experience aligned with WCAG 2.2 AA.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
Agent Workspace (Embedded) (Agent Embedded) will add a Desktop Profiles setting for Digital channels that will let you choose whether agents see a confirmation prompt when closing a digital interaction. This will help you reduce extra clicks and optimize average handle time while keeping the confirmation safeguard available when needed.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
Agents will receive an alert when a voice call has been on hold for longer than a configured threshold. Administrators will configure this in Desktop Profiles by enabling a Hold Timer Alert and selecting the desired duration.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
Agent Workspace (Embedded) (Agent Embedded) will fully support an existing permission in Roles (Hide Caller Phone Number) that lets organizations control whether agents can see caller phone numbers. This setting will be enforced consistently at runtime across relevant Agent views to support privacy-sensitive and public-safety environments.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
Agent Workspace (Embedded) (Agent Embedded) will help prevent one-way audio during voice calls by attempting to switch to the next available audio device if the agent’s primary headset or audio device disconnects mid-call. If automatic failover cannot be applied, Agent Workspace (Embedded) (Agent Embedded) will provide an in-call option for agents to select an available input and output device.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On toggle |
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
| Customer Request | ✓ | UI Change | ✖ | Availability | GA On deploy |
| Customer Request | ✓ | UI Change | ✖ | Availability | GA On deploy |
Agents will be able to resize the Digital channel response area to make it larger or smaller as needed, providing more space when composing longer messages. This capability is already available for the email channel.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
The email reply bar will be updated so that both Reply and Reply All will automatically address the most recent patron in the conversation, instead of replying to the last message in the thread. Additionally, the Forward button will be removed from the email reply bar.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
For all existing digital channels that support agent-to-patron typing indicators, when agents use Quick Responses, patrons will be able to see typing indicators indicating the agent is actively working on a reply.
| Customer Request | ✓ | UI Change | ✖ | Availability | GA On deploy |
In the App Space and Left Menu, once the apps and their orders are pinned, agents’ preferences will persist even after clearing the browser cache and cookies.
| Customer Request | ✓ | UI Change | ✖ | Availability | GA On deploy |
Agents will be able to warm-transfer an active voice contact to another agent who is already on a call.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
Agents will be able to warm-transfer an active voice contact to another agent who is already on a call.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
When agents make a manual outbound voice call using an Outbound Engagement skill, they will now be prompted to enter a customer ID and/or postal code when performing a redial from the Contact History app or making a callback on a voicemail contact. This will happen or not based on how administrators have configured Outbound Engagement.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
The Quick Bar will default to the topmost configured app when agents have no active interactions, based on their configured navigation order. This will also happen when the agent logs in for the first time and no interactions are assigned. This update will help provide a more consistent landing experience.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On toggle |
Agent Workspace for Microsoft Teams (Agent for Microsoft Teams) will generate a single Voice Biometrics verification pop-up at the appropriate time, instead of opening multiple duplicate pop-up windows during and after a call.
| Customer Request | ✓ | UI Change | ✖ | Availability | GA On deploy |
Agent Workspace for Microsoft Teams (Agent for Microsoft Teams) will improve support for assistive technologies such as screen readers, speech-to-text tools, and keyboard navigation to deliver a more accessible, inclusive experience aligned with WCAG 2.2 AA.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
Agent Workspace for Microsoft Teams (Agent for Microsoft Teams) will generate a single Voice Biometrics verification pop-up at the appropriate time, instead of opening multiple duplicate pop-up windows during and after a call.
| Customer Request | ✓ | UI Change | ✖ | Availability | GA On deploy |
Agents will receive an alert when a voice call has been on hold for longer than a configured threshold. Administrators will configure this in Desktop Profiles by enabling a Hold Timer Alert and selecting the desired duration.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
Agent Workspace for Microsoft Teams (Agent for Microsoft Teams) will fully support an existing permission in Roles (Hide Caller Phone Number) that lets organizations control whether agents can see caller phone numbers. This setting will be enforced consistently at runtime across relevant Agent views to support privacy-sensitive and public-safety environments.
| Customer Request | ✓ | UI Change | ✖ | Availability | GA On deploy |
Agent Workspace for Microsoft Teams (Agent for Microsoft Teams) will help prevent one-way audio during voice calls by attempting to switch to the next available audio device if the agent’s primary headset or audio device disconnects mid-call. If automatic failover cannot be applied, Agent Workspace for Microsoft Teams (Agent for Microsoft Teams) will provide an in-call option for agents to select an available input and output device.
| Customer Request | ✓ | UI Change | ✖ | Availability | GA On toggle |
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
| Customer Request | ✓ | UI Change | ✖ | Availability | GA On deploy |
| Customer Request | ✓ | UI Change | ✖ | Availability | GA On deploy |
Agents will be able to resize the Digital channel response area to make it larger or smaller as needed, providing more space when composing longer messages. This capability is already available for the email channel.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
The email reply bar will be updated so that both Reply and Reply All will automatically address the most recent patron in the conversation, instead of replying to the last message in the thread. Additionally, the Forward button will be removed from the email reply bar.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
For all existing digital channels that support agent-to-patron typing indicators, when agents use Quick Responses, patrons will be able to see typing indicators indicating the agent is actively working on a reply.
| Customer Request | ✓ | UI Change | ✖ | Availability | GA On deploy |
In the App Space and Left Menu, once the apps and their orders are pinned, agents’ preferences will persist even after clearing the browser cache and cookies.
| Customer Request | ✓ | UI Change | ✖ | Availability | GA On deploy |
Agents will be able to warm-transfer an active voice contact to another agent who is already on a call.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
When agents start a new manual outbound digital interaction, the system will create the contact/interaction immediately and update the agent.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
When agents make a manual outbound voice call using an Outbound Engagement skill, they will now be prompted to enter a customer ID and/or postal code when performing a redial from the Contact History app or making a callback on a voicemail contact. This will happen or not based on how administrators have configured Outbound Engagement.
The Quick Bar will default to the topmost configured app when agents have no active interactions, based on their configured navigation order. This will also happen when the agent logs in for the first time and no interactions are assigned. This update will help provide a more consistent landing experience.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On toggle |
Currently, agents using the CXone Agent Application for Salesforce Voice may need to access external CXone interfaces to listen to customer voicemail messages, creating workflow fragmentation and increasing handling time.
In this release, agents will be able to play back customer voicemail recordings directly within the Salesforce. Voicemail interactions will appear alongside other voice and digital interactions, enabling agents to access voicemail messages, review customer requests, and initiate follow-up actions such as returning calls or creating cases all without leaving Salesforce.
This feature streamlines the agent workflow by eliminating the need to switch between applications, reducing average handling time, improving agent productivity, and delivering a unified interaction management experience within a single interface.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
Currently, CXone Mpower Agent for Salesforce Voice supports only voice interactions in the Salesforce Omni-Channel widget. In this release, NiCE digital channel messaging will be added to the Enhanced Omni-Channel widget. The CXone routing engine will route all digital interactions to agents alongside voice, allowing them to view, accept, and handle every channel type from a single interface.
Supported NiCE Digital Channels:
This feature eliminates the need to switch between separate tools for voice and digital channels, reducing handle time and enabling agents to serve customers across channels from a single workspace.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
Agents will be able to receive and handle Salesforce Cases, as well as Email-to-Case interactions, routed through the CXone routing engine directly within the CXone Agent for Salesforce Voice Omnichannel widget.
Once a Salesforce Case is created and routed through external routing to NICE, it will leverage NICE Unified Routing to intelligently assign the case to the appropriate agent.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
Agent Workspace (Browser Extension) (Agent Integrated) will improve support for assistive technologies such as screen readers, speech-to-text tools, and keyboard navigation to deliver a more accessible, inclusive experience aligned with WCAG 2.2 AA.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
Agent Workspace (Browser Extension) (Agent Integrated) will add a Desktop Profiles setting for Digital channels that will let you choose whether agents see a confirmation prompt when closing a digital interaction. This will help you reduce extra clicks and optimize average handle time while keeping the confirmation safeguard available when needed.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
Agents will receive an alert when a voice call has been on hold for longer than a configured threshold. Administrators will configure this in Desktop Profiles by enabling a Hold Timer Alert and selecting the desired duration.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
Agent Workspace (Browser Extension) (Agent Integrated) will fully support an existing permission in Roles (Hide Caller Phone Number) that lets organizations control whether agents can see caller phone numbers. This setting will be enforced consistently at runtime across relevant Agent views to support privacy-sensitive and public-safety environments.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
Agent Workspace (Browser Extension) (Agent Integrated) will help prevent one-way audio during voice calls by attempting to switch to the next available audio device if the agent’s primary headset or audio device disconnects mid-call. If automatic failover cannot be applied, Agent Workspace (Browser Extension) (Agent Integrated) will provide an in-call option for agents to select an available input and output device.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On toggle |
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
| Customer Request | ✓ | UI Change | ✖ | Availability | GA On deploy |
| Customer Request | ✓ | UI Change | ✖ | Availability | GA On deploy |
Agents will be able to resize the Digital channel response area to make it larger or smaller as needed, providing more space when composing longer messages. This capability is already available for the email channel.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
The email reply bar will be updated so that both Reply and Reply All will automatically address the most recent patron in the conversation, instead of replying to the last message in the thread. Additionally, the Forward button will be removed from the email reply bar.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
For all existing digital channels that support agent-to-patron typing indicators, when agents use Quick Responses, patrons will be able to see typing indicators indicating the agent is actively working on a reply.
| Customer Request | ✓ | UI Change | ✖ | Availability | GA On deploy |
In the App Space and Left Menu, once the apps and their orders are pinned, agents’ preferences will persist even after clearing the browser cache and cookies.
| Customer Request | ✓ | UI Change | ✖ | Availability | GA On deploy |
Agents will be able to warm-transfer an active voice contact to another agent who is already on a call.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
When agents start a new manual outbound digital interaction, the system will create the contact/interaction immediately and update the agent.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
When agents make a manual outbound voice call using an Outbound Engagement skill, they will now be prompted to enter a customer ID and/or postal code when performing a redial from the Contact History app or making a callback on a voicemail contact. This will happen or not based on how administrators have configured Outbound Engagement.
The Quick Bar will default to the topmost configured app when agents have no active interactions, based on their configured navigation order. This will also happen when the agent logs in for the first time and no interactions are assigned. This update will help provide a more consistent landing experience.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On toggle |
Agent Workspace Advanced (Enhanced Customer Card) will soon support up to 50,000 named agents and 18,000 concurrent agents within a single tenant. This update will ensure high performance and responsiveness across all workflows, maintaining search latencies under two seconds for common queries even at maximum scale.
| Customer Request | ✖ | UI Change | ✖ | Availability | GA On deploy |
The Agent Workspace Advanced (Enhanced Customer Card) will soon be updated to align with WCAG 2.2 AA standards, ensuring a more inclusive and accessible experience for all agents. This enhancement will focus on improving navigation and usability for users who rely on assistive technologies.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
The Customer, Account, and Ticket list components will include three system-defined default views: Recently Viewed, All Records, and Assigned to Me. These standardized views will provide a more consistent and intuitive navigation experience by replacing fragmented settings with clearly visible, out-of-the-box options.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
Administrators will soon be able to restrict the scope of advanced searches to only the records within an agent's assigned View for Customers, Tickets, and Accounts. This feature will ensure that agents can only query and retrieve data they are authorized to see based on their specific View assignments.
| Customer Request | ✖ | UI Change | ✖ | Availability | GA On deploy |
Agent Workspace Advanced (Enhanced Customer Card) will soon include a dedicated Studio Features component that displays dynamic data directly from Studio Scripts. This feature will allow agents to view real-time, formatted information, such as custom text and color-coded alerts triggered by specific actions like answering, holding, or transferring calls.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
Agents will soon be able to manually link active interactions to specific tickets in Agent Workspace Advanced (Enhanced Customer Card) using a new Link Contact button. This feature will allow for more flexible record-keeping by enabling a single interaction to be associated with multiple tickets without requiring a save or update event.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
The Agent Desktop and Agent Portal will soon support up to 40 million customer records within Customer Manager (Contact Manager). This enhancement will ensure that searching, filtering, and data retrieval remain efficient and reliable even at significantly higher data volumes.
| Customer Request | ✓ | UI Change | ✖ | Availability | GA On deploy |
The Designer interface will be redesigned to migrate to a modern UI framework and simplify the configuration process for Agent Workspace Advanced (Enhanced Customer Card).
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
Agent Workspace Advanced (Enhanced Customer Card) will soon support all languages available in the standard Agent Workspace application, automatically detecting and applying the language based on your browser settings. However, Agent Workspace Advanced (Enhanced Customer Card) are not available in certain regions.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
To provide a more seamless and unified administrative experience, the Designer Builder interface will be integrated directly into the CXone User Hub. The integration will include the Designer Builder within the standard CXone menu structure, ensuring that all menu items and navigation paths are clearly displayed and easily accessible from a single location.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
The Agent Workspace Premium (Desk) will soon be updated to align with WCAG 2.2 AA standards, ensuring a more inclusive and accessible experience for all agents. This enhancement will focus on improving navigation and usability for users who rely on assistive technologies.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
The Customer, Account, and Ticket list components will include three system-defined default views: Recently Viewed, All Records, and Assigned to Me. These standardized views will provide a more consistent and intuitive navigation experience by replacing fragmented settings with clearly visible, out-of-the-box options.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
Administrators will soon be able to restrict the scope of advanced searches to only the records within an agent's assigned View for Customers, Tickets, and Accounts. This feature will ensure that agents can only query and retrieve data they are authorized to see based on their specific View assignments.
| Customer Request | ✖ | UI Change | ✖ | Availability | GA On deploy |
Agent Workspace Premium (Desk) will soon include a dedicated Studio Features component that displays dynamic data directly from Studio Scripts. This feature will allow agents to view real-time, formatted information, such as custom text and color-coded alerts triggered by specific actions like answering, holding, or transferring calls.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
Agents will soon be able to manually link active interactions to specific tickets in Agent Workspace Premium (Desk) using a new Link Contact button. This feature will allow for more flexible record-keeping by enabling a single interaction to be associated with multiple tickets without requiring a save or update event.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
The Agent Desktop and Agent Portal will soon support up to 40 million customer records within Customer Manager (Contact Manager). This enhancement will ensure that searching, filtering, and data retrieval remain efficient and reliable even at significantly higher data volumes.
| Customer Request | ✓ | UI Change | ✖ | Availability | GA On deploy |
The Designer interface will be redesigned to migrate to a modern UI framework and simplify the configuration process for Agent Workspace Premium (Desk).
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
Agent Workspace Premium (Desk) will soon support all languages available in the standard Agent Workspace application, automatically detecting and applying the language based on your browser settings. However, Agent Workspace Premium (Desk) are not available in certain regions.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
To provide a more seamless and unified administrative experience, the Designer Builder interface will be integrated directly into the CXone User Hub. The integration will include the Designer Builder within the standard CXone menu structure, ensuring that all menu items and navigation paths are clearly displayed and easily accessible from a single location.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
A new high-performance API will be introduced that will let you retrieve Segment Ids directly and efficiently, even without Interaction Analytics. This update will enable you to pull up to 90 days of Segment Ids using simple filters like time ranges or specific agents. This ensures your external record-keeping is faster and more reliable than ever. Use the results from this new API to make requests to other APIs that require a single Segment Id.
| Customer Request | ✖ | UI Change | ✖ | Availability | GA On toggle |
Analytics Policies will give you total control over how transcription and AI insights are triggered for your interactions. You will be able to create custom profiles to apply advanced features like IA annotation, Enlighten CSAT, and Topic AI to specific interaction filters. Admins will be able to target specific teams, employees, call directions, and ACD skills when setting up Analytics Policies. A new, easy-to-use interface will allow you to quickly configure these rules and see exactly how many interactions each filter covers, thus ensuring your business receives the most relevant and actionable data.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On toggle |
Topic AI will adopt the NiCE AI C26 (Cognigy 2026) theme with a fully redesigned application layout aligned with all NiCE AI applications within CXone. The updated interface will include new fonts, color palette, updated box shapes, and refreshed icons. Color contrast will meet accessibility standards. Key layout changes will include:
This change will provide a consistent visual and navigational experience across all NiCE AI applications.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On toggle |
After enriching a Topic AI model, you will be able to view model coverage and accuracy metrics on a new Overview page. In addition, each category, topic, and subtopic will include an accuracy metric calculated by LLM as a judge. This will allow you to check accuracy at every level and take actions such as rename, remove, move, or merge topics accordingly . The Overview page will also highlight low-accuracy topics across all topic types and will provide direct links to the topic view for taking action. These enhancements will make it easier to see which topics are working well and which ones need more refinement.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On toggle |
Topic AI will support the following additional languages:
This update will include specialized handling for non-whitespace languages to ensure high accuracy and deeper insights across global conversations.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On toggle |
Topic AI will provide better coverage and accuracy across all topic types, including improved topic naming, automatic creation of new categories when required, and better topic granularity. These updates will help organize your data more effectively by creating specific new categories instead of grouping items under "Other."
| Customer Request | ✖ | UI Change | ✖ | Availability | GA On toggle |
The number of visible examples for each subtopic will increase from 5 to 50, allowing for a more thorough assessment of intents and actions. A new scrollable interface and prioritized high-impact sentences will help you quickly verify the accuracy of the topic.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On toggle |
Users will be able to use Topic AI independently from Interaction Analytics (CXone). To get started, you will need to:
This update will allow you to upload and enrich your AI models directly from Integration Hub, even without an Interaction Analytics (CXone) license. You will be able to filter and sample up to 40,000 interactions to improve your AI-driven insights using your own data.
The recommended filters are:
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On toggle |
Users will be able to lock critical L3 subtopics to prevent them from being changed or removed during model updates. This feature will also support allowing to lock topics related to holidays so they will be retained on the next enrichment cycle, even if those topics are not present in the new enrichment data. Visual indicators for locked items and new filtering options will help users easily manage and protect essential business topics.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On toggle |
Topic AI will include significant accessibility improvements designed to offer a smoother, more inclusive experience for users across a wide range of visual, motor, and cognitive needs.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On toggle |
The new Store & Forward (S&F) Generic Ingestion API will provide a standardized way for external recording and digital systems to bulk‑import closed interactions into Contact Center.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
The CSV file generated by the Data Extract API will include the telephony system name (such as Cisco, Avaya, or Genesys) for each interaction. This will help customers in Engagement Hub (Multi-ACD/Open) environments to easily identify, analyze, and troubleshoot interactions.
| Customer Request | ✖✓ | UI Change | ✓ | Availability | GA On deploy |
A new set of APIs will be added to the Developer Portal to help build and maintain integrations with Feedback Management. Users will be able to programmatically retrieve invitation and response data in bulk, as well as access survey metadata, reducing manual work and keeping reporting pipelines up to date automatically.
| Customer Request | ✓ | UI Change | ✖ | Availability | GA On deploy |
Developers will soon be able to easily download OpenAPI 3.0 specification files for NiCE CXone APIs directly from the Developer portal. A new Download button will be introduced on individual API pages, enabling users to quickly access official JSON specification files. These production-ready specs can be used to generate SDKs, streamline API testing, and keep integrations up to date with trusted definitions. To access a specific API, simply select it using the filter available in the top-right corner of the page.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On toggle |
The Analyzed Interaction Segments API will support filtering by Skill ID. This enhancement will allow developers to refine API requests by combining the skillId parameter with existing date filters, ensuring that only interaction segments associated with specific skills are retrieved.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On toggle |
Currently, the GET /final-summary API returns only the AI-generated conversation summary. When an agent edits the summary before disposition, that agent-verified version, which often reflects more accurate, contextually refined information is not accessible via any API endpoint. Downstream consumers such as CRM integrations, QA platforms, and reporting pipelines receive the raw AI output rather than the final human-verified version saved to the system of record.
In this release, you will be able to retrieve the agent-edited final summary through the new Agent-Edited Summary API. The API returns the agent-edited version when one exists.
| Customer Request | ✖ | UI Change | ✖ | Availability | GA On deploy |
Currently, Copilot is not initiated for Dialer Personal Connection calls. As a result, no AutoSummary is generated for these call types, even when the associated skills are part of an active Copilot profile. Agents handling outbound dialer calls must complete after-call work manually without AI-generated summaries.
In this release, Copilot will be initiated for Dialer Personal Connection calls when the associated skill is included in a Copilot profile. AutoSummary will be generated and available after the call in a manner consistent with inbound and contact-based interactions.
This feature will be available later in the release cycle.
| Customer Request | ✖ | UI Change | ✖ | Availability | GA On deploy |
In this release, you will be able to customize the LLM prompts used to generate Self-Service Summary through the GenAI Prompts. A new Self-Service category will be added to the GenAI Prompts with a Self-Service Summary sub-category, including a default prompt that you can modify to match your specific use case and language requirements. You will be able to:
The Self-Service category in GenAI Prompts is available to tenants licensed for Virtual Agent Hub or AI Agents (Cognigy).
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
In an upcoming release, Contact Center will introduce a new API to support Multi-Region Business Continuity Plan (Business Continuity Plan) and Disaster Recovery (DR). This API will allow organizations to automatically enable or disable Multi-Region Business Continuity Plan (Business Continuity Plan) tenants, helping them respond faster during outages without manual steps. This will make failover and failback quicker and more controlled. To use this feature, a Programmatic Connect license will be required, and full API details will be available on the DEVone portal.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On toggle |
Currently, a Contact Center account representative must generate a passkey and give it to the administrator when setting up Multi-Region Business Continuity Plan (Business Continuity Plan). The administrator must enter the passkey to switch between the primary and secondary Multi-Region BCP tenants. This process is cumbersome and time consuming.
In this release, switching to the secondary tenant will no longer require a passkey. Instead, a confirmation warning will appear when switching between the secondary and primary tenants. The administrator must confirm before the switch occurs. Additionally, a new permission will be required for any role that is allowed to switch between Multi-Region BCP tenants. Together, these changes will simplify switching between tenants while still preventing accidental changes.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On toggle |
Managing your Disaster Recovery (DR) environment will become simpler and more secure. In this release, a status-first filtering experience will be introduced on the Sync Dashboard. This update will allow you to quickly identify problematic entities. To prevent accidental data overrides, manual synchronization will be limited to Failed entities only. You will also be able to multi-select and bulk-sync failed entities, helping reduce remediation time.
Pagination will be introduced to handle large datasets efficiently, while the UI will be simplified to display key details upfront. Version details will be moved to a pop-up view, and date formatting will be enhanced for improved readability. These enhancements will ensure a more focused, efficient, and secure workflow for Customer Admins during DR onboarding and failover readiness.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On toggle |
To ensure that your Multi-Region BCP tenant stays up to date, you will be able to sync data from your primary to Multi-Region BCP tenant. This will also prevent you from manually managing two tenants. However, not everything from your primary system will be synced.
In an upcoming release, support will be added for Standard Address Book, Personal Connection, and Voice Manual Outbound. These features will be enabled, and their related entities will be automatically synchronized with the secondary region.
| Customer Request | ✓ | UI Change | ✖ | Availability | GA On deploy |
Currently, when scripts are synced from the primary tenant to the secondary Multi-Region BCP tenant, they must be manually edited to change IDs for entities such as ACD skills. This is because the same entities have different IDs on each tenant, so to make sure that scripts work properly on the Multi-Region BCP tenant, they must reference the correct IDs for that tenant.
In this release, you will be able to use Studio dictionaries to map references to entities in each tenant. This will mean that you no longer need to manually edit scripts on your Multi-Region BCP tenant. The system will split scripts and files into smaller batches and process them at the same time to avoid timeouts, even for up to 50,000 items. The new approach will solve this by handling work in smaller parts. It will also retry failed batches automatically and show issues in the sync dashboard.
Script changes will be required to use Studio dictionaries. You will need to replace any reference to specific entities such as ACD skills with dictionary-based references.
| Customer Request | ✓ | UI Change | ✖✓ | Availability | GA On toggle |
In the upcoming release, Engagement Hub (Multi-ACD/Open) will support Disaster Recovery (DR) and Multi-Region BCP by automatically syncing recording configuration data across AWS regions. Key elements like Telephony Systems, Interfaces, Device Groups, and Devices will be copied to a secondary region every 24 hours to ensure readiness during outages. In a failover situation, systems will be quickly activated with minimal manual effort to maintain recording operations. The feature will also maintain data consistency across regions and will require a Multi-Region BCP DR license to be enabled.
| Customer Request | ✓ | UI Change | ✖ | Availability | GA On toggle |
In this release, administrators will be able to enable or disable 3rd-party telephony systems directly from the Contact Center Admin interface using a simple toggle button. This will help during onboarding, maintenance, and Disaster Recovery (DR) scenarios by keeping systems inactive and in standby until fully configured. When disabled, the CTI will not connect, reducing errors and noise. The interface will display clear status indicators and confirmation prompts. Administrators will still be able to manage and update configurations even when systems are disabled. All changes will be logged for auditing. This feature will support the integrations with Cisco, Avaya, Genesys, Aspect, and POM.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On toggle |
The Coaching Transactional Report will soon be upgraded to support multiple focus areas and behaviors within a single session. This update will automatically list each unique focus area-behavior pair in its own row, ensuring every part of your coaching is accurately tracked and visible. You will be able to filter and export these detailed records without losing any data, while your existing single-focus session reports will remain fully compatible. These changes will also improve the accuracy of your completion and acknowledgment metrics, giving you a more precise view of your team's development.
This feature will be available for users with the Quality Management (CXone) license.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On toggle |
NiCE CXone Coaching will include significant accessibility improvements designed to offer a smoother, more inclusive experience for users across a wide range of visual, motor, and cognitive needs.
| Customer Request | ✓ | UI Change | ✖ | Availability | GA On deploy |
Basic native Speech-to-Text (STT) and Text-to-Speech (TTS) services will be integrated directly into voice-enabled AI Agents (Cognigy). This enhancement will provide built-in voice capabilities, eliminating the need for additional service configuration and enabling you to deliver seamless voice interactions more efficiently. For advanced use cases, Bring Your Own (BYO) and Premium speech services will also be available.
| Customer Request | ✖ | UI Change | ✖ | Availability | GA On deploy |
Premium Speech-to-Text (STT), Text-to-Speech (TTS), and Large Language Model (LLM) services will be available through Contact Center. When using these services, you will not need to configure or manage provider-specific API keys. Instead, you will be able to select the desired Contact Center- provided premium service from the relevant configuration menus. A new billing and management experience will provide visibility into premium service usage and costs. The platform will automatically track service consumption, calculate associated charges, and include them in your billing.
| Customer Request | ✖ | UI Change | ✖ | Availability | GA On deploy |
You will be able to deploy AI Agents (Cognigy) services in South Africa region to support data residency and compliance requirements.
| Customer Request | ✖ | UI Change | ✖ | Availability | GA On deploy |
Multi-Region Storage (MRS) rules will now include Automatic Number Identification (ANI) as a filter. This will mean admins will be able to control where outbound interactions are stored based on the agent’s phone number (ANI). Previously, this was only possible for inbound calls using DNIS. The same logic and validations will now apply to ANI, which will make it easy to configure. This update will help large organizations manage and resolve the storage location better, while still following the limit of 10 rules per file type for each Business Unit.
This feature will be available for users with Multi-Region Storage enabled in Tenant Management.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On toggle |
The system could not handle large number of requests efficiently. Because of this, the retrieval page would freeze. This caused business problems, as customers were not able to create new retrieval requests until the old ones were archived.
In the upcoming release, the long-term retrieval page will be upgraded by adding pagination to help manage large lists of data more easily. Continuous scrolling and automatic sorting in descending order of request date will also be introduced, ensuring that the newest requests always appear at the top of the list for faster access.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On toggle |
Currently, autofill is limited to the initial Copilot starter form. Once a workflow transitions into AI Agents (Cognigy)-authored forms, agents must manually enter values even if that information already exists in the system or appears later in the conversation.
In this release, you will be able to automatically prefill fields in AI Agents (Cognigy) authored adaptive cards using information available in the conversation context. Copilot evaluates available data sources and populates form fields at render time and progressively as new information becomes available during the interaction. You will be able to:
This feature applies to all standard field types including text, numeric, date and time, dropdown, checkbox, and radio. Prefilled fields are visually distinguished in the form to help you quickly identify auto-populated values from manually entered ones.
This feature will be available later in the release cycle.
| Customer Request | ✖ | UI Change | ✖ | Availability | GA On deploy |
In this release, you will be able to use AI Agents (Cognigy) for Process Automation (Task Assist) workflows in Copilot for Agents in Engagement Hub environments that do not use Studio. This allows agents working on Engagement Hub to invoke AI Agents (Cognigy) based workflows from the AI Agents (Cognigy) for Process Automation (Task Assist) panel, including API lookups using customer data such as the calling number.
This feature enables Engagement Hub customers to benefit from guided workflow automation within Copilot without requiring a Studio dependency. Customer metadata from Engagement Hub is passed into Copilot at interaction time so workflows have the context they need to operate.
This feature will be available later in the release cycle.
| Customer Request | ✖ | UI Change | ✖ | Availability | GA On deploy |
In this release, you will be able to temporarily delegate part of a digital interaction to an AI Agent to complete routine tasks such as collecting structured information, guiding the customer through troubleshooting steps, or executing step-based procedures. While the AI Agent handles the delegated task, you can observe the conversation in real time and take control at any moment. You will be able to:
When the AI Agent completes the delegated task or is unable to continue, conversation control automatically returns to you with a confirmation notification. If the customer becomes inactive during AI interaction, the delegated session times out and control returns to the agent. The AI Agent makes up to three collection attempts per required field before escalating.
This feature will be available later in the release cycle
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
Currently, workflows execute sequentially within Copilot. When a workflow is active, other workflows must wait until the current one completes. This prevents supporting workflows from running alongside the primary workflow and delays backend automation tasks that could otherwise execute in parallel.
In this release, you will be able to run multiple workflows concurrently within the same customer interaction. Workflows that require your input are displayed as dedicated tabs within the AI Agents (Cognigy) for Process Automation (Task Assist) panel, and you can switch between them at any time and complete tasks in any order. You will be able to:
Administrators can configure the maximum number of workflows that may run concurrently. When the limit is reached, additional workflows are queued and promoted automatically when capacity becomes available. Queued workflows can be removed at any time.
This feature will be available later in the release cycle.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
In this release, there are new settings to refine how advanced rules behave during interactions. You will be able to:
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
In this release, you will be able to display richly formatted content in Custom Cards using Adaptive Card rendering. Custom Cards will support bold, italic, underline, strikethrough, hyperlinks, bullet lists, numbered lists, and color and size variations — making it significantly easier for agents to scan and act on knowledge article content. You will be able to:
This feature uses the Adaptive Card framework already in use for workflow forms and cards. Formatting is applied by configuring the JSON payload that drives the card, giving administrators full control over how card content is presented to agents.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
Currently, administrators and prompt engineers configure prompts and Copilot behaviors in AI Studio but have no native way to validate those configurations before deploying to a live environment.
In this release, you will be able to test your Copilot configuration directly within AI Studio using a native Copilot Simulator. A collapsible Simulator panel opens alongside the AI Studio editor and provides a high-fidelity sandbox for validating prompt changes without requiring a deployment. You will be able to:
All actions in the Simulator are isolated from production data and systems. Simulated workflows do not execute live API calls, and no changes are written to production databases during testing.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
Currently, a Copilot for Agents profile can only be assigned to an ACD skill as a whole, meaning every agent working that skill automatically uses the same profile. There is no way to assign a profile to a subset of agents within a skill.
In this release, you will be able to assign Copilot for Agents profiles at two levels of granularity: to all agents in a skill, or to specific agents within a skill. This gives you precise control over which agents receive AI-assisted Copilot guidance without affecting others working the same queue. You will be able to:
This feature is designed for phased Copilot rollouts, pilot programs, and scenarios where agents in the same skill queue need different Copilot configurations. The same skill can appear in multiple profiles with non-overlapping agent lists. All assignment changes are recorded in the audit log.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
Currently, there is no way to duplicate or clone an existing Copilot for Agents profile. Creating a new profile that is similar to an existing one requires manually recreating every configuration setting from scratch, which is time-consuming as profiles grow more complex.
In this release, you will be able to duplicate any existing Copilot for Agents or AI Profile with a single action. The duplicate is created as a new, independent profile with all configured settings copied under a name you provide. You can then modify the duplicate without affecting the original profile.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
Currently, skill assignments to AI Profiles must be managed individually within the Assignments tab. For tenants with hundreds or thousands of skills, manually assigning skills to profiles is time-intensive and error-prone.
In this release, you will be able to export existing skill assignments from a Copilot for Agents profile as an Excel or CSV file, and import skill assignments in bulk from a file. You will be able to:
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
In this release, you will be able to enable a Hide Copilot for Agent setting in the AI Studio Profile that suppresses the CopilotUI entirely while Copilot continues to run in the background. All configured features such as AutoSummary, custom LLM prompts, and background workflows will continue to operate normally. The Copilot panel simply will not be displayed to the agent and AutoSummary content will not be sent into the Agent Workspace > Outcome Panel > Disposition Notes field.
This setting is useful when Copilot outputs are intended for managerial assessment of Copilot, supervisors, downstream systems, or reporting pipelines rather than the agent directly. Enabling it does not affect any background feature, and all applicable usage fees apply regardless of whether the panel is visible.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
In this release, you will be able to configure Copilot for Agents profiles and GenAI Prompts to output in 12 additional language and location combinations, extending Copilot’s reach to more regions and customer populations. The new languages available are:
These languages are available in the AI Studio Profile language selector and across all customizable prompt categories in GenAI Prompts, including AutoSummary, Realtime Summary, Realtime Sentiment, Journey Summary, KB Answer, and Customer Prompt categories. Location-specific language combinations are also added to the GenAI Prompts.
| Customer Request | ✖ | UI Change | ✖ | Availability | GA On deploy |
Copilot for Agents for email was initially released in Controlled Release with limited functionality available only with direct Expert deployments. The current implementation does not support Knowledge Hub response generation, and does not support AutoSummary, Realtime Summary, or Realtime Sentiment for email interactions.
In this release, you will be able to configure and use the full range of Copilot AI features for email interactions, including topic extraction and response generation using Knowledge Hub content, AutoSummary, Realtime Summary, and Realtime Sentiment. You will be able to:
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
Currently, the real-time transcript of a voice call is used by Copilot internally to generate suggestions, but the transcript itself is not displayed to the agent in the Copilot UI. Agents using Engagement Hub environments have no way to view the live transcript within Copilot.
In this release, you will be able to enable a real-time transcript view in Copilot for Agents, primarily for Engagement Hub deployments. When enabled in the Copilot profile, a transcript icon-button appears on the Copilot toolbar. Clicking it opens a dedicated Transcript page that displays utterances as they are captured during the call, labeled by participant.
You will be able to view the live transcript during an active call without leaving the Copilot panel. The transcript display is consistent with the format used in Agent Workspace (Agent), providing a familiar experience across tools.
The Show Transcript setting is configured in the Copilot for Agents profile under the General tab and applies to the voice channel only.
This feature will be available later in the release cycle.
| Customer Request | ✓ | UI Change | ✖ | Availability | GA On deploy |
Currently, there is no cap on how many rules can trigger during a single interaction. All matching rules fire simultaneously regardless of volume, and there is no way to prioritize which rules take precedence when multiple rules match at the same time.
In this release, you will be able to configure two new controls on the Copilot for Agents profile Rules tab to manage how many rules fire during a single interaction and which rules take precedence when multiple rules match simultaneously. You will be able to:
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
Currently, rules can only be triggered by keywords or phrases and by intent detection. There is no way to trigger a rule based on what happens during the operational lifecycle of an interaction, such as when a call starts or ends.
In this release, you will be able to configure rules that trigger based on interaction lifecycle events in addition to utterance-based triggers. This allows you to launch checklists, decision trees, or automated workflows at precisely the right moment in an interaction. Supported interaction events include:
Interaction event triggers are configured from the rule creation page using a dedicated Interaction Events trigger type. They work within the existing conditions and actions framework and have no impact on existing keyword or intent-based rules.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
Currently, Decision Trees are triggered directly from the Copilot interface without involvement of the Rules. This limits flexibility and means Decision Trees cannot be invoked conditionally based on conversation signals — unlike Text Cards, which can already be triggered through rules.
In this release, you will be able to configure a Decision Tree as a linked action in the Rules. When the rule’s conditions are met, the selected Decision Tree is automatically triggered and rendered to the agent without any manual action required.
This feature brings Decision Trees into the Rules Engine’s trigger-and-action framework, enabling them to launch automatically based on keywords, intent detection, or interaction lifecycle events depending on how the rule is configured.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
In this release, admins will be able to build Decision Trees faster by importing sections and fields in bulk from a CSV template, significantly reducing the time required to create large or complex trees. As an admin, you will be able to:
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
In this release, agents will be able to export completed Decision Trees as a PDF, making it easier to retain records, support audits, and hand completed workflows over to other teams. As an agent, you will be able to:
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
Urgent Assist detection will move to LLM via Prompt Manager, enabling multi language support. The Urgent Assist reason and interaction summary will be displayed in the language configured in the Copilot profile.
Supported languages will include Chinese Simplified (China), Chinese Traditional (China), Dutch (Netherlands), English (Australia), English (Canada), English (UK), English (US), Finnish (Finland), French (Canada), French (France), German (Germany), Italian (Italy), Japanese (Japan), Korean (South Korea), Norwegian (Norway), Portuguese (Brazil), Portuguese (Portugal), Spanish (Latin America), Spanish (Spain), Swedish (Sweden), Welsh (Wales).
When an Urgent Assist alert is triggered for a contact, any existing Negative Sentiment alert for the same contact will be automatically removed. The alert will include the Urgent Assist reason and a summary of the interaction when the Alert Insights permission is enabled.
This feature will require the Copilot for Supervisors license.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On toggle |
You will be able to generate an AI-powered real time summary for any active interaction directly from the Agent and Contact tabs. By selecting Generate Summary from the actions menu, the system will generate a summary of the conversation so you can quickly understand the context.
You will be able to configure the summary length as Short, Medium (Default) or Long - and it will be generated in the language set in your browser locale. A regenerate option will be available to fetch the latest summary at any time.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On toggle |
Copilot for Supervisors will support intent-based real-time alerts in addition to existing phrase-based alerts.
Admins will be able to configure rules based on customer intents, such as "Customer mentions legal action, lawyer involvement, or references ongoing litigation related to the product or service issue", with a defined confidence threshold, eliminating the need to manually specify every keyword variation manually. When a configured intent is detected in a customer's speech during a live interaction and meets the confidence threshold, an alert is triggered in real time, enabling supervisors to Monitor, Join, or Assist the interaction.
This feature requires Copilot for Supervisors, Copilot for Agents, and Rule engine license.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
Users will be able to export Ticket Search results data to csv or excel.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
You will be able to apply Global Filters at the dashboard level to update all compatible widgets at once. Widgets without compatible filters will remain unchanged, and data will not refresh.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
Dashboards will load the last 7 days of data up to 10x faster using a pre-calculated cache that refreshes every 15–30 minutes. You will be able to select a custom date range of up to the last 7 days, while today’s data remains unchanged.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
The Metrics Interval and KPI Trend widgets will support Historical metrics only. Real-time (NRT) and Snapshot metrics will no longer appear as selectable options.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
Metric Widgets will feature a guided configuration flow. Once you select at least one metric, Settings will unlock and display only options that are compatible with your metric selection.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
The Report widget will move to the Data Insights category, and the Metrics permission section in Admin settings will be renamed to Metrics & Reports for clear navigation and permission management.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
Guide metrics will migrate to a new data architecture, enabling consistent filtering and view-by granularity across all metrics.
| Customer Request | ✓ | UI Change | ✖ | Availability | GA On deploy |
When the Metrics Interval widget is set to hourly or minute-level intervals, the date will be displayed alongside the time for easier evaluation of multi-day trends.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
Generic Abandon metrics will be redefined to cover all abandon types—Short, Long, Prequeue, Held Party, Outbound, and Expired. You will see consistent count, time, average, and percentage metrics, along with an Abandon Type view-by option in widgets.
| Customer Request | ✓ | UI Change | ✖ | Availability | GA On deploy |
You will see two new standardized Voice transfer metrics available across voice and digital channels:
| Customer Request | ✖ | UI Change | ✖ | Availability | GA On deploy |
Four NRT Digital Experience (DX) contact metrics will return to the metric selector:
| Customer Request | ✖ | UI Change | ✖ | Availability | GA On deploy |
One operational metric will deliver consistent results across Agent and Skill views:
When interval-type widgets are set to hourly or minute-level intervals, the date will be displayed alongside the time for easier evaluation of multi-day trends.
| Customer Request | ✖ | UI Change | ✖ | Availability | GA On deploy |
The new Agent Variance widget will show a scatter plot of each agent’s Adherence % vs. Scheduled Time, color-coded by range with a median line to quickly identify outliers.
This feature requires a WFM license.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
The new Out-of-Adherence (OOA) Cause widget will use a treemap to reveal what agents were doing during out-of-adherence periods. Each segment will represent an activity, sized by occurrence count or percentage of OOA time, helping WFM Managers and Supervisors understand the drivers behind adherence deviations.
This feature requires a WFM license.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
Legacy report grids will be replaced with modern widgets for a consistent design, better performance, and improved usability.
This feature requires a WFM license.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
WFM Managers will be able to use metric widgets to view forecasted intraday data for future dates directly on the dashboard.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
The new Usage Report landing page will provide easy access to the following Usage and Billing reports:
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
The Last Login field will show an agent’s most recent login from the past 30 days. If no sessions are recorded within the 30-day window, you will see a null value instead of a misleading timestamp so activity can be tracked accurately.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
Updated permissions will allow Administrators to grant or restrict access to new ACD and QM reports.
| Customer Request | ✖ | UI Change | ✖ | Availability | GA On deploy |
The new Quality Plan Distribution Visibility Report will provide distribution insights at the plan, evaluator, and interaction levels, giving clear visibility into quality plan lifecycles, distribution behavior, and workload outcomes.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
The Activity, Entity, and Application filter fields will appear in Settings before you run the report. Filters will be applied to the initial report output, resulting in more efficient queries.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
Export limits for the Quality Evaluation and Report widgets will increase from 10,000 to 100,000 records, allowing you to export larger datasets in a single operation. Only one export will run at a time to prevent duplicates, and you will receive a notification if the data exceeds the export limit.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
You will see new Cognigy AI metrics on the dashboard. These metrics will help you monitor self-service performance and begin unifying AI and agent insights across Contact Center. More metrics will follow in later releases.
This feature requires a Cognigy AI Integration license.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
Automated inventory scanning, parity analysis, and user-initiated migration tools will allow users to scan, analyze, and migrate Legacy User Hub dashboards into Contact Center Dashboards with minimal effort.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
Analysts will be able to create and modify report templates, configure settings and filters, organize templates into categories, share with their team, export to Excel, PDF, or CSV, subscribe to scheduled delivery, and track all changes using Audit History.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
Contact Center Dashboards will include significant accessibility improvements designed to offer a smoother, more inclusive experience for users across a wide range of visual, motor, and cognitive needs.
| Customer Request | ✓ | UI Change | ✖ | Availability | GA On deploy |
CXone Data Share will include Cognigy AI interaction analytics, enabling you to access AI agent performance data directly in your Snowflake environment. New metrics will cover four key areas: Intent Analytics (Average Intent Score, Max Intent Score, Top Intents, Intents by Score Range), Goal & Task Performance (Completed, Partially Completed, and Incomplete Goals, Top Tasks Reached, Top Slots), Business Impact (Total Time Saved, Cost Savings, Revenue Earned — both aggregate and per goal), and Escalation & Containment (Handover Rate, Handovers by Time of Day, Average First Response Time, Average Resolution Time). This will be available for both CXone-routed and standalone Cognigy AI deployments with no changes to your existing Data Share setup.
| Customer Request | ✖ | UI Change | ✖ | Availability | GA On deploy |
Auto Score data from CXone Quality Management will be available through Snowflake Data Share.
Within Quality Management (QM) framework, automated scoring evaluates each interaction segment or ticket against defined scorecards, capturing overall quality outcomes to support performance tracking across the contact center. These results are further broken down by individual evaluation criteria — such as empathy or product knowledge — providing supervisors and quality analysts with granular insight into agent performance. Metadata associated with each interaction segment submitted for automated scoring is also retained, ensuring full traceability of the scoring process. Together, these data points drive quality management reporting, supervisor dashboards, and downstream analytics to continuously monitor and improve contact center performance.
| Customer Request | ✖ | UI Change | ✖ | Availability | GA On deploy |
CXone Recording customers will be able to access their interaction and segment metadata including segment identifiers, timestamps, interaction duration, channel, direction, recording status, hold details, disposition, business data tags, and recording alerts through CXone Data Share. Data Share will complement not replace the existing Data Extract API, and will cover interaction metadata only, not audio or screen recording media files.
| Customer Request | ✖ | UI Change | ✖ | Availability | GA On deploy |
Engagement dimension data, including call-to-action, engagement rule, and engagement type dimensions will be available directly in Suite Views. Visit Activity, Visit Conversion, and Visit Fact views will also be updated to include engagement level data.
You'll be able to analyze digital engagement data alongside visit and conversion metrics in a single, unified reporting experience. This will make it faster and easier to build dashboards and gain insights into your digital engagement performance.
| Customer Request | ✖ | UI Change | ✖ | Availability | GA On deploy |
A new audit trail feature for Configuration Manager will allow administrators and supervisors to track all user-initiated changes to configuration files. This update will provide full visibility into when configurations are created, modified, or assigned to teams, including detailed "before and after" values for changed parameters.
| Customer Request | ✖ | UI Change | ✖ | Availability | GA On deploy |
Administrators will soon be able to configure terminal emulator processes for data collection directly within the Desktop Discovery Configuration Manager. This new section will allow for the management of multiple terminal definitions, including process names, HLLAPI DLL paths, and screen title capture settings.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
Desktop Discovery will soon include the ability to detect synthetic input generated by idle-prevention tools, such as mouse jigglers or software-based simulators. This enhancement will provide more accurate visibility into genuine agent activity by distinguishing between human interactions and automated movements.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
To ensure the highest level of data security, Desktop Discovery will soon include a checksum verification process for message files stored on disk. This feature will automatically detect and prevent the transmission of any files that have been manually altered or tampered with, ensuring only authentic data reaches the server. The tampered files will be stored in a dedicated folder for further review.
| Customer Request | ✖ | UI Change | ✖ | Availability | GA On deploy |
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
Draft Message History Retrieval API will soon include date and time stamps for every approval or rejection action. This enhancement will allow you to maintain a complete audit trail for compliance and regulatory requirements by tracking exactly when a supervisor or administrator took action on a message draft.
For drafts approved or rejected before this update, the timestamp value will be null.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
Currently, when an agent is handling manual outbound interactions, such as an email message, their state does not change to Working in the agent application or in Supervisor. This only applies if the agent isn't handling any other digital interactions. If the agent has other active digital interactions, their state correctly shows that they are working.
In this release, the agent state will accurately reflect that the agent is working on an interaction. This will allow supervisors to accurately assess the state of each of their agents.
This feature is currently part of a Controlled Release and requires a feature toggle to be enabled.
| Customer Request | ✓ | UI Change | ✖ | Availability | GA On deploy |
Administrators will soon be able to assign customer contact forms directly to specific skills rather than being limited to channel-level assignments. This update will ensure that agents automatically see the most relevant custom fields and data entry options based on their specific line of business or expertise, even when interactions are transferred across different teams.
This feature is currently part of a Controlled Release and requires a feature toggle to be enabled.
| Customer Request | ✓ | UI Change | ✖ | Availability | CR On toggle |
Users will soon be able to track configuration changes made to digital channel settings through a new Audit Trail capability. This feature will provide enhanced visibility and accountability by capturing detailed records of who made a change, when it occurred, and the specific before-and-after values for each update.
| Customer Request | ✓ | UI Change | ✖ | Availability | GA On deploy |
Agents using Agent Workspace will soon be required to complete all mandatory custom fields before resolving or closing a digital contact. This update ensures that required data is consistently captured across all agent interfaces, improving data accuracy and streamlining post-contact workflows.
| Customer Request | ✓ | UI Change | ✖ | Availability | GA On toggle |
Currently, when a contact's device does not support form messages, Apple Messages for Business sends an external form link. In this release, it will break the form into simple in‑chat messages. Contacts will answer one question at a time using quick replies, list pickers, or text replies, depending on each input type in the original form message. Apple Messages for Business will send answers back to agents as a form submission. This streamlines the form filling experience for contacts with non-compatible devices, keeping them in the chat window instead of asking them to switch to a browser. Form messages are supported in iOS 18.4 and later.
| Customer Request | ✖ | UI Change | ✖ | Availability | GA On toggle |
Responses submitted through secure forms will be automatically saved to the corresponding contact custom fields eliminating the need for manual data entry. Previously, agents had to manually copy secure form data into custom fields, introducing risk of errors or missed entries. This change will ensure form data is captured consistently and immediately upon submission, improving data accuracy and reducing agent effort.
| Customer Request | ✓ | UI Change | ✖ | Availability | GA On toggle |
A limit of 250 notes per customer card and 5,000 characters per note will be introduced.
Once enabled:
Action Required: Before this feature is enabled on your account, review customer cards with high note volumes. If historical notes are critical for compliance or business records, export or archive them in advance. Please contact your account team if you need assistance identifying affected records.
| Customer Request | ✓ | UI Change | ✖ | Availability | GA On toggle |
As a security measure, any attachment download request that uses a file:// URI (local file path) will be automatically blocked and flagged as a potential security threat. This will prevent malicious attempts to access internal server files through the attachment download mechanism.
Action Required: If any of your integrations, bots, or automation scripts use file:// URIs when referencing attachments, these requests will fail after this change is enabled. Review your integration configurations and ensure all attachment references use standard https:// URLs. Contact your account team if you need assistance.
| Customer Request | ✓ | UI Change | ✖ | Availability | GA On deploy |
Outbound attachment download requests that resolve to private or internal IP address ranges (e.g., 10.x.x.x, 172.16.x.x, 192.168.x.x) will be automatically rejected. This is a server-side request forgery (SSRF) protection measure that prevents the platform from being used to access internal infrastructure.
Action Required: If your environment routes attachment downloads through an internal proxy, on-premises gateway, or private network endpoint that falls within these IP ranges, those requests will fail. Please review your network configuration and ensure attachment endpoints are reachable via public IP addresses. Contact your account team if this impacts your current setup.
| Customer Request | ✓ | UI Change | ✖ | Availability | GA On deploy |
A new safety guard will be introduced to prevent a known misconfiguration in Workflow Automation (WFA) that causes an infinite processing loop. Specifically, a WFA rule that uses a BeforeCaseClosed trigger combined with a ChangeCaseStatus job targeting a closed status will now be silently blocked from executing when the feature is enabled.
Previously, this combination caused the rule to trigger itself repeatedly, resulting in system instability and potential performance impact. After this change, affected rules will stop executing without raising an error.
Action Required: If you have WFA rules configured with a BeforeCaseClosed trigger and a ChangeCaseStatus job set to a closed status, those rules will no longer run after this update. Review your WFA configurations and reconfigure any rules that were relying on this combination. If you are unsure whether your account is affected, contact your account team for assistance prior to the 26.3 release.
| Customer Request | ✓ | UI Change | ✖ | Availability | GA On toggle |
You will be able to manage data policies for Digital Experience (DX) data directly within Interactions Hub. This will allow you to apply policies like Time to Live (TTL) and archiving in a single location, helping you maintain compliance with security and data retention standards such as GDPR, CPRA, and PCI.
To set up data policies, you must have Cloud Storage Services and Integration Hub enabled in your Contact Center system.
| Customer Request | ✖ | UI Change | ✖ | Availability | GA On toggle |
DX Email will be simplifying the setup of Microsoft Graph for outbound email by adding support for client certificate authentication and the Client Credentials grant type. These enhancements reduce administrative overhead by minimizing manual consent steps and eliminating the need for periodic client secret renewals. This provides a more secure and streamlined authentication experience for Microsoft Graph integrations.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
DX Email will now support enhanced email routing and address handling for scenarios where the sender ("From") and reply ("Reply-To") addresses differ. These improvements will help ensure replies are routed more accurately, improve email address validation, and provide more consistent experience for agents managing customer conversations.
This optional feature can be enabled for your business unit to provide more accurate customer identification and a streamlined communication experience for your agents.
| Customer Request | ✖✓ | UI Change | ✖✓ | Availability | GA On toggle |
Outbound email replies sent through DX Email will now include RFC 5322-compliant email headers, including In-Reply-To and References. This enhancement helps external email clients such as Microsoft Outlook and Gmail correctly group related messages into a single conversation thread, improving email continuity for recipients.
No additional configuration is required. This enhancement will be automatically enabled upon deployment.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
You will be able to create digital SMS channels that use the following SMS providers: Textel, Sinch, and Vonage. The channels will be able to handle inbound and outbound interactions.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
On Apple Messages for Business channels, forms are sent as a single message that contains all of the form fields. The contact completes the form and the system returns the form response as a single message.
On devices that don't support Apple Messages for Business form messages, the form will be sent as a series of separate messages. Each field or question on the form will be sent separately. The next field or question will not be sent until the contact answers the preceding field or question.
The contact will be notified as part of the chat that a form message is starting and given instructions. The agent will also be notified in the agent application that the contact is on a non-compatible device and given instructions about what will happen. Agents should not send other messages to the contact until the form completes.
| Customer Request | ✖ | UI Change | ✖ | Availability | GA On deploy |
Currently, the contact only sees typing indicators when the agent is actively typing. If the agent is selecting a quick response or doing another action that doesn't involve typing, the agent's message appears in the chat application without a typing indicator. In this release, typing indicators will be displayed for all messages on channels that support typing indicators, even if the agent doesn't type anything before sending the message. Typical indicators help make conversations with virtual agents feel more natural. This change only affects interactions between contacts and human agents using Agent Workspace (Agent).
| Customer Request | ✖ | UI Change | ✖ | Availability | GA On deploy |
Currently, public comments and replies on your organization's posts on LinkedIn refresh in Contact Center once a day. In this release, they will sync in near-real time. Agents will be able to see and respond to LinkedIn activity more quickly, improving the efficiency of managing interactions on this channel.
| Customer Request | ✓ | UI Change | ✖ | Availability | GA On deploy |
You will be able to add the ability to delete messages from your BYOC channel. To do this, you will need to update your channel to support delete by changing the hasAbilityToDelete parameter of the POST /channels endpoint to True. Next, you will need to update your middleware to accept and process the delete request from the Digital Experience (DX) APIs, similar to other calls Contact Center makes to your middleware. The platform will send the request as follows:
DELETE /1.0/channel/:channelId/messages/:messageIdOnExternalPlatform
{
"brand": {brandView},
"thread": {threadView}
}
| Customer Request | ✓ | UI Change | ✖ | Availability | GA On deploy |
In this release, the Meta Business Scope User ID (BSUID) will be used as the backend identifier that Digital Experience (DX) uses for WhatsApp contacts. This change prepares Contact Center for future support of WhatsApp user names, which Meta will enable for their users in the near future. With the introduction of user names, contacts who prefer not to use their phone numbers to interact with your organization will be able to use their user name instead. Users will be able to change their WhatsApp user names, but their BSUID will not be able to be changed to allow for continuity of threads with unique contacts even if their user names change.
| Customer Request | ✖ | UI Change | ✖ | Availability | GA On deploy |
Several UI enhancements will be introduced to DX Chat, including clearer queue counters, a new notification sound for incoming messages, unified menu navigation, updated avatar behavior, and smooth animations. These updates also include enhanced image viewing capabilities to provide a more intuitive and professional interaction for your patrons.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
To support compliance with the EU AI Act, both DX Chat and the Mobile SDK will soon include a visual indicator to notify patrons when they are interacting with an AI-powered bot. This feature will provide clear transparency during automated conversations and will automatically update if the chat is handed over to a human agent.
This feature will automatically be enabled for customers in the EU. For customers outside the EU, it is optional and can be enabled in Chat Settings.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
New privacy settings will be introduced for the Mobile SDK that will allow organizations to hide sensitive agent information, such as names and avatars, during active chat sessions. These controls will help protect agent identity by replacing real-time data with generic placeholders.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
All ESP customers will be migrated from the WCX cloud (North America) to the CXone cloud (North America).
| Customer Request | ✖ | UI Change | ✖ | Availability | GA On deploy |
The pages in the Feedback Management application will include significant accessibility improvements designed to offer a smoother, more inclusive experience for users across a wide range of visual, motor, and cognitive needs.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
A new set of APIs will be added to the Developer Portal to help build and maintain integrations with Feedback Management. Users will be able to programmatically retrieve invitation and response data in bulk, as well as access survey metadata, reducing manual work and keeping reporting pipelines up to date automatically.
| Customer Request | ✓ | UI Change | ✖ | Availability | GA On deploy |
Users in a regulated or sovereign environment will be able to capture verbatim feedback from IVR surveys using a Speech-to-Text engine that processes entirely in-region. The Post Call ASR for Transcription engine keeps all transcription under strict data residency controls, so your verbatim data never has to leave your regulated environment to be processed. This feature will be available in multiple languages.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On toggle |
From this release, the native Feedback Text Analytics engine will be generally available providing in-platform topic classification and sentiment analysis of survey comments. Organizations in Sovereign Cloud or FedRAMP environments will be able to use Feedback Text Analytics without any customer comment data leaving the regulated environment.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On toggle |
Users of the legacy Hierarchical Data Access configuration will be able to manage hierarchy during the transition to Advanced Data Access. The new Hierarchy Import means you will not need to freeze your hierarchy while you migrate, you can continue updating it via import file until you are ready to complete the move.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
In this release, the legacy Hierarchical Data Access configuration will be deprecated. Customers are advised to migrate to Advanced Data Access before the end of 2026. The new Hierarchy Import will allow you to keep your hierarchy up to date during the transition.
| Customer Request | ✖ | UI Change | ✖ | Availability | GA On toggle |
As part of a platform maintenance update, all charts are migrating to a new platform. The underlying data, calculations, and all functionality are unchanged. You may notice minor visual refinements in some charts.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
In this release, you will be able to use AI Assist in GenAI Prompts. AI Assist, implemented with AI Agents (Cognigy) will help you write and refine prompts directly within the application. As you create prompts, it will provide relevant suggestions and guidance. It will use existing product resources, such as online help, training materials, and prompt writing best practices, to suggest improvements and answer your questions in plain language.
In this release for Quality Management AutoScore only, you will be able to leverage transcript timestamps included in the data passed to the LLM, enabling prompts to assess time-sensitive behaviors—such as whether an agent completed a required action within a specified time frame during the interaction. For example, you can create prompts that assess questions such as:
The inclusion of transcript timestamps expands the ability of Quality Management AutoScore to support evaluations that depend on time-bound criteria.
In this release, timestamp support is available at the back-end level and is included in the context provided to the LLM. Visual timestamp representation within the GenAI Prompts interface will be introduced in a future release.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
Currently, when a language model is deprecated, customers receive no proactive warning within the product. There is no mechanism to alert users when a model they are actively using is approaching end of life, and no guided path for migrating prompt templates to a replacement model.
In this release, you will be able to see proactive deprecation indicators directly within the AI Studio interface. Warning messages will appear when you are using a model that is scheduled for or has already reached deprecation. Deprecated models will also be identified by a dedicated icon in the LLM list, making it easy to scan for models that require attention.
A migration path will also be provided to help you move existing prompt template versions to a supported replacement model, reducing the risk of service disruption when a model reaches end of life.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
In this release, GenAI Prompts will support multiple user interface languages, enabling users to interact with the GenAI Prompts in their preferred language. You will be able to:
This enhancement makes GenAI Prompts more accessible for multilingual teams and helps users work more efficiently in their preferred language.
| Customer Request | ✖ | UI Change | ✖ | Availability | GA On deploy |
Currently, GenAI Prompts profiles are tied to a fixed set of platform LLMs with no visibility or control over which models are available, their status, or their cost tier. Organizations with proprietary models, vendor contracts, or compliance requirements cannot use their own models within the GenAI Prompts.
In this release, you will be able to view the language models available in your GenAI Prompts profiles from a new LLM Manager. The LLM Manager is accessible through the Settings icon in the GenAI Prompts header. It gives you a central place to see all available models and understand their status. You will be able to:
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
Currently, rule evaluation in Guide uses the tenant-level time zone for all conditions. For organizations operating across multiple regions, this creates significant configuration overhead. A rule intended for a call center in Dubai, for example, must be duplicated and rewritten in terms of the tenant's time zone often requiring two or three rule variations to represent what should be a single, straightforward schedule.
In this release, you will be able to assign a dedicated time zone to each rule directly from the Rules Configuration page. When you set a time zone on a rule, all time-based conditions within that rule including shifts, dates, holidays, and day-of-week checks are evaluated using that rule's time zone rather than the tenant default. You will be able to:
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
Currently, the ability to check whether a specific element on a web page contains a particular string is available only in the legacy version of Guide. Customers who have migrated to the current Guide version do not have access to this condition type, limiting their ability to target visitors based on the text content of page elements.
In this release, you will be able to create rule conditions that check whether a specific element on a web page contains a particular string. This will allow you to target visitors based on what they see and interact with on your site, for example, showing a proactive offer, applying a tag, or triggering any other rule-based action relevant to that group. As with other page-content conditions, you must map the relevant elements using the Web Assistant Plugin.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
Currently, page view events and visitor location data including country, general location, and IP address are not sent to the data lake. This data was removed in the previous release due to storage concerns
In this release, all page view events will be restored to the data lake streams. Visitor location data, including IP address, location, and country, will also be restored. Specific data field definitions will be finalized as part of this release.
| Customer Request | ✖ | UI Change | ✖ | Availability | GA On deploy |
In this release, you will be able to define more precise schedules for your rules by including or excluding specific recurring dates and date ranges. This enhancement will help you automate rule behavior for holidays, seasonal events, and other recurring annual occurrences without having to manually enable or disable rules each year.
With the new Recurring Date & Time condition, you will be able to create recurring annual schedule exceptions and restrictions, such as the following:
In this release, the following scenarios will not be supported:
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
The Analyzed Interaction Segments API will soon support filtering by Skill ID in addition to the existing date filter. This enhancement will allow users to retrieve only those interaction segments that match both the specified Skill ID and date range, providing more precise and relevant results.
For more details, select the API filter on the top right.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On toggle |
Interaction Analytics (CXone) will soon support Contact End Reasons more reliably, even when they're set during after-call work (ACW). This means your interaction reports will be more complete and accurate.
| Customer Request | ✖ | UI Change | ✖ | Availability | GA On toggle |
IA will soon move language settings from the Analytics Backoffice to the Analytics Policies page for a more unified configuration experience. If your tenant has active policies, the Analytics Backoffice will display a message and a link to help you navigate to the new location for these configurations.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On toggle |
IA will introduce a smoother navigation experience that keeps your search filters active when you switch between views. Additionally, new Intent fields will be available to give you more detailed reporting. We are also updating the interface with better filter layouts, easier-to-read transcripts, and a faster Category Editor that automatically focuses on your newest entries.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
IA will soon integrate Interaction Analytics (CXone) and Quality Management (CXone) category data into the CXone Data Lake using standardized formats. This update will allow you to leverage your custom category insights across other CXone applications, providing a more unified view of your data and deeper cross-platform analysis.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
Users will be able to perform more flexible and precise historical searches for ANI and DNIS fields using substring operators. New operator selection and visibility in the policy panel will make it easier to define, review, and understand applied criteria.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On toggle |
Compliance managers will be able to define risk detection widgets using multiple criteria to identify potential violations with greater precision. Enhanced filtering will make it easier to tailor risk detection to specific business needs and focus on interactions that may require review.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On toggle |
Compliance Admins will be able to set a Line in the Sand date to prevent interaction deletions during legal events and help ensure required media is preserved. New configuration options and notifications will support clearer compliance management while safeguarding interactions that must remain intact.
| Customer Request | ✓ | UI Change | ✓ | Availability | CR On toggle |
Users will be able to view policy details and take key policy actions directly from a new right-side panel in the Policies tab. The panel will reduce navigation between pages and make policy review, evidence report downloads, recurrence management, and release actions more efficient.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On toggle |
Users will be able to support GDPR data erasure workflows across additional participating services through end-to-end integration with CSA Orchestration and Interaction Analytics. This will help ensure sensitive interaction data is properly deleted, strengthening data governance and regulatory compliance.
| Customer Request | ✖ | UI Change | ✖ | Availability | GA On toggle |
Users will be able to create more precise policy criteria using advanced comparison operators for Business Data fields. Expanded filtering options will make it easier to align policies with external data sources, handle incomplete or missing data, and define criteria that better reflect business needs.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On toggle |
Supervisors, evaluators, and managers will be able to instantly identify and manage locked recordings in iHub, reducing compliance risk and confusion. New UI with lock indicators and new search filtering will make it easy to find secured interactions.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On toggle |
Users will experience a cleaner and more organized dashboard layout with widgets that better adapt to high-resolution screens. Improved responsiveness will help maximize screen space, enhance data visibility, and provide a more consistent interface across supported displays.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
In this release, you will be able to connect Knowledge Hub to the Engageware Knowledge Management System as a knowledge source. You will be able to:
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
Currently, setting up a Knowledge Hub connector requires customers to manually enter multiple credentials, including a Client ID, Client Secret, Access Token, and Authorization Code.
In this release, you will be able to connect ServiceNow to Knowledge Hub using a simplified OAuth authentication flow. Instead of entering credentials manually, you will be redirected to your ServiceNow platform to authenticate with your existing username and password. Token generation and refresh are handled in the background, so you will not need to manage them yourself. You will be able to:
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
In this release, Knowledge Hub will be available in the Japan region.
| Customer Request | ✖ | UI Change | ✖ | Availability | GA On deploy |
Knowledge Hub documentation has been moved from the Contact Center Help Center to the Expert Help Center. Use the Expert Help Center to access the latest Knowledge Hub documentation.
| Customer Request | ✖ | UI Change | ✖ | Availability | GA On deploy |
Several enhancements, including new search filters for External Segment IDs and External Contact IDs, the ability to share segments with multiple users, and a new deletion flow for contacts aligning to CXone's data management best practices will all be introduced in this upcoming release.
| Customer Request | ✓ | UI Change | ✓ |
Availability | GA On deploy |
As part of the unification of Contact Center and Outbound Engagement (SmartReach), Outbound Engagement (SmartReach) will be updated with the new NiCE CXone logo. The name of the application will be changed from SmartReach to Outbound Engagement.
Additionally, in this release, the Services Editor user interface will be updated to be consistent with Contact Center.
| Customer Request | ✓ | UI Change | ✓ |
Availability | GA On deploy |
To support larger scale deployments and growing customer data needs, Customer (Contact) Manager will support contact lists that can be configured for up to 40 million records.
| Customer Request | ✓ | UI Change | ✓ |
Availability | GA On deploy |
You will be able to use Contact Center digital SMS channels that use Textel as a messaging provider with Outbound Engagement (SmartReach) for outbound SMS campaigns. You will be able to run campaigns through Textel channels, automate compliance keyword responses, and manage two-way agent conversations.
For more details about SMS channels with Textel, select the Digital filter on the top right.
| Customer Request | ✓ | UI Change | ✖ | Availability | GA On deploy |
To streamline the integration with Contact Center, Outbound Engagement (SmartReach) will introduce specific configuration restrictions within its Configuration Manager. These updates ensure a more cohesive experience by automatically disabling or hiding certain settings, such as specific ACD modes and service types that are managed directly through Contact Center.
| Customer Request | ✖ | UI Change | ✓ |
Availability | GA On deploy |
In this release, you will be able to use Outbound Engagement (SmartReach) for manual outbound calls placed using a Contact Center agent application. Outbound Engagement (SmartReach) will perform compliance checks on the call, and if the call violates a compliance check, the system will not place the call.
This option requires Contact Center agent applications and Outbound Engagement (SmartReach). You will need to configure the compliance rules in the Outbound Engagement (SmartReach) application.
| Customer Request | ✖ | UI Change | ✖ | Availability | GA On toggle |
To ensure a seamless monitoring experience on the unified platform, Outbound Engagement (SmartReach) dashboards will be optimized to display only relevant campaign management data. This update will automatically hide inactive ACD, agent, and inbound data fields, and will provide a cleaner and more focused interface for real-time outbound performance tracking.
| Customer Request | ✖ | UI Change | ✓ |
Availability | GA On deploy |
The Outbound Engagement (SmartReach) application will include significant accessibility improvements designed to offer a smoother, more inclusive experience for users across a wide range of visual, motor, and cognitive needs.
| Customer Request | ✓ | UI Change | ✖ | Availability | GA On deploy |
Comprehensive support will be added for Australian geographic identifiers within Dialing Profiles. This enhancement will use state, territory, and postcode mapping to ensure outbound campaigns maintain strict compliance with regional time zone regulations and dialing windows.
| Customer Request | ✖ | UI Change | ✖ | Availability | GA On deploy |
Outbound Engagement (SmartReach) will support skill prioritization that aligns with the existing Contact Center ACD routing model. The Outbound Engagement skill type in Contact Center ACD will be updated so you can assign skills numeric priorities. This will ensure that agents automatically receive the most important interactions first, whether they are inbound, manual outbound, or predictive outbound. By unifying prioritization across all channels, you will be able to prevent outbound tasks from overshadowing high-priority inbound queues and maintain consistent service levels across your blended agent workforce.
| Customer Request | ✖ | UI Change | ✓ |
Availability | GA CR On deploy On toggle |
Users will be able to evaluate Monitoring Gateway Subscriptions in a structured demo environment available in the USA only. Simulated event generation, real-time log visualization, and a hosted dashboard will help demonstrate how subscription data can support monitoring and observability workflows without accessing production systems.
| Customer Request | ✖ | UI Change | ✓ |
Availability | GA On toggle |
The Personal Connection application will include significant accessibility improvements designed to offer a smoother, more inclusive experience for users across a wide range of visual, motor, and cognitive needs.
| Customer Request | ✓ | UI Change | ✖ | Availability | GA On deploy |
You will be able to configure agentless outbound Personal Connection skills to be able to retry calls when they encounter carrier error (SIP 480 (Cause Code 16)) responses. This will give you more control over call handling.
A new outbound-specific disposition code will be available for this type of response. You will be able to apply this disposition through scripting, which will let you enable retry behaviors that you can configure to meet your specific business needs. To use this new disposition code, you'll need to update your customer scripts to include the SETDISPOSITION action with the new code. Otherwise, your existing outbound behavior will remain unchanged.
After enabling it in your scripts, you will be able to enable or disable this disposition on a per-skill basis. By enabling the new Treat Carrier Error as Temporarily Unavailable option for a skill, you will be able to choose the situations where you want the new disposition used.
| Customer Request | ✓ | UI Change | ✓ |
Availability | GA On deploy |
You will be able to preview wallboards in real time before publishing. Previews will show live, read-only data and follow the configured slide order, timing, and transitions. In addition, the Wallboards experience will be redesigned with a modern, consistent interface, including updated slides, a new management page, and improved workflows to make creating and editing wallboards more intuitive and efficient.
This feature requires a PM – Insights license to activate.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
New preset dashboard date range filters, such as Current Week and Current Month, will help you quickly view data without manually setting custom dates.
This feature requires a PM – Insights license to activate.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
Role-based dashboard sharing will be updated with a clean, modern UI. New dedicated columns for Roles and Permissions will make managing access more efficient and intuitive.
This feature requires a PM – Insights license to activate.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
You will be able to use the new Notepad widget to record action items, reminders, explanations, and other notes right next to your data, helping you capture context and make decisions faster.
This feature requires a PM – Insights license to activate.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On toggle |
Charts will receive minor UI improvements, with no changes to functionality.
| Customer Request | ✖ | UI Change | ✖ | Availability | GA On deploy |
CXone Performance Management (Native) will include significant accessibility improvements designed to offer a smoother, more inclusive experience for users across a wide range of visual, motor, and cognitive needs.
| Customer Request | ✓ | UI Change | ✖ | Availability | GA On deploy |
We will be introducing a maximum limit of 20 Auto Score profiles per scorecard to enhance system stability and ensure consistent scoring performance. When creating or editing a scorecard, the Add Profile action will be disabled once the cap is reached, along with a clear notification. You should plan your configurations within the 20-profile limit.
The Select Profile dropdown will disable further selections once 20 profiles are assigned. If you have active scorecards exceeding this limit, they will continue to function. However, you will not be able to add new profiles or duplicate these scorecards until the profile count is reduced to 20 or fewer.
This feature will be available for users with the Quality Management (CXone)Advanced and Gen AI licenses.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On toggle |
The upcoming Auto Score Ad Hoc Feedback feature will give supervisors and administrators a direct voice in the Auto Score process.
Users will be able to provide instant feedback on AI-generated scores directly within the My Zone Scorecard Dashboards. With simple thumbs up or thumbs down icons, users will validate accurate results or flag discrepancies. When a thumbs down is selected, the user will explain the lack of agreement in a text box that will route to administrators for feedback collection (up to 1K characters) and possible action to improve the Prompt. This human-in-the-loop approach will help ensure higher accuracy and greater transparency in quality programs. You will be able to seamlessly review Auto Score results to ensure alignment with organizational quality standards, building higher confidence in automated metrics.
This feature will be available for users with the Quality Management (CXone)Advanced and Gen AI licenses.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On toggle |
You will be able to export data directly from the following My Zone pages to Excel or CSV formats.
My Zone pages with Export:
When you click the Export button, you will be able to choose your preferred format to download the records currently visible in your grid.
This feature will be available for users with the Quality Management (CXone) license.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On toggle |
You will soon see a small but helpful change in My Zone. The Tasks tab will be renamed to Evaluation Tasks to make its purpose clearer and easier to understand. The page title and URL will also reflect this update. No widgets will be added or removed just a smoother experience when navigating to your evaluation tasks.
This feature will be available for users with the Quality Management (CXone) license.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On toggle |
With this update, Quality Management (CXone) will only distribute interactions if the leading agent is part of a team in the Quality Plan. Going forward, an interaction will only be distributed for evaluation if the leading agent is explicitly part of a team associated with the Quality Plan. Previously, distribution could occur if any participant matched the plan.
This change will ensure that both the interaction eligibility and the leading agent’s team membership align with the Quality Plan requirements. As a result, agents will only be evaluated under plans they belong to, improving reporting accuracy and ensuring evaluations are routed to the appropriate supervisors.
This feature will be available for users with the Quality Management (CXone) license.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On toggle |
Quality Management (CXone) will include significant accessibility improvements designed to offer a smoother, more inclusive experience for users across a wide range of visual, motor, and cognitive needs.
| Customer Request | ✓ | UI Change | ✖ | Availability | GA On deploy |
Quality Management (CXone) will support Tenant Segmentation, enabling strict data segregation across organizational divisions. Users and admins will only be able to access forms, quality plans, evaluations, and calibrations specific to their assigned division, ensuring more relevant and secure data visibility. Division level segmentation will streamline workflows by reducing clutter and aligning processes with organizational structures.
The update will include new scripts for data creation, form creation, and Quality Plan setup, requiring proper division metadata (L0, L1, L2) to ensure accurate segmentation. The system will also depend on the Division license being enabled for performance tenants. To avoid disruptions, new tenant setups will be recommended, and teams will need to review configurations and workflows to align with the updated segmentation model.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On toggle |
Currently, custom headers used during evaluations are not available in external API data tables, limiting your ability to perform deep-dive analysis.
In this release, the Data Extract API will be updated to include custom headers from evaluations. This change will allow your Reports Analysts to pull this data directly from the Data Lake into your API tables, making it easier to use these headers as filters for external analysis. You will be able to more effectively track and organize your evaluation data in third-party reporting tools, bridging the gap between data collection and deep-dive reporting.
This feature will be available for users with the Quality Management (CXone)Advanced license.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On toggle |
Managing large numbers of teams will become more efficient with a new dynamic search in the Evaluation view. The dropdown will use an API-driven search to help you find any team instantly by name. The system will load results in smooth batches of 250 to prevent browser lag, and a new footer notification will let you know if you need to refine your search. You will also see a clear count of your selected teams, ensuring you can always find and track the exact groups you need for evaluations.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On toggle |
You will soon be able to organize evaluation forms much faster using a new Elements tree panel. This tool will provide a clear tree view of your entire form, allowing you to move questions instantly across different sections and add new ones exactly where you need them. It will replace the old drag-and-drop method with a more reliable, scrollable map that makes managing long forms simple. Additionally, built-in warnings will protect your form logic by alerting you if you try to move a question linked to a rule, ensuring your design remains accurate and error-free.
This feature will be available for users with the Quality Management (CXone) license.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On toggle |
This upcoming release will deliver CRM Ticketing Enhancements to improve evaluation workflows, flexibility, and reporting accuracy. Key updates will include the ability to play back audio directly from Salesforce CRM ticket when the Salesforce is integrated with Amazon Connect, making ticket reviews more efficient. The system will also better handle tickets with missing or unknown agent information, ensuring they are still assigned for evaluation via the Quality Plan reducing gaps in quality monitoring. Validation rules will be relaxed to support edge cases, allowing smoother assigning of tickets to evaluate even when agent metadata is missing.
Additionally, enhanced agent discovery will support first-reply, first-resolved, and assigned agents, which may impact reporting and analysis. These changes will improve flexibility and coverage, though teams may need to review workflows for tickets with incomplete agent data.
This feature will be available for users with the Quality Management (CXone) license.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On toggle |
You will soon be able to bring external voice, screen, and digital interactions into Contact Center using the new Generic Injection API. This feature will allow you to seamlessly import transcripts and attachments from outside sources, making them immediately available for Search and Playback. Once injected, these interactions will be treated just like native data, enabling you to perform Quality Management (CXone) evaluations and run Interaction Analytics (CXone) (IA) for a complete, unified view of your customer experience across all channels.
This feature will be available for users with the Quality Management (CXone) license.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On toggle |
The new Store & Forward (S&F) Generic Ingestion API will provide a standardized way for external recording and digital systems to bulk‑import closed interactions into Contact Center. This feature will require a Recording Advanced Store & Forward license with the Voice/Digital API option selected.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
Engagement Hub (Multi-ACD/Open) will support AWS Direct Connect, enabling private, secure connectivity for CTI and media traffic.
| Customer Request | ✓ | UI Change | ✖ | Availability | GA On deploy |
Administrators will be able to enable or disable telephony systems directly in Contact Center with new systems created in a disabled state by default. This provides greater control during setup and supports smoother configuration, maintenance, and business continuity.
| Customer Request | ✖✓ | UI Change | ✓ | Availability | GA On deploy |
The CSV file generated by the Data Extract API will include the telephony system name (such as Cisco, Avaya, or Genesys) for each interaction. This will help customers in Engagement Hub (Multi-ACD/Open) environments to easily identify, analyze, and troubleshoot interactions.
| Customer Request | ✖✓ | UI Change | ✓ | Availability | GA On deploy |
Users will be able to easily retrieve and playback media files for interactions stored in long-term storage directly from the Interactions Search grid. This new flow will use the existing Cloud Storage>Long-term File Retrieval>Create permission.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On toggle |
The transcript in the Player was enhanced to display Multi-Party transcription for up to five participants.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
Indication for Leading Agent, adding a columns and filters for Transcript Language and Playback Lock, will be added to the Interaction Search.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On toggle |
Users will be able to view all skills associated with an interaction, including secondary skills, directly in the search results table. The Skills column and filter will be renamed to Primary Skill and a new column and filter called Additional Skills will be added.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On toggle |
Users will be able to export all interaction data to csv or excel, and not only the columns set to display, directly from Interactions Search with the new Export all fields export option.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On toggle |
Users will be able to filter interactions in the Interaction Hub by criteria (for example: Last 90 Days or Voice) to create Topic AI collections without needing an Interaction Analytics (IA) license. Will require a Topic AI license.
| Customer Request | ✖✓ | UI Change | ✖ | Availability | GA On toggle |
CXone Recording applications will support up to 100,000 named agents per tenant. This scalability improvement will enable large enterprises to maintain performance during peak demand and support growth without service disruption. Recording Policies introduce new usage limits for smooth functionality.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
Currently, the Connectivity Check Tool validates connectivity requirements for Screen Recording. In this release, the Connectivity Check Tool will also validate connectivity requirements for Real-Time Screen Monitoring (RTSM).
| Customer Request | ✖ | UI Change | ✖ | Availability | GA On deploy |
Currently, Contact Center Reporting supports SFTP as a file delivery option for Data Downloads and Custom Report scheduled outputs. In this release, to meet updated NiCE compliance and security requirements, SFTP will be deprecated via a feature toggle and replaced with the Secure Export Agent (SEA) Cloud Storage architecture.
When the system-level feature toggle is enabled:
Action Required:
No manual setup is required for the migration; however, administrators should review their report schedules after the update to confirm settings and familiarize themselves with the new SEA Cloud Storage workflow.
| Customer Request | ✖ | UI Change | ✓ | Availability | On toggle |
In this release, you will gain full visibility into Digital Experience (DX) contact lifecycles with our new activity tracking. Unlike previous versions that relied on the contact's original start date, this new API will allow you to retrieve all state changes (assignments, status shifts, and so on) that occur within any 7-day window. This ensures you capture critical intraday events for digital interactions, even if they began weeks ago.
For more details, select the API filter on the top right.
Action Required:
Prepare to update your Reporting workflows to leverage the new endpoints.
| Customer Request | ✓ | UI Change | ✖ | Availability | GA On deploy |
Currently, when an action property contains a large string, such as the Body property of the EMAIL action, you cannot see the entire value. The contents of the field are truncated in the Property panel view. In this release, you will be able to hover the cursor over the field to see a tooltip containing the entire property value. You will also be able to click an expand button that will open a text editing window, where you will be able to view or edit the property value.
| Web or Desktop Studio | Web only | Customer Request | ✓ | UI Change | ✓ | Availability | GA On toggle |
Currently, in the snippet debugger does not allow you to copy the value of variables. If the value is long, you cannot see the entire value. In this release, there will be an option to copy a variable's value to the clipboard. Also, you will be able to see the entire value. These changes will make it
| Web or Desktop Studio | Web only | Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
You will have more flexibility in how you organize your scripts within script development workflows. You will be able to choose whether to use branch subfolders, such as the "main" subfolder currently required for the development stage. This change will simplify the workflow for organizations that do not require Git-based branching strategies, while still supporting those who do. You will only be able to configure this option during the initial setup of a script development workflow organization.
| Web or Desktop Studio | Web only | Customer Request | ✖ | UI Change | ✓ | Availability | CR On toggle |
Currently, for drop-downs that allow you to select from a list of named objects, such as agents, Studio loads the entire list. These lists appear in Studio action properties. In this release, these lists will be paginated. This will ensure that when there are a large number of these objects, the lists load quickly and the script editing interface remains responsive.
Additionally, you will be able to search lists in action properties. This will allow you to easily locate specific objects in long lists.
| Web or Desktop Studio | Web only | Customer Request | ✓ | UI Change | ✓ | Availability | GA On toggle |
Currently, when you start multiple traces on the same script, they appear in a single window, but to detach the trace from contact or end the contact, you must open each script. In this release, the options will be available in the header of this window. This will allow you to take those actions on scripts listed in the window without having to open each script.
| Web or Desktop Studio | Web only | Customer Request | ✖ | UI Change | ✓ | Availability | GA On toggle |
Currently, you can resize the text field of the ANNOTATION action on the script canvas. In this release, this will be improved. The text field will have more obvious borders on the canvas and it will be more obvious that you're able to resize it.
| Web or Desktop Studio | Web only | Customer Request | ✓ | UI Change | ✓ | Availability | GA On toggle |
Currently, the API actions are listed in alphabetical order by name on the API Actions palette. In this release, the actions will be grouped into categories to match those on the NiCE CXone developer portal . Additionally, actions will be renamed to match the corresponding API on the developer portal. These changes will make it easier to find the corresponding API documentation.
| Web or Desktop Studio | Web only | Customer Request | ✓ | UI Change | ✓ | Availability | GA On toggle |
Currently, you can create a copy of a script using a menu option called Duplicate. In this release, option will be renamed to Save As. This will reduce confusion and align with the name of the same option in Desktop Studio. Additionally, the option will move to be near Save button.
| Web or Desktop Studio | Web only | Customer Request | ✖ | UI Change | ✓ | Availability | GA On toggle |
Currently, you can filter traces using the ANI and DNIS fields. This doesn't work for digital scripts, because digital interactions don't have this data, which are related to phone numbers. In this release, you will be able to filter trace requests for digital scripts using To and From fields. This will make it easier to isolate and analyze specific digital interactions.
This feature will be available later in the release cycle.
| Web or Desktop Studio | Web only | Customer Request | ✓ | UI Change | ✓ | Availability | GA On toggle |
The ADDCFR action will be removed from Desktop Studio. If you use this action in your scripts, you will need to update them. If this action is in your scripts an error will be logged when it runs, but the script will continue to execute.
| Web or Desktop Studio | Web only | Customer Request | ✖ | UI Change | ✖ | Availability | GA On deploy |
You will be able to change the state of multiple agents at once from the Focused View Agent tab - either to Available or any of your configured Unavailable codes.
This will help you quickly transition large groups of agents between states in a single action, ideal for emergencies.
This feature will require the Bulk Change Agent State permission and must be enabled in Global Settings under Bulk Operations.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
The Agent Schedule view in Supervisor will display the custom activity colors as configured in WFM.
If no custom colors are configured, the schedule will continue to show the default system colors.
This feature only applies to CXone WFM users.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
You will be able to assign and unassign skills to all agents within a team in a single action from the Focused View, Skill tab. When assigning a skill, you will be able to set a custom proficiency value (1 to 20) instead of the default value (3) to apply to all agents in the Team at once.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
Screen Assist, introduced in the previous release, enables you to place contextual coaching notes on an agent's screen during live screen monitoring sessions. The agent will see a blue dot where the comment has been placed.
Building on this, you will now be able to show or hide Screen Assist notes from the agent using a new Show/Hide menu on the supervisor toolbar. This will let you temporarily remove notes from the agent's view and restore them as needed to give you more control on your assist session, making the coaching process fully reversible.
All hidden and restored notes will still be captured in the session audit report.
To use Screen Assist, you must have Recording Management (CXone) Advanced license enabled for your tenant and the Screen Recording Advanced license.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |
You will be able to change the next state of agents who are currently handling contacts from both the Overall View and the Focused View. When you select a new state for a working agent, the system will set it as the agent's next state. The agent will automatically transition to the chosen state once they complete their current contact.
This feature will use the existing Change Agent State permission. No new permission is needed.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
In this release, the Test Suite will receive several usability and transparency enhancements designed to make testing workflows more efficient and easier to understand. You will be able to view additional metadata directly within the Test Suite, including the LLM profile and model used during analysis. This provides greater transparency into test execution and eliminates the need to navigate to multiple areas of the application to find key configuration details.
As part of this redesign, product documentation and screenshots will be updated to reflect the new user interface.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
In this release, the Test Suite will support multiple user interface languages, allowing users to perform testing and evaluation activities in their preferred language. You will be able to:
| Customer Request | ✖ | UI Change | ✖ | Availability | GA On deploy |
Contact Center Transcription will soon support 25 additional languages across all ASR modes, including low-latency, real-time, and post-call transcription. This update will allow users to select from an extended list of languages such as Mandarin, Cantonese, and Thai directly within existing workflows without requiring any new interface changes or manual enablement.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
Vocabulary configurations for Contact Center Transcription will soon move from the Interaction Analytics (CXone) application to a new location under the Admin menu. This change establishes Contact Center Transcription as a standalone service and places its settings alongside related features like Redaction Profiles and Analytics Policies for a more streamlined administrative experience.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On toggle |
The Contact CenterTranscription configuration will include significant accessibility improvements designed to offer a smoother, more inclusive experience for users across a wide range of visual, motor, and cognitive needs.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On toggle |
A new Real-Time Audio (RTA) connector will be introduced for the Voicebot Stream action, which will allow customers to select Azure Open AI GPT-4o as a provider. This enhancement will allow faster, more natural AI conversations and automated self-service within their IVR.
| Customer Request | ✖ | UI Change | ✓ | Availability | CR On toggle |
The unsupported SIP Integration option will be removed from the Custom Exchange Endpoints and Salesforce Einstein configurations in Virtual Agent Hub. This update will simplify the setup process by ensuring only supported integration options are visible to users.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
A None option will be added to the language selection dropdown for Google Dialogflow CX bots. This will allow the bot to automatically detect the customer's language during a conversation instead of requiring a pre-defined language code.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On deploy |
Agents using Virtual Desktop Infrastructure will experience improved audio quality and reduced latency with media routing that bypasses the VDI tier. A new browser extension will help simplify multimedia handling, reduce bandwidth usage, and provide a more accessible and responsive voice experience.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On toggle |
Voice Biometrics Hub will be available in the UK sovereign cloud configurations. This will expand the regions where you can implement voice biometric authentication using this hub application.
| Customer Request | ✖ | UI Change | ✖ | Availability | GA On deploy |
The option in Voice Biometrics Hub for selecting Voice Biometrics when adding a new voice biometric profile will be updated. The name listed on the button will change to NiCE CXone Voice Biometrics.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On toggle |
In version 26.3 and later, custom color codes that you assign to activity codes in Scheduling will be consistently displayed across additional areas of the product. You will be able to visually distinguish between multiple activity codes of the same type, such as Open, Busy, On Call, Out of Office, and Break, and identify them immediately without hovering over each activity.
Currently, custom colors assigned to activity codes are only supported in Scheduling. When you navigate to other pages such as My Zone, Time Off, or Admin, all activity codes of the same type appear in the same default color. To identify a specific activity, you must hover over it and read the name.
In this release, custom color code support will be extended to the following pages:
The updated colors will be reflected in page filters, activity code values in grids, and anywhere else activity codes are displayed.
This enhancement simplifies schedule management, reduces errors, and boosts efficiency for teams handling complex schedules across Agent, Time Off, Admin, and Mobile views.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On toggle |
The forecasting engine will support a new Whole Time Series forecasting method alongside the existing Day of Week method. Whole Time Series will use continuous time series data to generate forecasts, delivering more accurate predictions by preserving data continuity. It will use a single model per predicted skill, simplifying model management and troubleshooting.
Currently, the forecasting engine splits historical data by day of the week and builds separate models for each day. This disrupts data continuity and limits the ability to capture seasonal trends.
In this release, a new Whole Time Series forecasting option will be available alongside the existing Day of Week method. The engine will automatically evaluate all supported models and select the best one based on Mean Absolute Percentage Error (MAPE). You will also have the option to select a model manually. The supported models include:
All forecasting jobs, both new and existing, will default to Day of Week forecasting. To use Whole Time Series, select it as the forecasting method when creating the job. You can switch between the two methods until a forecast becomes active. Once a forecast is active, the forecasting method cannot be changed.
This enhancement improves forecast accuracy, simplifies model management, and supports additional models and forecasting methods in the future.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On toggle |
In Step 5 (Post-staffing), Intraday Manager, and Schedule Manager, you will see staffing results that stay aligned with your original forecasted Volume and AHT. This will help you trust what you see in post-staffing and intraday views and make planning decisions with a single, consistent set of numbers.
Currently, Step 5 shows Volume and AHT based on simulated values instead of the forecast from Step 3. Due to spillover, where calls cross into the next interval, the simulated totals deviate from the forecast, causing mismatched numbers across steps and downstream views.
In this release, two new data fields will be available in Step 5 of the forecast job, fixing an issue where Volume and AHT previously reflected staffing solution values rather than the original forecast:
Forecast Volume and AHT will now flow to downstream reports, including Intraday Manager and Schedule Manager, giving you accurate, traceable forecast data that simplifies reconciliation and improves confidence in staffing outputs.
The staffing calculator itself remains unchanged.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On toggle |
The WFM Copilot panel in Intraday Manager will now support a curated set of 13 validated questions, enabling you to analyze post-shift adherence and skill performance directly from a conversational interface, without switching between reports, exports, or spreadsheets.
In this release, the Copilot panel will support 13 production-ready questions covering the most common post-shift analysis topics. You can ask questions such as:
Responses are generated from historical data and rendered as text, lists, or grids within the panel. All responses respect your organizational unit, team, and agent-group permissions.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On toggle |
Starting with the 26.3 release, your time-off balance will be deducted based on the actual duration of the time-off activity on your published schedule. This change will help ensure that your balance accurately reflects the time you take off, especially if you work extended or non-standard shifts.
Currently, time-off deductions are capped by the FTE value defined in the Time Off Rule. For example, if an agent has a 10-hour shift but the FTE value is set to 8 hours, only 8 hours are deducted from the balance. This discrepancy allows agents to exceed their earned time-off hours without it being reflected in the balance.
In this release, the following changes will apply:
This enhancement helps ensure that your time-off balance accurately reflects the actual time off you take.
| Customer Request | ✖ | UI Change | ✓ | Availability | GA On toggle |
Adjusted forecast data from Step 3 and Step 4 will now automatically reflect in the Intraday Report without requiring schedule regeneration.
Currently, forecast adjustments made in Steps 3 and 4 could be propagated to Schedule Manager and Intraday Manager without regenerating schedules, but the Intraday Report continued to display the original forecast data until schedules were regenerated.
In this release, any adjustments made in Step 3 or Step 4 of the Forecast workflow will automatically propagate to the Intraday Report once saved in Step 5. The supported adjustments include:
Step 3:
Step 4:
These adjustments will update the staffing requirements, forecast volume, and forecast AHT displayed in the Intraday Report.
Only future intervals from the time of the forecast update will be refreshed. Historical interval data will remain unchanged.
| Customer Request | ✖ | UI Change | ✖ | Availability | GA On deploy |
Skill levels are a core tool for WFM managers and supervisors to manage skill groups and work volume distribution. By assigning proficiency scores to agents across WEM skills, teams can prioritize or reserve agent capacity for specific queues, ensuring the right agents are scheduled for the right work at the right time.
Currently, proficiency scores can be assigned to an employee's WEM skills within the platform, ensuring alignment between the WFM system and the ACD platform. The ACD relies on these proficiency scores for contact distribution during simulation, but they do not influence how schedules are generated. Agents with higher proficiency scores are not preferentially scheduled over lower-scoring peers.
In this release, agent proficiency scores will drive schedule generation. When agent proficiencies are enabled for WEM skills and configured under Employee Management, those scores will be factored directly into schedule generation, not just simulation.
Agents with higher proficiency scores will be prioritized for scheduling coverage on the corresponding skill, ensuring your highest-scoring agents are allocated first.
This enhancement improves skill-based scheduling coverage by aligning schedule outputs with the priority tiers your team has already defined, reducing manual override work.
| Customer Request | ✖ | UI Change | ✖ | Availability | GA On toggle |
CXone WFM will include significant accessibility improvements designed to offer a smoother, more inclusive experience for users across a wide range of visual, motor, and cognitive needs.
These improvements include updates across multiple areas of the application. For example, the Forecasting wizard will feature refreshed icons, patterns, and layout to enhance clarity. These are appearance changes only—all existing functionalities will remain unchanged.
| Customer Request | ✓ | UI Change | ✓ | Availability | GA On deploy |