Genesys Cloud and ServiceNow integration: Unified Experience, routing and A2A

Genesys and ServiceNow announced a strategic partnership on 7 May 2024, and the result is Unified Experience from Genesys and ServiceNow. Genesys describes it as an integration that unifies customer service teams through a single desktop and centralises routing across departments and channels. Genesys's first release notes for it are dated 10 March 2025, and on 12 March 2025 Genesys announced it as available on the ServiceNow Store and the AppFoundry Marketplace. Genesys lists it as a separately priced add-on on its pricing hub.

Two older Genesys apps remain on the ServiceNow Store: the Genesys Cloud Connector, built on the Genesys Cloud Embeddable Framework, which supports screen pops of existing cases and interaction records, and Genesys External Routing, which adds presence sync and work assignment through Genesys Cloud routing. Beyond packaged apps, Genesys Cloud's Web Services Data Actions can call ServiceNow's JSON web services from Architect flows and scripts, which suits simple lookups or record updates without a desktop integration.

Genesys says Unified Experience routes ServiceNow interactions, including voice, case, chat, email, incident and digital messaging, through Genesys Cloud, and surfaces native call controls and interaction context directly in the ServiceNow Agent Workspace for customer service, IT service and HR teams. ServiceNow's own announcement puts it the same way: routing is centralised inside Genesys Cloud. Since the first release, Genesys has added the capabilities shown in the table.

On the ServiceNow side, two apps are installed in order, Unified Experience from Genesys Core and then Unified Experience from Genesys, and Genesys approval is needed before download. Genesys lists the plugins each workspace needs. The customer service workspace needs CSM Configurable Workspace, OpenFrame, Advanced Work Assignment with its External Routing Support plugin, Customer Central, the Interaction Control Component and IntegrationHub Starter. IT service management adds ServiceNow Voice for ITSM, and HR adds the HR agent workspace and HR core plugins, together with cross-scope privilege and restricted caller access records approved by a security administrator.

On the Genesys side, users need per-user Genesys Cloud licences, and Genesys's release notes list CX 1 with the digital add-on, CX 2 Digital, CX 2 with the WEM add-on, CX 3 or CX 3 Digital for external routing. Genesys's use-case page states the Yokohama release of the ServiceNow platform, and digital channels need Zurich or later, so confirm the instance release first. Authentication runs both ways: a Client Credentials OAuth client in Genesys Cloud with the conversation, messaging and integration permissions Genesys lists, and OAuth JWT through a ServiceNow application registry with a self-signed certificate.

• Unified Experience from Genesys Core, then Unified Experience from Genesys
• OpenFrame and Advanced Work Assignment with external routing support
• Workspace plugins for customer service, IT service management or HR
• A Genesys Client Credentials OAuth client with the listed permissions
• A ServiceNow application registry with a key pair for OAuth JWT

Routing is where the integration does most of its work. Genesys Cloud routes ServiceNow chats and cases alongside its own channels, while ServiceNow's Advanced Work Assignment provides the plumbing. In ServiceNow you create an AWA service channel and external queues whose provider is Genesys Cloud (Case) or Genesys Cloud (Workitem), referencing the Genesys queue and worktype. In Genesys Cloud, a workbin and worktype carry workitem attributes for the ServiceNow case and work item, so each routed record can be traced both ways.

Two rules catch teams out. Parent case routing must be in place before case task routing, which needs app version 1.1.0 or later, and each service channel needs its own utilisation conditions. For voice, Genesys asks for a phone service channel on the interaction table with the default work item size and capacity both set to one. Because Genesys Cloud makes the routing decision, skills, priorities, bullseye expansion and predictive routing apply to ServiceNow work just as they do to calls.

Status mappings set up bidirectional relationships between the two platforms' presence states, and Genesys asks you to define a fallback status in Genesys Cloud. ServiceNow's Offline status means an agent is unavailable for routing even when still logged in, which matters for how mappings are designed. Genesys does not state which system is the master, so we agree the presence model, including breaks and after-call work, before build and test it with real agent schedules.

For voice, an incoming call opens the interaction record in the Agent Workspace when auto-answer is used, and agents control the call from ServiceNow. Participant data collected in Genesys Cloud, for example in an IVR, can be passed into ServiceNow fields, but the mapping is one way and is applied only when the record is created. Plan the data journey accordingly: anything the flow learns later in the call needs another route into ServiceNow, such as a data action.

Live transcripts of voice interactions are published to ServiceNow automatically and remain afterwards in the Internal Transcript section of the interaction record. Genesys requires low-latency transcription for this, and transcription itself is a Genesys Cloud capability, covered in our speech and text analytics guide. After a transfer, Genesys notes that the first agent's last words may be attributed to the receiving agent, which is worth explaining to quality teams.

Agents can start, pause, resume and stop call recordings from ServiceNow, and pausing a call recording also pauses screen recording when it is enabled. Recordings stay in Genesys Cloud. Wrap-up codes configured on Genesys queues are fetched and shown to the agent in ServiceNow. Agents cannot enter after-call work retroactively, a timeout submits a system wrap-up code, and digital wrap-up works only in the customer service, IT service and HR workspaces.

In September 2025 Genesys and ServiceNow expanded their partnership to agent-to-agent orchestration, with a Genesys Cloud virtual agent collaborating with ServiceNow's AI agents. Genesys's help site documents how this will work through the External A2A Server integration, still marked as coming soon and in development: an agentic virtual agent delegates specialist tasks to external agents on platforms such as ServiceNow, remains the sole customer-facing owner of the conversation, and shares only the fields you map. Configuration uses an agent card URL with basic authentication or an OAuth grant.

Genesys's September 2026 announcement expects A2A interoperability with enterprise platforms such as Salesforce and ServiceNow to become generally available between November 2026 and January 2027, and also refers to Model Context Protocol connectivity. ServiceNow, for its part, describes its AI agents reaching external agents and tools through A2A. Until A2A is released, the practical pattern is a Genesys agentic virtual agent that calls ServiceNow through data actions, with the design ready to move to A2A delegation when it arrives.

Most limits are design decisions rather than blockers, but they belong in the plan from the start. Check the ServiceNow release against Genesys's stated requirements, and remember that digital channels need Zurich or later. Mapped participant data is written only at record creation, a workbin's division cannot be changed later, and HR routing depends on cross-scope and restricted caller access records being approved. Agent-to-agent delegation is not yet released, so any agentic design should work without it today.

• ServiceNow release: Yokohama stated; Zurich or later for digital channels
• Participant data mapping is one way, at record creation only
• No retroactive after-call work; timeouts submit a system wrap-up code
• Each AWA service channel needs its own utilisation conditions
• Workbin divisions are fixed once set
• A2A delegation is in development, not yet released

QVCCS leadership has worked in contact centre technology since 1984, and we design and build Genesys Cloud integrations with CRM and service management platforms, including ServiceNow. We start with which system owns each step, from routing and presence to records and wrap-up, then document the apps, plugins, OAuth clients, queues and mappings in an interface contract and test them end to end with real cases, incidents and calls. Every delivery team member holds, or is completing, Genesys Cloud certification, and we work remotely unless agreed otherwise.