Skip to main content
8x8 Support

Salesforce screen pop does not work


When you are logged into the 8x8 Work for Salesforce Integration communication panel (the dialer), inbound and outbound calls do not generate a Salesforce tab or window pop for the associated phone number.

Applies To

  • 8x8 Work for Salesforce Integration
  • Integration version 2.8
  • Integration version 3.1


The most common causes for not receiving a screen pop from the 8x8 Salesforce integration are:

  • Web Browser Issues:
    • Popups are disabled in the web browser.
    • The web browser cache is corrupted.
  • 8x8 Communication Panel Settings
    • Call pops are incorrectly configured in the 8x8 communication panel.
    • The supported Salesforce object has been disabled for search.
  • Salesforce Issues / Unknown Calls
    • The called/calling phone number is not associated with a supported Salesforce object.
    • Person Accounts are not supported.
    • Phone fields have been customized.
    • Salesforce Field-Level security permissions cause all call searches to fail.
  • Calls Have Multiple Matches


Web Browser Issues

Pop-Up Settings

The 8x8 Salesforce integration relies on window or tab pops, so browser popups must be enabled for call pops to work properly.

Please verify that popups are enabled/allowed in the web browser settings:

Browser Cache

Your web browser's cache is possibly corrupted with invalid information.

This can easily be fixed by performing one of the following:

As a test, try logging in to a different web browser, either on the same computer or on a different computer. This can help determine where the problem is if clearing the browser cache fails to resolve the issue.

8x8 Communication Panel Settings

Behavior Settings for the Integration v2.8

  1. Navigate to Menu > Settings > Behavior.
  2. Ensure that Screen pop on inbound call is set to Ringing or Connected.
    • Note: When enabled, the Pop a record during a call option allows screen pops for new calls while you are already connected to another call. If this option is disabled (gray), you'll still see additional call notifications in the comm panel, but no screen pop will occur unless you initiate them.
  3. Click Save and Close.

clipboard_eeac4a16ea615bbe16593efc1052be283.png  clipboard_e10e03b09e15e7d1344e80fa603c5357b.png  clipboard_e0816e712ddaeca069861bec34c0234f4.png

Behavior Settings for the Integration v3.1

Unlike v2.8, the integration v3.1 does not have settings to change call Behavior. The default behavior for v3.1 is to pop a new tab for single-match caller recognition.

Salesforce Object Search Support

One or more supported Salesforce objects may have been disabled for search in the agent's 8x8 communication panel.

If a phone number exists only in Salesforce objects that search has been disabled for (such as Contacts), the display will show Unknown and no screen pop will occur for that number.


Salesforce objects supported for search are:

  • Contact
  • Opportunity
  • Account
  • Lead
  • Case

To fix this:

  1. Navigate to the following, depending on the integration version you're using:
    • v2.8: Menu > Settings > CRM Objects to search
    • v3.1: Settings (gear icon) > Integrations > Salesforce > Search Types
  2. Verify and/or enable (green) the Salesforce object types you want searched when calls are received or initiated.
  3. For v3.1, changes are immediate. For v2.8, click Save and Close at the bottom of Settings to enable any changes.


Note-Icon.png Note: FAX phone fields are not supported by the integration in any Salesforce object.

Salesforce Issues

The called/calling phone number is not associated with a supported Salesforce object

When calls are made or received, the 8x8 integrations search through the user's Salesforce org to match the called or calling number.

If that phone number is not assigned to a Salesforce object supported by the integration such as an Account or Contact, the number match will fail.

In this case, the integration will display the phone number as Unknown, and no call pop can occur.

Person Accounts

It's possible that phone numbers in Salesforce are assigned to a Person Account. Person Accounts are a rare type of Salesforce object that have been converted from Contacts by Salesforce itself, at customer request.

Salesforce Person Accounts are not (and will not be) supported by the 8x8 Salesforce integration, and will not pop records on inbound or outbound phone calls.

Phone Field Customization

If the Salesforce Phone fields in a supported object (such as Contacts) have been significantly customized, phone numbers for inbound and outbound calls could fail to be recognized by the 8x8 integration, and will not pop a tab or window.

Changes like this are made by a Salesforce administrator/developer, and cannot be resolved by an end user without Salesforce Administrator role access.


Note that simply re-naming the Phone field label does not normally break this function.

Salesforce Field-Level security permissions cause call searches to fail

Field-Level Security of Salesforce object fields must be set to Visible, within the user profile assigned to an 8x8 integration user. If this is disabled, all search activity performed by the integration will fail.

Note that this setting also affects contact searches from the integration's Search tab.

The details of this specific cause, and its resolution, are fully documented in this article:


Calls Have Multiple Matches

When calls are received or initiated, the integration searches all supported Salesforce objects that are enabled in the comm panel for a match against the called or calling phone number.

When more than one object matches the phone number, the comm panel will display Multiple Match, and no call pop will occur.

In this case, the agent must manually assign the correct Salesforce object to the call. The agent can also open/pop that object from the 8x8 comm panel.

While integrations v2.8 and v3.1 look a little different, the process is the same for both:

clipboard_ee35a5c5988cad66c137a825a5298e759.png  clipboard_edd7aa46c6dd467d15d166e63bc45e9f6.png  clipboard_e8b7e3a9b22bc49023c02afd4484f17b7.png