Genesys Cloud Composable Desktop: Genesys components inside your CRM

Most contact centres that run a CRM or help desk want agents to stay in it: the customer record, the case and the history are there, and switching windows costs time on every interaction. Genesys has offered ways to bring its contact centre into other applications for years, but they have mostly embedded Genesys Cloud as one block, a softphone or a full client in a side panel, with limited control over what appears and where.

Two things are moving the question up the agenda. Salesforce will retire Open CTI on 28 February 2028, and Genesys's Open CTI integration retires with it, so every Salesforce contact centre on that integration needs a new route. And organisations that built their own desktops, on Microsoft Dynamics 365, ServiceNow or custom web applications, want Genesys capabilities such as Agent Copilot or scripts inside those desktops without rebuilding them. The Composable Desktop SDK is Genesys's answer to the second need.

Genesys describes the Composable Desktop SDK as a way for developers to embed Genesys Cloud user interfaces into desktop or third-party applications, providing a modular framework for integrating Genesys Cloud capabilities into environments such as CRM systems, service consoles or custom enterprise applications. Instead of each team building its own communication layer between Genesys Cloud and the host application, the SDK exposes an event-based API that manages the integration.

Genesys lists three core capabilities. Authentication establishes and maintains a Genesys Cloud session inside the host application. Localisation keeps language and regional settings in step between Genesys Cloud and the host. Interaction context exchanges data about the current interaction in both directions between the embedded Genesys component and the host, so a component can show, for example, the Copilot suggestions for the call the agent is handling in the CRM record on screen.

• Build custom agent desktops that combine Genesys Cloud components with your own workflows.
• Integrate through standard event hooks rather than hard-coded integrations.
• Leave authentication and localisation updates to the SDK, reducing maintenance.
• Control how Genesys Cloud is presented and used inside your application.

The host application, such as a CRM page, loads Genesys's embedded desktop and the components it needs in iframes, and exchanges messages with them through the browser's standard postMessage interface. Inside the embedded desktop, a broker loads and orchestrates the components. Genesys describes the broker as a central service that manages all communication between embedded components and Genesys Cloud: shared authentication, API access, WebSocket connections for real-time updates, and synchronisation across browser tabs. Each component is a self-contained application in its own iframe that relies on the broker for all of that.

Genesys serves the static parts from its content delivery network, while runtime operations such as authentication and interaction management go through the Genesys Cloud Public API. Before a component can exchange data, it completes a short handshake with the broker, shown below. Interaction context is scoped: in the embedded scope, each embedded session has its own scope identifier, and setting an interaction affects only the components in that scope.

The Composable Desktop SDK handshake, from Genesys's requirements page (message names as Genesys documents them)

Host page                         Composable Desktop broker
---------                         -------------------------
GET_STATUS            --------->
                      <---------  STATUS_UPDATE (authenticated: true)
REGISTRATION_REQUEST  --------->
                      <---------  REGISTRATION_RESPONSE

Once registered:
SET_LOCALE            --------->  (language and region)
SET_INTERACTION       --------->  (a Genesys Cloud interaction ID, for one scope)
                      <---------  LOCALE_UPDATE / INTERACTION_UPDATE

Composable Desktop is not self-service yet. Genesys's requirements say the Genesys Cloud organisation must be onboarded for Composable Desktop SDK use, must have access to the components, and that the component names to be embedded are allow-listed by Genesys's Composable Desktop team during onboarding. Users need the right Genesys Cloud permissions for each component. Customers install a Genesys Cloud Composable Desktop integration in their own organisation and list the components to enable; AppFoundry partners can publish their own integration, with Genesys's approval, for customers to enable from AppFoundry.

The host application must embed components in iframes, run JavaScript to send and receive SDK events, allow a pop-up window for Genesys Cloud sign-in when the user is not already signed in, and keep iframe state while the user stays on the page. Your network must allow outbound access to Genesys Cloud's domains for your region and WebSocket connections; where you enforce a Content Security Policy, it must allow Genesys Cloud iframe sources, and third-party cookies must not be blocked. Genesys supports the latest Chrome, Microsoft Edge and Firefox.

The runtime limits matter for design. The table sets out the ones Genesys documents. The practical consequence is that Composable Desktop suits a desktop built around a few well-chosen Genesys components, such as Copilot or scripts beside the case record, rather than recreating the whole Genesys Cloud workspace inside another application.

Composable Desktop joins a set of options that already exist, and for many organisations one of them remains the right choice. The Genesys Cloud Embeddable Framework puts a version of Genesys Cloud's contact centre services inside your own systems: Genesys says it supports call, callback, outbound dialling, email, message and ACD voicemail interactions, and recommends running Genesys Cloud alongside it for fuller functionality. Genesys also offers packaged embedded clients and two vendor-built unified desktops, and, in the other direction, Client Applications that bring a web application such as a CRM inside Genesys Cloud.

For ServiceNow, Genesys already documents an Embeddable Component that integrates core contact centre capabilities into ServiceNow's configurable workspace, with components including Agent Copilot, Agent Stats, Queue Activation, Scripter, Station Selection and WEM Activity. It shows the direction Composable Desktop generalises to any host application.

Start from where your agents should spend their day, not from the technology. If they live in Salesforce, CX Cloud is Genesys's documented path after Open CTI. If they live in ServiceNow, Unified Experience or the Embeddable Component already exist. If they work mainly in Genesys Cloud, Client Applications bring the CRM to them. Composable Desktop is strongest where the desktop is your own or highly configured, such as Microsoft Dynamics 365, a case management system or a custom web application, and where you want specific Genesys capabilities placed exactly where agents need them.

Whichever route you choose, treat the desktop as a product with its own design, interface contract and testing. Decide which events pass between the host and Genesys Cloud, who owns each piece of interaction data, what happens when a page refreshes mid-call, and how agents recover from a lost session. Those questions decide whether agents trust the desktop on a busy Monday morning far more than the choice of framework does.

QVCCS designs and builds agent desktops on Genesys Cloud CX for organisations that run their service in a CRM, a help desk or their own applications. We start by mapping the agent's working day and the data each step needs, then recommend the route on its merits: a packaged integration, a vendor desktop, Composable Desktop or a custom build. Our Solution Architects record the decision and its trade-offs in the high-level design, and the events and data exchanged between host and Genesys Cloud become an interface contract that both sides build and test against.

Our developers then build and integrate the desktop under four-eyes peer review, and our testers prove it end to end, including the failure paths that matter most on a desktop: page refreshes, expired sessions, blocked pop-ups and network policy. Every delivery team member holds, or is completing, Genesys Cloud certification, and the work is delivered remotely unless agreed otherwise.