CRM & business applications

ServiceNow integration

Run customer service and service-desk conversations inside ServiceNow, powered by Genesys Cloud CX – designed, integrated and supported by certified Genesys specialists.

Genesys Cloud CX joined to the CRM Two large tiles face each other. On the left, a royal blue Genesys Cloud CX tile holds an agent and a screen-pop card showing the customer record. On the right, a dark CRM and ITSM tile holds the customer record with its fields, the last field marked green with a tick. An upper arrow carries the record from the CRM to the agent as a screen pop, and a lower arrow writes the interaction back to the record. CRM & BUSINESS APPS Genesys Cloud CX CRM · ITSM Screen pop Write-back

In summary

Our Genesys Cloud ServiceNow integration services bring customer conversations and service workflows together on one desktop. QVCCS designs and implements Unified Experience from Genesys and ServiceNow, routing voice, digital, case and incident work through Genesys Cloud and surfacing native call controls and interaction context in ServiceNow Agent Workspace, with statuses mapped across both platforms. For bespoke processes, our certified developers build data actions that let Architect flows and bots read and update ServiceNow records. Certified specialists from our own bench own the outcome, from requirements and design to testing and support.

Who works on this

  • Solution Architect
  • Senior Business Consultant / Business Analyst
  • Senior Developer
  • Systems Integration Tester
  • User Acceptance Test Lead
  • Support Engineer
  • One agent workspaceGenesys Cloud call controls and interaction context surfaced in ServiceNow Agent Workspace, so agents serve customers without switching applications.
  • Voice, digital and casesVoice, chat, email, callbacks, digital messaging, cases and incidents routed through Genesys Cloud to the right queue or agent.
  • Statuses in stepStatuses and attributes mapped between Genesys Cloud and ServiceNow, so agents are offered work in one place at a time.
  • ServiceNow data in flowsData actions give IVRs and bots live access to incidents, cases and requests for self-service and smarter routing.
DiagramGenesys Cloud CX and ServiceNow working as one
Unified ExperienceGenesys and ServiceNow
  • VoiceNative call controls
  • DigitalChat, email, messaging
  • CSM casesCase context and pop
  • ITSMIncidents and requests
  • PresenceStatuses synchronised
  • AI assistanceAgent Copilot embedded
  • Data actionsLookups in IVR and bots

Genesys Cloud handles conversations and routing; ServiceNow holds cases, incidents and workflow.

01

Why a Genesys Cloud ServiceNow integration matters

A Genesys Cloud ServiceNow integration joins the conversation to the workflow that resolves it. In many organisations, ServiceNow holds the cases, incidents, requests and knowledge that define how service is delivered, while the contact centre platform holds the calls and messages. When the two are separate, agents copy details between screens, case history is incomplete and supervisors struggle to connect contact volumes with service outcomes. When they work together, a customer or employee is recognised, routed with the context of their open work, and every interaction becomes part of the case record.

The relationship between the two companies is strategic: ServiceNow co-invested in Genesys alongside Salesforce, and Unified Experience from Genesys and ServiceNow is a published Genesys Cloud use case. For customer service leaders that means a jointly designed route to one desktop for agents. For architects it means a defined integration pattern rather than a bespoke build. QVCCS helps both audiences decide how far to go, from a focused ITSM service-desk integration to a full Customer Service Management deployment with AI assistance, and we capture that scope in a Business Requirements Document with MoSCoW priorities, so the first release delivers the journeys that matter most.

02

How Unified Experience from Genesys and ServiceNow works

Unified Experience from Genesys and ServiceNow routes ServiceNow work through Genesys Cloud and delivers it inside ServiceNow. Voice, chat, email, callbacks, digital messaging, cases and incidents can be routed to the appropriate queues or agents, across CSM, ITSM and HR Agent Workspaces, and native call controls and interaction context appear in the ServiceNow Agent Workspace. Case routing synchronises ServiceNow cases with Genesys Cloud work items, wrap-up codes are kept in step, and statuses and attributes are mapped between the platforms. Genesys Cloud embeddable components, such as Agent Copilot, can run directly in the ServiceNow experience. The integration is priced separately from core Genesys Cloud licences.

Implementation spans both platforms. In ServiceNow, the Unified Experience applications are installed, an application registry with a certificate enables OAuth JWT access, presence states are created and an OpenFrame configuration registers Genesys Cloud as the provider. In Genesys Cloud, OAuth clients, status, attribute and queue mappings are configured; an AppFoundry accelerator can create the supporting Genesys Cloud assets. Digital channels require the ServiceNow Zurich release or later, so we confirm prerequisites in discovery. Alongside Unified Experience, data actions can call ServiceNow APIs from Architect flows and bots, which suits bespoke workflows such as checking incident status or raising a request during self-service.

When the conversation and the case live on one desktop, agents spend their time resolving issues instead of moving information between systems.

QVCCS point of view

03

Designing routing, presence and case context

Bringing two routing-capable platforms together raises important design questions. Which work should Genesys Cloud route, and which should stay in ServiceNow? How do queues in Genesys Cloud map to assignment groups and workspaces in ServiceNow? Our architects work with your ServiceNow and contact centre teams to define the routing model, queue mappings and presence mapping, so agents are never offered a call while working a case they cannot leave, and supervisors can still see a complete picture of demand and capacity across both systems.

Context design determines the agent experience. We define how customers and employees are identified in the IVR or bot, which ServiceNow records should be shown or created for each interaction type, how Genesys Cloud participant data maps to ServiceNow fields, and how wrap-up information and notes are captured against the case or incident. For data actions, we write an Interface Control Document covering ServiceNow tables, fields, authentication, timeouts and error handling, so self-service never stalls. Security is agreed with your ServiceNow administrators and security team: the integration user and its roles, OAuth and certificate ownership, and which personal data moves between the platforms. Each decision is logged and traced back to its requirement.

Change control matters on both sides. ServiceNow releases arrive on their own cadence, Genesys Cloud updates continuously, and the Unified Experience applications have their own package versions. We document which components are vendor-supplied, which are configuration and which are custom, and agree with your ServiceNow platform team how upgrades are tested. That clarity prevents the most common long-term problem with CRM integrations: a small change on one platform breaking the agent experience on the other without anyone noticing until customers do. Our handover pack records all of it.

04

How QVCCS delivers your ServiceNow integration

A ServiceNow integration crosses two platform teams, so QVCCS musters a team from its own bench that works hand in hand with your ServiceNow platform owners or partner. A Senior Business Consultant / Business Analyst maps journeys, case and incident processes and writes the BRD and RTM, including which work each platform routes. A Solution Architect owns the HLD, routing and status mappings and the interface control documents. Senior Developers configure OAuth clients, queues, flows, data actions and scripts, and work with your ServiceNow team on the Unified Experience applications, certificates and presence states. A Systems Integration Tester and a User Acceptance Test Lead prove the service, and the Senior Platform Practice Lead reviews every design and build.

We test the whole service, not just the connection. The SIT pack, traced to the RTM, covers end-to-end journeys for every channel and workspace, status changes in both directions, case routing to work items, screen context and wrap-up synchronisation. Negative testing exercises expired certificates, failed OAuth tokens, data action timeouts and unavailable instances. Because the ServiceNow side has its own release and update-set discipline, we agree early which non-production ServiceNow instance pairs with which Genesys Cloud organisation, who promotes changes on each side and in what order, so a mapping changed in one platform is never tested against a stale version of the other.

05

Growing the ServiceNow integration

Many organisations start with one area, such as customer service or the IT service desk, and extend from there. HR and other ServiceNow workspaces can follow once the routing, status and context patterns are proven. QVCCS helps you plan that expansion in a continuous-improvement roadmap, reusing designs and data actions where they fit and adding queues, flows and mappings where they do not. We also help you add AI with care: virtual agents that check incident or case status, Agent Copilot embedded in the ServiceNow experience, and automation that keeps records complete. Each step is measured against resolution and effort in regular service reviews, so the integration keeps earning its place.

What you get from QVCCS

  • Assessment of Unified Experience and data action options and prerequisites
  • Routing, queue, status and attribute mapping across both platforms
  • Genesys Cloud OAuth clients, queues, flows and scripts built to the LLD
  • ServiceNow data actions specified in an interface control document
  • SIT pack, negative tests and UAT scripts traced to requirements
  • Upgrade and change-control approach agreed with your ServiceNow team
  • Support alongside your provider or direct, plus release impact assessments

Genesys documentation references

Checked against current official documentation, October 2026. Genesys releases weekly, so we re-validate every design against the live release notes.

  1. About Unified Experience from Genesys and ServiceNow – Genesys Cloud Resource Centerhelp.genesys.cloud
  2. Unified Experience from Genesys and ServiceNow – Genesys Cloud use casehelp.genesys.cloud
  3. Release notes for Unified Experience from Genesys and ServiceNowhelp.genesys.cloud
  4. Unified Experience from Genesys and ServiceNow – Genesys AppFoundryappfoundry.genesys.com
  5. About the web services data actions integration – Genesys Cloud Resource Centerhelp.genesys.cloud

Methods & templates

ServiceNow integration: the methods and templates we use

Every QVCCS engagement follows our seven-stage delivery lifecycle, each stage closed by a quality gate. For ServiceNow integration, the work concentrates in Define, Design, Prove and Run & evolve, and these are the techniques and standard templates we lean on there, each one traceable from requirement to design, build, test and support.

  1. 01DiscoverDiscovery sign-off
  2. 02DefineRequirements baseline
  3. 03DesignDesign authority review
  4. 04BuildBuild complete
  5. 05ProveGo / no-go readiness
  6. 06TransitionOperational acceptance
  7. 07Run & evolveService reviews
  • 2 · Define

    Business Requirements Document (BRD) with MoSCoW priorities

    Fixes which ServiceNow workspaces, channels and case types the first release covers, and what each journey must achieve.

  • 3 · Design

    High-Level Design (HLD) and design decision log

    Sets the routing model, queue-to-assignment mapping and status mapping, and records which work Genesys Cloud routes.

  • 3 · Design

    Interface Control Document (ICD)

    Specifies OAuth, certificates, attribute mappings and data action contracts between Genesys Cloud and your ServiceNow instance.

  • 5 · Prove

    SIT test pack

    Proves every channel, workspace, status change and case-to-work-item route end to end, traced to the requirements.

  • 7 · Run & evolve

    Release readiness reviews

    Assesses ServiceNow releases, Genesys Cloud updates and Unified Experience package versions before they reach agents.

See the full QVCCS delivery method

How we deliver

ServiceNow integration: one accountable team, start to finish

  1. 01DiscoverWorkshops with service, ServiceNow platform and contact centre owners on journeys, processes, channels and data.
  2. 02DesignArchitecture, routing and presence mappings, interface contracts and security model documented and agreed.
  3. 03BuildCertified developers configure Genesys Cloud and data actions, and partner with your team on ServiceNow applications.
  4. 04ProveSIT across channels, workspaces, status mapping and case routing, negative testing, then UAT with real agents.
  5. 05Run & extendHypercare, support aligned to your model, release reviews and a roadmap towards AI-assisted service in ServiceNow.

The specialists on this work, from our own bench

  • Solution Architect
  • Senior Business Consultant / Business Analyst
  • Senior Developer
  • Systems Integration Tester
  • User Acceptance Test Lead
  • Support Engineer

Every engagement follows our seven-stage method, with design authority, engineering standards and four-eyes peer review behind it. How we deliver →

Questions

ServiceNow integration: common questions

What is Unified Experience from Genesys and ServiceNow?

It is the joint integration that routes ServiceNow work, including voice, chat, email, callbacks, digital messaging, cases and incidents, through Genesys Cloud and delivers it in ServiceNow Agent Workspace with native call controls, interaction context and mapped statuses. Applications are installed in ServiceNow and configured in Genesys Cloud.

Can Genesys Cloud integrate with ServiceNow ITSM?

Yes. Unified Experience supports routing from ServiceNow ITSM, CSM and HR Agent Workspaces, and Genesys Cloud data actions can call ServiceNow APIs from Architect flows, bots and scripts, so service-desk callers can check incident status or raise requests.

Do we need a separate licence for the ServiceNow integration?

Unified Experience from Genesys and ServiceNow is priced separately from core Genesys Cloud licensing, and ServiceNow-side requirements depend on your products and release; digital channels need the Zurich release or later. We confirm prerequisites in discovery so licensing and platform versions are in place before build begins.

Last reviewed

Talk to a specialist about this

We work by introduction. Clients, partners and people introduced to us can reach the right specialist for this topic directly.

Who to contact