Genesys Cloud FedRAMP Region – Features coming soon
This preview lists the features scheduled for the next Genesys Cloud FedRAMP region release. The features will not be live in Genesys Cloud FedRAMP region until March 9, 2026. The feature descriptions in the March 9, 2026 Genesys Cloud FedRAMP region Release Notes will contain links to the accompanying documentation in the Resource Center or Developer Center. For information about upcoming Genesys Cloud FedRAMP region feature releases, see the Feature releases and Announcements sections in Genesys Cloud FedRAMP region Release Notes.
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.
Administrators can now configure knowledge portals to return only articles that match specific knowledge base article labels. When users filter by label, the knowledge portal returns only articles tagged with that label. This update helps knowledge authors reuse a single article across multiple knowledge portals by applying different label sets, which reduces duplicate content and ongoing maintenance effort. The configuration is available through the knowledge APIs.
Administrators can now use pagination when retrieving lists of Messenger web deployments, configurations, and configuration versions through the API. Pagination improves performance when working with large or highly versioned lists and helps administrators manage growing records more efficiently. Results are returned in smaller segments, making it easier to navigate and process large datasets.
Increased limits for Messenger configuration and deployment counts
Administrators can now create up to 1,200 Messenger configurations and 1,200 Messenger deployments within a single organization. This increase helps organizations support more clients and deliver tailored web and mobile messaging experiences at scale. For organizations that require higher limits, requests can be made through Genesys Care.
Bring Your Own Technology (BYOT) ASR engines in Architect bot flows
Administrators can now integrate third-party automatic speech recognition (ASR) engines into Genesys Bot Flows with the new Bot Transcription Connector. After administrators configure the connector, bot authors can select a customer-provided ASR engine as the default transcription engine for a Bot Flow or for individual Ask for Slot actions. These options help improve speech recognition for specific languages, accents, and domains, while maintaining a single Bot Flow design.
Deprecation: Administrator login using only username and password
Genesys deprecated the ability for administrators to log in using only a username and password. Administrators must use multi-factor authentication (MFA) when they sign in to Genesys Cloud. This change applies to all administrator accounts with elevated access permissions, except those that authenticate through single sign-on (SSO) systems. Requiring MFA helps improve account security and reduces the risk of unauthorized access when login credentials are compromised.
Deprecation: Billing APIs and UI components update
On March 10, 2025, Genesys announced the planned deprecation of the following Billing APIs and related UI components as part of a transition to a new billing infrastructure.
Partner Billing Usage API: /api/v2/billing/trusteebillingoverview/{trustorOrgId} GET /v1/regions/{region}/organizations/{orgId}?appIds={appIds}
Premium Applications – Usage API – Individual Customer Subscription GET endpoint: billable-vendor-usage-api.usw2.pure.cloud/v1/regions/{region}/organizations/{orgId}?appIds={appIds}
Genesys has added the following APIs to the list of deprecated endpoints:
Overall Customer Count: GET /v1/regions?appIds={appIds}
Usage per customer within a region: GET /v1/regions/{region}/organizations?appIds={appIds}
Genesys will provide additional details, including API specifications, migration guidance, and confirmed deprecation timelines, as they become available.
Organizations using these APIs or the Billing & Usage UI should prepare to migrate to the new billing infrastructure once replacement capabilities are announced.