NICE CXone on Salesforce: Which Agent App You Run and What Moving to Salesforce Voice Takes

For NICE CXone customers, the first Open CTI question is surprisingly basic: which Salesforce app are we actually running? NICE has renamed several of its Salesforce agent applications, and the name you see in documentation, on AgentExchange and in Salesforce Setup can all differ.

This guide uses NICE’s own help center to sort that out, then walks through what NICE documents for setting up its Salesforce Voice app. We did not find a NICE-specific Open CTI retirement notice, so confirm your timeline with your NICE account team.

Step one: identify your NICE app

NICE’s Salesforce Agent Applications page lists the current product names alongside their previous names, AgentExchange listings and package names. Three are relevant:

• Unified Agent for Salesforce Voice (previously Agent for Service Cloud Voice). On AgentExchange it is “NiCE Agent for Salesforce Voice,” and in Installed Packages it shows as “CXone Agent for Service Cloud Voice.” Agents open it from the Omni-Channel widget’s Phone tab.
• Embedded Agent Workspace for Salesforce (previously CXone Mpower Agent Workspace for Salesforce). Its AgentExchange name is “NiCE Agent Workspace for Salesforce Embedded OpenCTI,” and agents open it from the Phone widget in Lightning.
• Salesforce Agent, the legacy app for Classic and Lightning, also opened from the Phone widget.

NICE explains that package names are set when a package is first published and cannot be changed after installation, which is why Setup may show an older name. The quick test: if agents take calls in the Omni-Channel widget, you are likely already on the Salesforce Voice app. If they use a separate Phone widget, ask NICE whether your app depends on Open CTI. The word “OpenCTI” in the Embedded Agent Workspace listing name is a strong hint.

What the Salesforce Voice app requires

NICE’s setup guide for Agent Workspace for Salesforce Voice lists several prerequisites that are worth checking well before a migration:

• Environment limits. NICE says the app cannot be used in Salesforce Hyperforce or GovCloud environments, because they are not currently supported.
• Licenses from Salesforce. Your org needs Partner Telephony licenses, bought through Salesforce. NICE also says multiparty licenses should be enabled by opening a case with Salesforce, or agents may have call control issues. Warm transfer and conference need Multi-party Conferencing and Consult permissions.
• No org namespace. The app has its own namespace and will not run in an org that already defines one.
• Naming conflicts. If you already have a contact center definition named “NICE CXone Contact Center,” rename it first or the install will fail.
• Presence. The app supports Salesforce presence statuses only, not CXone unavailable codes, so your status design moves into Salesforce.

NICE also notes that installing the app gives you a trial license with 25 seats that expires after 30 days, and that your account representative must raise a work order to activate a full license. Plan your pilot around that window.

Configuration details to plan for

The setup itself runs mostly in Salesforce: enabling Omni-Channel and Voice in Partner Telephony Setup, creating a presence status with the Phone channel, importing a NICE contact center XML file, creating a certificate, adding remote site settings, building a Lightning console app with Omni-Channel and Voice Calls, and enabling Lightning Web Security. NICE recommends turning off “Respect Agent Capacity” to avoid dropped inbound calls, with capacity handled through presence configurations instead.

What this means for your contact center

• Inventory first. Confirm which NICE package each team runs before you scope anything.
• Check your Salesforce environment. Hyperforce and GovCloud orgs need a direct conversation with NICE.
• Open Salesforce cases early for multiparty licenses and permissions; they gate transfers and conferences.
• Redesign presence in Salesforce, since CXone unavailable codes do not carry over.

If the requirements make you want to compare options, see how Vonage Contact Center for Salesforce handles voice and digital channels inside the same Omni-Channel workspace.

Sources

• NICE CXone Help: Salesforce Agent Applications
• NICE CXone Help: Set Up Agent Workspace for Salesforce Voice
• Salesforce Help: Open CTI Retirement