CX Cloud from Genesys and Salesforce implementation: a technical guide

Genesys describes CX Cloud from Genesys and Salesforce as a solution that integrates Genesys Cloud CX and Salesforce Service Cloud, bringing voice, digital and CRM data from Genesys Cloud into Service Cloud Voice. It connects the two platforms at an API level, with Genesys capabilities embedded directly in the Salesforce workspace, so Genesys channels flow into Salesforce's own interaction layer. Genesys Cloud still routes and carries the interaction; Salesforce is where the agent works and where the records live.

The integration is delivered as managed packages from Salesforce AppExchange. Salesforce calls the product Salesforce Voice with partner telephony, formerly Service Cloud Voice with partner telephony, and Genesys acts as the telephony provider. Underneath, the integration uses Lightning Web Components, Apex classes and Omni-Channel features of Salesforce, and Genesys notes that the exact configuration is unique to each customer environment. That is why a build starts with a clear decision about which packages, channels and routing model the contact centre needs.

The base package, called CX Cloud from Genesys and Salesforce in Genesys's text and Core Services in package lists, contains the components needed to set up the contact centre in Salesforce, and every other package lists it as a prerequisite. An admin Lightning app with the CX Cloud Genesys Settings tab is then used to install and update the other packages and to create and manage contact centres. The table summarises the packages Genesys lists.

On the Salesforce side, Genesys states that voice, digital and external routing features need a Salesforce Service Cloud Voice licence, and Salesforce says Voice is available only in Lightning Experience, as an add-on to Agentforce Service and Agentforce Sales. Omni-Channel must be enabled, and Voice with partner telephony switched on in Partner Telephony Setup. Salesforce also notes that Voice is not supported on Salesforce Mobile or iPad, and asks customers to check regional availability with their Salesforce representative.

On the Genesys side, Genesys lists per-user Genesys Cloud licences plus add-on licences for the Salesforce integration, with the integration permissions for administrators and agents set out in its requirements article. A self-signed certificate and private key authenticate telephony requests between the platforms. Agents need a current Chrome, Firefox or Edge with third-party cookies allowed for the Salesforce domain, and for voice-only agents Genesys recommends setting maximum capacity to zero for every interaction type except calls and callbacks.

Genesys's documentation follows a fixed order: install the CX Cloud package from AppExchange into production or a sandbox, configure remote site settings, create and launch the admin Lightning app, install the Voice package, update packages, and configure OAuth. Remote sites must include the Genesys apps and login URLs for your region, and the API URL as well if you install Digital and AI or External Routing; Genesys notes these can be added automatically during installation.

For Core Services, Genesys uses an OAuth client of the Client Credentials grant type, created in Genesys Cloud with the minimum permissions Genesys lists and entered, with its region, in the CX Cloud Genesys Settings tab, where a Test button confirms the connection. Digital and AI and voice transcription use a separate OAuth client of the Code Authorization with PKCE grant type, whose redirect URI points at your own Salesforce Lightning domain. Keeping both clients documented, with their scopes and owners, saves time later, particularly after a sandbox refresh.

In the Salesforce console you build a contact centre Lightning app with console navigation, adding the Genesys Cloud CX Utility and the Omni-Channel utility and setting the Genesys utility to start automatically. Presence statuses such as Available, Available for Voice and Busy are created and assigned to profiles, agents receive the Contact Center Agent (Partner Telephony) permission set, and administrators the Contact Center Admin set. Genesys states it is mandatory to add its callback state and schedule callback components to the Voice Call record page.

The contact centre itself is created from an XML file generated with a display name, the Genesys Cloud region, a long distance prefix and the public key, then uploaded in Salesforce's Partner Telephony Contact Centers page with Genesys Cloud selected as the provider. On the Genesys side, the CX Cloud integration is configured with the OAuth client, group filtering and the private key, and set to active. Users are then added to the contact centre; Genesys and Salesforce both note that a user can belong to only one contact centre at a time.

CX Cloud can synchronise call attributes to custom fields on the Salesforce VoiceCall object for inbound and outbound calls. You create a custom field in Salesforce, then map it to the attribute in the contact centre settings. Genesys states that the integration can map any attribute set before the call leaves the agent's queue for Salesforce, and that Lightning will not save attributes to fields the Salesforce user cannot access, so field-level security has to be part of the design. The table lists the attributes Genesys documents.

Screen pops are driven by participant data. Setting the GC_SCREEN_POP attribute in an Architect flow pops a specific Salesforce page for inbound calls and callbacks, and for outbound campaigns a GC_SCREEN_POP column in the contact list does the same. The pop can be a standard Salesforce page, a Visualforce page or a new record page pre-populated with data from the flow. Genesys notes that only Lightning pages are supported, that Classic URL pops are not, and that the new-record URL format is not an API Salesforce officially supports.

There is no documented feature that creates a Case automatically from a voice call. For voice, the documented routes are a screen pop to a new or existing record, and Salesforce's own caller matching, which tries to match the phone number to a contact and lets the agent search or create one. For digital, Genesys documents automatic stitching: with first name, last name, email and case number set as participant data, Digital and AI finds or creates the Contact and connects to the Case. For linking records afterwards, the VoiceCall VendorCallKey contains the Genesys conversation ID.

Transcription is done by Genesys, not Salesforce. Voice transcription must be enabled at organisation and queue level in Genesys Cloud, with low latency transcription on, and the Genesys Cloud CX Voice Transcript component in Salesforce only displays transcripts that Genesys has generated, alongside Salesforce's Enhanced Conversation component. Both the Voice and the Digital and AI packages are needed, and recent package releases extended transcription to non-ACD calls, callbacks and outbound preview calls.

After-call work happens in a Genesys component on the Voice Call record. Agents choose wrap-up codes and can review AI-suggested summaries and wrap-up codes through features such as Agent Copilot, which Genesys adds through its embeddable component. When the agent submits after-call work, Genesys saves the notes to the Description field and the wrap-up code to the Call Resolution field of the VoiceCall record, the first time only; later edits are not synchronised in either direction. Plan any reporting on summaries around that behaviour.

With the Voice package, Genesys routes the call and Salesforce Omni-Channel presents it. Genesys notes that the call must appear in Omni-Channel before it is answered, that the call record must exist in Salesforce before the call is marked connected, and that transfers should always start from Omni-Channel. Agent status is kept in step by a mandatory status mapping between Omni-Channel and Genesys Cloud presence, for example Available for Voice to On Queue, with an optional enhanced status sync that uses an extension class in Salesforce.

External Routing turns this around for Salesforce work items. Salesforce queues use External Routing as their routing model, Salesforce queues are mapped to Genesys Cloud queues, and Genesys's ACD routes Cases, Email-to-Case and Messaging Sessions for Enhanced Chat; Legacy Chat and other object types are not supported. Salesforce data can travel to Genesys as participant data, such as case priority and status, and a recent release added mapping from Genesys conversation attributes to custom fields on Case and Messaging Session records.

Salesforce's guidance for sandboxes running Voice is to use only a Partial Copy refresh, because a full refresh means setting Voice up again, and to work with the telephony provider on provider-specific steps. Genesys publishes no separate refresh procedure, so after any refresh we check the settings that are specific to each Salesforce org: the Salesforce organisation ID in the Genesys integration, OAuth redirect URIs on the Lightning domain, remote sites, the contact centre, certificate and keys, and the OAuth credentials in the CX Cloud Genesys Settings tab.

Genesys lists other limits to design around: each agent in a broadcast ring group receives an individual VoiceCall record, Salesforce caps calls at six participants, and Salesforce's own auto-accept option cannot be scoped to some queues or used for progressive and predictive campaigns. Genesys Cloud for Salesforce, the Open CTI integration, was deprecated on 23 March 2026 and retires with Open CTI on 28 February 2028. The two integrations can run side by side, with each Salesforce user on one or the other, so most teams move in phases.

We start with the decisions that shape everything else: which packages, which channels, whether Genesys or Salesforce routes digital work, what data the agent needs on screen, and how transcripts and summaries will be used. From there we build Architect flows that set the participant data the Salesforce fields and screen pops rely on, configure both platforms in a sandbox, test with real call types, and plan the cut-over from Genesys Cloud for Salesforce in waves.

QVCCS leadership has worked in contact centre technology since 1984, and every delivery team member holds, or is completing, Genesys Cloud certification. We work remotely unless agreed otherwise. Our Salesforce integration guide covers the commercial choice and the Open CTI deadline, and our Service Cloud Voice transcripts guide goes deeper on live and post-call transcripts.