Genesys Cloud FedRAMP Region – November 9, 2026
Feature availability may vary and is based on factors such as, but not limited to, region readiness, product licensing, and the Genesys release schedule. For more information, see the Genesys Cloud release schedule.
Genesys Cloud Experience Units terminology
Genesys Cloud renamed Genesys Cloud AI Experience Tokens to Genesys Cloud Experience Units. This terminology change appears across Genesys Cloud, including billing and usage views, reports, meter descriptions, and AppFoundry pricing. This is a name change only and does not affect the value of the units, pricing, existing contracts, usage, balances, entitlements, or how customers consume Genesys Cloud capabilities. No customer action is required.
Web Directory updated to use PKCE for improved security
Web Directory now uses Proof Key for Code Exchange (PKCE) for authentication. This update prevents access tokens from appearing in browser URLs, improving security and helping organizations address authentication vulnerabilities identified during security assessments.
Assign divisions to roles for authorized organizations users and groups
Administrators can now scope individual roles for users and groups in authorized organizations to one or more divisions. Previously, these roles could only be scoped to All Divisions. Administrators can view the roles assigned to an authorized user or group and select the divisions that apply to each role. This capability limits access to the resources required for the user's or group's responsibilities and provides the same division-based role scoping available for other Genesys Cloud users and groups.
Configurable auth token storage
Administrators can now choose whether to store authentication tokens in persistent storage or session storage. Persistent storage can reduce the number of times users are required to log in, such as after a browser refresh, while Session storage can potentially reduce the risk of unauthorized access to authentication tokens. This option allows organizations to choose the storage method that best meets their security and user experience requirements.
Instagram engagement metrics in social listening
Administrators and supervisors can now view and track engagement metrics for Instagram owned-page content in social listening. Previously, engagement information was available for X and Facebook. Users can view, filter, and sort Instagram posts and reels by likes, shares, comments, views, reposts, and saves as engagement information updates. Administrators can also use supported engagement metrics as criteria in social escalation rules to help prioritize content based on engagement levels.
Callback Copilot available to create and modify scheduled callbacks
Supervisors can now use Genesys Cloud Copilot to create, modify, and cancel scheduled callbacks by using natural language. Copilot reduces operational complexity by minimizing UI navigation and enables supervisors to respond more quickly to operational changes. Callback actions require user confirmation before they are completed.
Secure replies and new outbound emails to addresses outside the Domain Allow List
Administrators can now configure Domain Allow Lists to allow agents to reply to or forward emails to recipients outside the allow list when those recipients appeared in the most recent email in the conversation. Administrators can also allow agents to initiate new outbound emails from ACD queues to addresses outside the allow list. Both options are configured per Domain Allow List and are disabled by default. Domain Allow Lists also support wildcard domains in the *.example.com format, which includes subdomains but not the root domain unless it is added separately. These options reduce the need to continually add individual customer and third-party domains while allowing administrators to retain control over where agents can send emails.
Administrators can now bring their own SMS SMPP provider
Administrators can now use the Bring Your Own (BYO) SMS feature to integrate existing SMPP accounts and SMS numbers in Genesys Cloud. This feature allows organizations to use their preferred SMS carrier, broker, or aggregator while continuing to manage SMS interactions within Genesys Cloud. With this update, administrators can configure external SMS providers, validate SMS-enabled numbers, and assign them for outbound queues, inbound flows, or agentless notifications. This feature provides greater flexibility for organizations that want to use existing vendor relationships, consolidate messaging partners, or reach markets not directly supported by Genesys Cloud.
Expanded WebHID integration for call control via headsets
Feature postponed: November 20, 2026
Genesys Cloud users can now control calls on their WebRTC softphone using physical buttons on supported Poly and Jabra headsets through WebHID integration. This enhancement eliminates the need for proprietary desktop applications, enabling features such as answer, end, mute, and manage calls directly from the headset in Chromium-based browsers. The update helps improve agent productivity and streamlines headset integration with Genesys Cloud.
Canadian French user interface language support
Genesys Cloud now supports Canadian French (fr-CA) for the Agent, Supervisor, Admin, Performance/Analytics, Embeddable Framework, Mobile, and Desktop user interfaces, enabling organizations to provide a more localized user experience.
Zendesk data actions OAuth client credentials grant support
Administrators can now use the OAuth client credentials grant to authenticate Zendesk data actions. Previously, Zendesk data actions used API tokens for authentication. This update provides an authentication option for new Zendesk integrations and allows administrators to migrate existing integrations before Zendesk deactivates API tokens, helping to maintain data action functionality.
Data action test UI improvements
Administrators can now use a JSON mode in the data action test UI to explicitly define input values as omitted, empty strings, or null. This enhancement provides greater control over test payloads and helps administrators more accurately reproduce and troubleshoot data action behavior observed in production.
Agentic virtual agent direct knowledge answer generation
Administrators can now configure agentic virtual agent knowledge tools to generate answers directly from retrieved knowledge using APT-2. Previously, the knowledge pipeline generated an answer and then used APT-2 to reformulate it. The new option bypasses these additional processing steps, helping to reduce response latency while keeping answers grounded in retrieved knowledge content.
Dynamic knowledge filtering for Agent Copilot
Administrators can now configure Agent Copilot to dynamically filter knowledge content based on customer and interaction context available at runtime. Administrators can select existing Agent Copilot context attributes and map them to applicability metadata associated with knowledge content. During an interaction, Agent Copilot resolves the configured context values and passes them to Knowledge Fabric, which filters the eligible knowledge content before retrieval and answer generation. This capability reduces irrelevant search results and helps agents receive knowledge that is more applicable to the customer and interaction they are handling.
Architect flow runtime variable memory insights
Administrators and flow authors can now view memory usage information for flow-authored variables in Architect. Flow execution data tracks the highest amount of variable memory used during a flow instance and identifies the execution item where that peak occurred. When replaying a supported flow, users can view the peak memory usage and navigate directly to the corresponding execution item. Architect also shows the initial size of individual variables. These insights help flow authors identify variables and execution paths that consume significant memory and troubleshoot inefficient variable usage before it affects flow execution.
Deprecation: Genesys Cloud login web app can no longer be embedded in an iframe
Genesys Cloud is extending the previously announced end-of-life date for existing integrations that load the Genesys Cloud login web app within an iframe from February 4, 2027, to September 27, 2027. New integrations that attempt to load the login web app in an iframe are already blocked. Existing integrations can continue to use iframe-based authentication during the extended transition period. By September 27, 2027, all application integrations must use pop-out authentication instead of loading the Genesys Cloud login web app in an iframe. This deprecation helps improve protection against clickjacking attacks.
Note:
- Genesys Cloud enables features for release starting on Tuesday and completing by the end of the day Friday, per region. If you do not see a feature enabled for your organization by the following business day, check the required subscriptions and permissions provided in the Release Notes and related documentation. If you confirm the subscription and permissions and still experience issues, contact Customer Care.
- Some features may require an integration add-on.
[NEXT] Was this article helpful?
Get user feedback about articles.