# Troubleshooting Webex Contact Center screen pops and empty CAD variables

Canonical: https://warmtransfer.net/knowledge/wxcc-screen-pop-troubleshooting

Last verified: 2026-10-02

In Webex Contact Center Flow Designer, a Screen Pop is a window or dialog box that appears in the agent's Desktop when the agent answers a customer call[^1]. Agents edit editable CAD variable values in Desktop text fields, and a global variable is shown on the Desktop only when its Make agent viewable toggle is on[^12][^21].

## How screen pops are triggered

The Screen Pop activity becomes relevant only after an agent is involved in the interaction, and it typically uses the AgentAccepted and PhoneContactEnded events[^2]. The Queue To Agent activity triggers the AgentAccepted event when an agent answers an inbound call[^3]. Cisco instructs that the Screen Pop activity configuration is completed in the Event Flows tab of Flow Designer[^13].

The Screen Pop activity takes a Screen Pop URL naming the intended website, plus Query Parameters into which flow variables can be entered in the payload[^58]. The Screen Pop Desktop Label field sets short custom display text that replaces the Screen Pop URL on the Agent Desktop[^14].

Screen Pop for new digital channels must be configured in Connect Flow Builder, not with the Flow Designer Screen Pop activity[^15]. The Webex Connect Screen Pop - WXCC node sends a screen pop message to the agent contact by calling the Webex Contact Center screen pop API[^38]. The node takes a Task ID, which is the flow transaction ID as a UUID, and an Agent ID from the routed event as inputs, along with the screen pop URL and query parameters[^42]. Its loading behaviour can be Inside Desktop, New Browser Tab or Existing Browser Tab[^39]. The node exits on onScreenpopSuccess or Queued for success, and on onError, onScreenpopFailure or onTimeout for failure[^41].

## Where the screen pop appears

The Flow Designer Screen Pop activity offers these display settings:[^19][^17][^18]

| Display setting | Behaviour |
|---|---|
| New browser tab | Opens in a new browser tab every time without affecting the existing Screen Pop[^19] |
| Existing Screen Pop tab | Loads inside the existing browser tab and replaces the previous Screen Pop[^17] |
| Inside Desktop | Appears as a tab in the Auxiliary Information pane of the Desktop[^18] |

In the Desktop Layout, Screen Pop can be configured as a custom page, as one of the widgets in a custom page, or as a tab in the Auxiliary Information pane[^34]. When Screen Pop is a custom page, agents open it from the Screen Pop icon on the Navigation bar; when it is a widget in a custom page, they open it from that custom page's icon[^37]. The Cisco Screen Pop widget is referenced in desktop layout JSON by the component name `agentx-wc-screen-pop`[^60]. Cisco's example Auxiliary Information pane configuration shows the Screen Pop tab with the property `"visibility": "SCREEN_POP"`[^6].

For voice, whether and where the Screen Pop displays depends on both the Desktop Layout configuration and the Screen Pop activity defined in Flow Designer[^59]. For new digital channels, Screen Pop display depends on the Desktop Layout configuration and the Screen Pop node defined in Connect Flow Builder[^16]. In the Agent Desktop, the screen pop shows only 1 URL at a time, in a tab labelled Screen Pop[^40]. Whether this one-URL limit also applies to voice screen pops configured in Flow Designer is not covered by the sources below.

The agent guide describes a screen pop as a window or tab on the Agent Desktop for conversations across all channels: voice, email, chat and social[^4]. The screen pop shows customer details for the agent's currently selected interaction[^48]. The Auxiliary Information pane holds tabs including Contact History, Customer Journey Widget, Screen Pop and custom widgets, and its display position depends on the type of the active request[^5].

The desktop layout also offers a separate iFrame widget, `agentx-wc-iframe`, that embeds a web page as a widget on the Desktop[^29]. Desktop $STORE variables are available only to Web Component widgets, not to iFrame widgets[^56]. Desktop $STORE variables update in real time so that widgets track the current Desktop state[^57].

## Diagnosing a screen pop that does not appear

Cisco's Desktop browser settings require pop-up blockers to be turned off[^46]. The same settings require JavaScript to be allowed to run and cookies and site data to be allowed[^7]. The desktop profile General settings include a Screen Popups toggle that specifies whether external pop-up screens are allowed[^47].

We infer that pop-up blocking most plausibly hits the New browser tab and Existing Screen Pop tab modes, which open browser tabs, rather than Inside Desktop, which renders in the Auxiliary Information pane[^32].

WarmTransfer's reading of the sources is that a Screen Pop activity placed in the main flow before an agent is connected is unlikely to pop, because Cisco ties the activity to post-agent events such as AgentAccepted in the Event Flows tab[^31].

For voice, check both the Desktop Layout and the Flow Designer Screen Pop activity, because display depends on both[^59]. For new digital channels, check the Desktop Layout and the Connect Flow Builder Screen Pop node[^16]. On the Screen Pop - WXCC node, an exit on onError, onScreenpopFailure or onTimeout indicates failure[^41].

See also [Troubleshooting Webex Contact Center desktop layout and widget errors](https://warmtransfer.net/knowledge/wxcc-desktop-layout-troubleshooting).

## Diagnosing a wrong or stale screen pop

WarmTransfer's reading of the sources is that a screen pop showing the wrong customer may simply reflect a different selected interaction, or a reused tab under the Existing Screen Pop tab mode, before any CRM lookup fault is suspected[^33]. The screen pop shows customer details for the currently selected interaction[^48]. Under the Existing Screen Pop tab setting, each new Screen Pop replaces the previous one in the same browser tab[^17].

## Diagnosing empty CAD and global variables

A global variable is shown on the Desktop, with the value set during the flow, only when its Make agent viewable toggle is on[^21]. Global variables are defined in Control Hub, but flow developers must add them to a flow as required before the flow can use them[^20]. Global variables cannot be added directly in a subflow; a global variable can only be mapped from the main flow to a local variable in the subflow[^26]. Global variables cannot be deleted, only deactivated when no flow uses them, and an inactive global variable cannot store data[^24].

We infer that an agent-viewable variable that shows blank on the Desktop most likely was never assigned in the running flow, was not added to that flow, sits in a subflow without mapping, or is an inactive global variable[^30].

The incoming call popover on the Agent Desktop shows a minimum of 3 and a maximum of 6 variables[^44]. The incoming popover does not display variables that the administrator has marked as secure[^45].

The Edit on Desktop toggle on an agent-viewable global variable lets the agent edit the variable value during the interaction session[^23]. Agents edit editable CAD variable values in the Desktop text fields and must click Save for the change to be kept[^12].

Other global variable limits also apply:[^28][^27][^25]

- A string global variable holds at most 256 characters[^28].
- At most 100 global variables can be enabled for reporting[^27].
- The Name and Variable type of an existing global variable cannot be edited[^25].

See also [Troubleshooting Webex Contact Center flows](https://warmtransfer.net/knowledge/wxcc-flow-troubleshooting).

## Salesforce connector screen pops

In the Salesforce Version 2 integration, the objects selected in the Salesforce Softphone Layout are the objects searched to trigger the lookup and screen pop on an inbound call[^53]. Screen pop happens only for inbound calls; for internal and outbound calls a search runs and results appear in the connector, but no screen is popped[^52]. For the Salesforce connector to show the name of a found record, the Softphone Layout for that record type must include the Name field[^54].

The Remove ANI Prefix Strings setting takes a comma-separated list of prefixes, such as country codes, that are stripped from the inbound ANI before record matching[^50]. Salesforce advanced screen pop is configured with the name of a CAD variable that holds the ID to be searched in the Softphone Layout[^51]. Cisco's 5 May 2026 release added Screenpop ANI Fallback for Salesforce only, which searches Salesforce by the caller's ANI when the primary customer data is unavailable[^49].

See also [Troubleshooting Webex Contact Center CRM connectors](https://warmtransfer.net/knowledge/wxcc-crm-connector-troubleshooting).

## Webex Calling Customer Assist

In Webex Calling Customer Assist, screen pop on inbound calls is available only in the Webex App desktop client[^9]. Customer Assist screen pop applies only to the primary line, not to secondary or shared lines configured on the Webex App[^10].

## See also

- [Setting up screen pops and CAD variables in Webex Contact Center](https://warmtransfer.net/knowledge/wxcc-screen-pop-setup)
- [Webex Contact Center Flow Designer architecture](https://warmtransfer.net/knowledge/webex-cc-flow-designer)
- [Webex Contact Center Agent Desktop and widgets](https://warmtransfer.net/knowledge/webex-cc-agent-desktop)
- [Webex Connect Flow Builder node reference](https://warmtransfer.net/knowledge/webex-connect-node-reference)
- [Pebble template syntax and filters in Flow Designer](https://warmtransfer.net/knowledge/pebble-template-expressions)

## Applicability

Applies to: Cisco Webex Contact Center, Cisco Webex Connect, Cisco Webex Contact Center for Salesforce, and Cisco Webex Calling Customer Assist. Deployments: multi-tenant. Sources checked 2026-10-02. The Salesforce screen pop behaviour described here applies to the Salesforce Version 2 integration[^53]. Screenpop ANI Fallback was added in Cisco's 5 May 2026 release[^49].

## What remains uncertain

How to inspect a Flow Designer Screen Pop activity at run time to confirm whether it fired is not covered by the sources below. Which variables the incoming call popover selects when more than 6 variables are agent-viewable is not covered by the sources below. Whether the Salesforce ANI prefix and advanced screen pop settings interact with Screenpop ANI Fallback is not covered by the sources below.

## Sources

[^1]: In Webex Contact Center Flow Designer, a Screen Pop is a window or dialog box that appears in the agent's Desktop when the agent answers a customer call. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Activities in Contact Handling > Screen Pop. Checked 2026-10-02.
[^2]: The Screen Pop activity becomes relevant only after an agent is involved in the interaction and typically uses the AgentAccepted and PhoneContactEnded events. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Activities in Contact Handling > Screen Pop. Checked 2026-10-02.
[^3]: The AgentAccepted event is triggered by the Queue To Agent activity when an agent answers an inbound call. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Event flows. Checked 2026-10-02.
[^4]: The agent guide describes a screen pop as a window or tab on the Agent Desktop for conversations across all channels: voice, email, chat and social. Source: [Get started with Agent Desktop](https://help.webex.com/en-us/article/itebdl/Get-started-with-Agent-Desktop), Screen Pop. Checked 2026-10-02.
[^5]: The Auxiliary Information pane holds tabs including Contact History, Customer Journey Widget, Screen Pop and custom widgets, and its display position depends on the type of the active request. Source: [Get started with Agent Desktop](https://help.webex.com/en-us/article/itebdl/Get-started-with-Agent-Desktop), Auxiliary information pane. Checked 2026-10-02.
[^6]: Cisco's example Auxiliary Information pane configuration shows the Screen Pop tab with the property "visibility": "SCREEN_POP". Source: [Create custom desktop layout](https://help.webex.com/en-us/article/ng08gqeb/Create-custom-desktop-layout), Auxiliary Information Pane (JSON example). Checked 2026-10-02.
[^7]: Cisco's Desktop browser settings require JavaScript to be allowed to run and cookies and site data to be allowed. Source: [System requirements for Webex Contact Center Desktop](https://help.webex.com/en-us/article/besrkt/System-requirements-for-Webex-Contact-Center), Browser settings. Checked 2026-10-02.
[^8]: As of the 2026-09-01 update, the Desktop minimum supported browsers are Chrome 144, Microsoft Edge 144 and Firefox 140 or later. Source: [System requirements for Webex Contact Center Desktop](https://help.webex.com/en-us/article/besrkt/System-requirements-for-Webex-Contact-Center), Minimum system requirements. Checked 2026-10-02.
[^9]: In Webex Calling Customer Assist, screen pop on inbound calls is available only in the Webex App desktop client. Source: [Webex Calling Customer Assist](https://help.webex.com/en-us/article/72sb3r/Webex-Calling-Customer-Assist), Screen pop configuration section. Checked 2026-10-02.
[^10]: Customer Assist screen pop applies only to the primary line, not to secondary or shared lines configured on the Webex App. Source: [Webex Calling Customer Assist](https://help.webex.com/en-us/article/72sb3r/Webex-Calling-Customer-Assist), Screen pop configuration section. Checked 2026-10-02.
[^11]: Customer Assist screen pop URLs take variables such as NewPhoneContact.ANI, NewPhoneContact.DNIS, AgentAnswered.AgentID and AgentAnswered.QueueName as key-value query parameters. Source: [Webex Calling Customer Assist](https://help.webex.com/en-us/article/72sb3r/Webex-Calling-Customer-Assist), Screen pop configuration section (variables table). Checked 2026-10-02.
[^12]: Agents edit editable CAD variable values in the Desktop text fields and must click Save for the change to be kept. Source: [Manage your calls in Agent Desktop](https://help.webex.com/en-us/article/mmcf7p/Manage-your-calls-in-Agent-Desktop), Edit CAD variables section. Checked 2026-10-02.
[^13]: Cisco instructs that the Screen Pop activity configuration is completed in the Event Flows tab of Flow Designer. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Activities in Contact Handling > Screen Pop. Checked 2026-10-02.
[^14]: The Screen Pop Desktop Label field sets short custom display text that replaces the Screen Pop URL on the Agent Desktop. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Activities in Contact Handling > Screen Pop > URL Settings. Checked 2026-10-02.
[^15]: Screen Pop for new digital channels must be configured in Connect Flow Builder, not with the Flow Designer Screen Pop activity. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Activities in Contact Handling > Screen Pop. Checked 2026-10-02.
[^16]: For new digital channels, Screen Pop display depends on the Desktop Layout configuration and the Screen Pop node defined in Connect Flow Builder. Source: [Create custom desktop layout](https://help.webex.com/en-us/article/ng08gqeb/Create-custom-desktop-layout), Screen Pop (list after 'displayed on the Desktop based on the following factors'). Checked 2026-10-02.
[^17]: With the Existing Screen Pop tab display setting, the Screen Pop loads inside the existing browser tab and replaces the previous Screen Pop. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Activities in Contact Handling > Screen Pop > Display Settings. Checked 2026-10-02.
[^18]: With the Inside Desktop display setting, the Screen Pop appears as a tab in the Auxiliary Information pane of the Desktop. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Activities in Contact Handling > Screen Pop > Display Settings. Checked 2026-10-02.
[^19]: With the New browser tab display setting, the Screen Pop opens in a new browser tab every time without affecting the existing Screen Pop. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Activities in Contact Handling > Screen Pop > Display Settings. Checked 2026-10-02.
[^20]: Global variables are defined in Control Hub but flow developers must add them to a flow as required before the flow can use them. Source: [Manage global variables](https://help.webex.com/en-us/article/ngfdsbi/Manage-global-variables), Overview. Checked 2026-10-02.
[^21]: A global variable is shown on the Desktop, with the value set during the flow, only when its Make agent viewable toggle is on. Source: [Manage global variables](https://help.webex.com/en-us/article/ngfdsbi/Manage-global-variables), Create a global variable. Checked 2026-10-02.
[^22]: A global variable's Desktop Label is shown on the Desktop in place of the variable name and can be at most 50 characters. Source: [Manage global variables](https://help.webex.com/en-us/article/ngfdsbi/Manage-global-variables), Create a global variable. Checked 2026-10-02.
[^23]: The Edit on Desktop toggle on an agent-viewable global variable lets the agent edit the variable value during the interaction session. Source: [Manage global variables](https://help.webex.com/en-us/article/ngfdsbi/Manage-global-variables), Create a global variable. Checked 2026-10-02.
[^24]: Global variables cannot be deleted, only deactivated when no flow uses them, and an inactive global variable cannot store data. Source: [Manage global variables](https://help.webex.com/en-us/article/ngfdsbi/Manage-global-variables), Activate or deactivate a global variable. Checked 2026-10-02.
[^25]: The Name and Variable type of an existing global variable cannot be edited. Source: [Manage global variables](https://help.webex.com/en-us/article/ngfdsbi/Manage-global-variables), Edit a global variable. Checked 2026-10-02.
[^26]: Global variables cannot be added directly in a subflow; a global variable can only be mapped from the main flow to a local variable in the subflow. Source: [Manage global variables](https://help.webex.com/en-us/article/ngfdsbi/Manage-global-variables), Overview. Checked 2026-10-02.
[^27]: At most 100 global variables can be enabled for reporting. Source: [Manage global variables](https://help.webex.com/en-us/article/ngfdsbi/Manage-global-variables), Create a global variable (Reportable). Checked 2026-10-02.
[^28]: A string global variable holds at most 256 characters. Source: [Manage global variables](https://help.webex.com/en-us/article/ngfdsbi/Manage-global-variables), Create a global variable (variable type String). Checked 2026-10-02.
[^29]: The desktop layout offers a separate iFrame widget, agentx-wc-iframe, that embeds a web page as a widget on the Desktop. Source: [Create custom desktop layout](https://help.webex.com/en-us/article/ng08gqeb/Create-custom-desktop-layout), page > agentx-wc-iframe. Checked 2026-10-02.
[^30]: An agent-viewable variable that shows blank on the Desktop most likely was never assigned in the running flow, was not added to that flow, sits in a subflow without mapping, or is an inactive global variable (inferred). Source: [Manage global variables](https://help.webex.com/en-us/article/ngfdsbi/Manage-global-variables), Overview; Activate or deactivate a global variable. Checked 2026-10-02.
[^31]: A Screen Pop activity placed in the main flow before an agent is connected is unlikely to pop, because Cisco ties the activity to post-agent events such as AgentAccepted in the Event Flows tab (inferred). Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Activities in Contact Handling > Screen Pop. Checked 2026-10-02.
[^32]: Pop-up blocking most plausibly hits the New browser tab and Existing Screen Pop tab modes, which open browser tabs, rather than Inside Desktop, which renders in the Auxiliary Information pane (inferred). Source: [System requirements for Webex Contact Center Desktop](https://help.webex.com/en-us/article/besrkt/System-requirements-for-Webex-Contact-Center), Browser settings (combined with Flow Designer > Screen Pop > Display Settings). Checked 2026-10-02.
[^33]: A screen pop that shows the wrong customer may simply reflect a different selected interaction, or a reused tab under the Existing Screen Pop tab mode, before any CRM lookup fault is suspected (inferred). Source: [Get started with Agent Desktop](https://help.webex.com/en-us/article/itebdl/Get-started-with-Agent-Desktop), Screen Pop (combined with Flow Designer > Screen Pop > Display Settings). Checked 2026-10-02.
[^34]: In the Desktop Layout, Screen Pop can be configured as a custom page, as one of the widgets in a custom page, or as a tab in the Auxiliary Information pane. Source: [Create custom desktop layout](https://help.webex.com/en-us/article/ng08gqeb/Create-custom-desktop-layout), Screen Pop. Checked 2026-10-02.
[^35]: Webex Contact Center allows a maximum of 5000 active global variables per tenant. Source: [System limits in Webex Contact Center](https://help.webex.com/en-us/article/n7s6ed7/System-limits-in-Webex-Contact-Center), Table 1. Maximum system limits for configuration entities and attributes, row Global variables. Checked 2026-10-02.
[^36]: Webex Contact Center allows a maximum of 200 active desktop layouts. Source: [System limits in Webex Contact Center](https://help.webex.com/en-us/article/n7s6ed7/System-limits-in-Webex-Contact-Center), Table 1. Maximum system limits for configuration entities and attributes, row Desktop layouts. Checked 2026-10-02.
[^37]: When Screen Pop is configured as a custom page, agents open it from the Screen Pop icon on the Navigation bar; when it is a widget in a custom page, they open it from that custom page's icon. Source: [Create custom desktop layout](https://help.webex.com/en-us/article/ng08gqeb/Create-custom-desktop-layout), Configuring Screen Pop in the Navigation Bar. Checked 2026-10-02.
[^38]: The Webex Connect Screen Pop - WXCC node sends a screen pop message to the agent contact by calling the Webex Contact Center screen pop API. Source: [Screen Pop - WXCC](https://help.webexconnect.io/docs/wxcc-screen-pop), Screen Pop - WXCC (introduction). Checked 2026-10-02.
[^39]: The Screen Pop - WXCC node's loading behaviour can be Inside Desktop, New Browser Tab or Existing Browser Tab. Source: [Screen Pop - WXCC](https://help.webexconnect.io/docs/wxcc-screen-pop), Display Settings - Screen Pop Loading Behavior. Checked 2026-10-02.
[^40]: In the Agent Desktop, the screen pop shows only one URL at a time, in a tab labelled Screen Pop. Source: [Screen Pop - WXCC](https://help.webexconnect.io/docs/wxcc-screen-pop), Screen Pop - WXCC (limitation note). Checked 2026-10-02.
[^41]: The Screen Pop - WXCC node exits on onScreenpopSuccess or Queued for success and on onError, onScreenpopFailure or onTimeout for failure. Source: [Screen Pop - WXCC](https://help.webexconnect.io/docs/wxcc-screen-pop), Node outcomes. Checked 2026-10-02.
[^42]: The Screen Pop - WXCC node takes a Task ID (the flow transaction ID as a UUID) and an Agent ID from the routed event as inputs, along with the screen pop URL and query parameters. Source: [Screen Pop - WXCC](https://help.webexconnect.io/docs/wxcc-screen-pop), Input variables table. Checked 2026-10-02.
[^43]: Customer personally identifiable information in the interaction control pane stays masked when sensitive data protection is enabled. Source: [Get started with Agent Desktop](https://help.webex.com/en-us/article/itebdl/Get-started-with-Agent-Desktop), Interaction control pane (note). Checked 2026-10-02.
[^44]: The incoming call popover on the Agent Desktop shows a minimum of three and a maximum of six variables. Source: [Manage your calls in Agent Desktop](https://help.webex.com/en-us/article/mmcf7p/Manage-your-calls-in-Agent-Desktop), Incoming call popover / accept a call section. Checked 2026-10-02.
[^45]: The incoming popover does not display variables that the administrator has marked as secure. Source: [Manage your calls in Agent Desktop](https://help.webex.com/en-us/article/mmcf7p/Manage-your-calls-in-Agent-Desktop), Incoming call popover / accept a call section. Checked 2026-10-02.
[^46]: Cisco's Desktop browser settings require pop-up blockers to be turned off. Source: [System requirements for Webex Contact Center Desktop](https://help.webex.com/en-us/article/besrkt/System-requirements-for-Webex-Contact-Center), Browser settings. Checked 2026-10-02.
[^47]: The desktop profile General settings include a Screen Popups toggle that specifies whether external pop-up screens are allowed. Source: [Manage desktop profiles](https://help.webex.com/en-us/article/nvaf71f/Manage-desktop-profiles), Create a desktop profile > General settings. Checked 2026-10-02.
[^48]: The screen pop shows customer details for the agent's currently selected interaction. Source: [Get started with Agent Desktop](https://help.webex.com/en-us/article/itebdl/Get-started-with-Agent-Desktop), Screen Pop. Checked 2026-10-02.
[^49]: Cisco's 5 May 2026 release added Screenpop ANI Fallback for Salesforce only, which searches Salesforce by the caller's ANI when the primary customer data is unavailable. Source: [What's new for administrators in Webex Contact Center](https://help.webex.com/en-us/article/a1gx3h/What's-New-in-Webex-Contact-Center), May 05, 2026 > Enhancements to CTI Connectors for Salesforce, ServiceNow, and Microsoft Dynamics. Checked 2026-10-02.
[^50]: The Salesforce connector's Remove ANI Prefix Strings setting takes a comma-separated list of prefixes such as country codes that are stripped from the inbound ANI before record matching. Source: [Integrate Webex Contact Center with Salesforce (Version 2-New)](https://help.webex.com/en-us/article/dyidod/Integrate-Webex-Contact-Center-with-Salesforce-(Version-2-New)), Standard Screen Pop / Advanced Screen Pop settings. Checked 2026-10-02.
[^51]: Salesforce advanced screen pop is configured with the name of a CAD variable that holds the ID to be searched in the Softphone Layout. Source: [Integrate Webex Contact Center with Salesforce (Version 2-New)](https://help.webex.com/en-us/article/dyidod/Integrate-Webex-Contact-Center-with-Salesforce-(Version-2-New)), Advanced Screen Pop settings. Checked 2026-10-02.
[^52]: In the Salesforce Version 2 integration, screen pop happens only for inbound calls; for internal and outbound calls a search runs and results appear in the connector but no screen is popped. Source: [Integrate Webex Contact Center with Salesforce (Version 2-New)](https://help.webex.com/en-us/article/dyidod/Integrate-Webex-Contact-Center-with-Salesforce-(Version-2-New)), Screen pop section (note). Checked 2026-10-02.
[^53]: In the Salesforce Version 2 integration, the objects selected in the Salesforce Softphone Layout are the objects searched to trigger the lookup and screen pop on an inbound call. Source: [Integrate Webex Contact Center with Salesforce (Version 2-New)](https://help.webex.com/en-us/article/dyidod/Integrate-Webex-Contact-Center-with-Salesforce-(Version-2-New)), Softphone Layout configuration step. Checked 2026-10-02.
[^54]: For the Salesforce connector to show the name of a found record, the Softphone Layout for that record type must include the Name field. Source: [Integrate Webex Contact Center with Salesforce (Version 2-New)](https://help.webex.com/en-us/article/dyidod/Integrate-Webex-Contact-Center-with-Salesforce-(Version-2-New)), Screen pop section (note). Checked 2026-10-02.
[^55]: Behaviour when no Salesforce record matches is set in the Softphone Layout Screen Pop Settings, which support popping to a new record of a chosen object type. Source: [Integrate Webex Contact Center with Salesforce (Version 2-New)](https://help.webex.com/en-us/article/dyidod/Integrate-Webex-Contact-Center-with-Salesforce-(Version-2-New)), Softphone Layout > Screen Pop Settings. Checked 2026-10-02.
[^56]: Desktop $STORE variables are available only to Web Component widgets, not to iFrame widgets. Source: [Enhancing Webex Contact Center Widgets with Dynamic $STORE Variables](https://developer.webex.com/blog/enhancing-webex-contact-center-widgets-with-dynamic-store-variables), article body, $STORE overview. Checked 2026-10-02.
[^57]: Desktop $STORE variables update in real time so that widgets track the current Desktop state. Source: [Enhancing Webex Contact Center Widgets with Dynamic $STORE Variables](https://developer.webex.com/blog/enhancing-webex-contact-center-widgets-with-dynamic-store-variables), article body, $STORE overview. Checked 2026-10-02.
[^58]: The Screen Pop activity takes a Screen Pop URL naming the intended website, plus Query Parameters into which flow variables can be entered in the payload. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Activities in Contact Handling > Screen Pop > URL Settings. Checked 2026-10-02.
[^59]: For voice, whether and where the Screen Pop displays depends on both the Desktop Layout configuration and the Screen Pop activity defined in Flow Designer. Source: [Create custom desktop layout](https://help.webex.com/en-us/article/ng08gqeb/Create-custom-desktop-layout), Screen Pop (list after 'displayed on the Desktop based on the following factors'). Checked 2026-10-02.
[^60]: The Cisco Screen Pop widget is referenced in desktop layout JSON by the component name agentx-wc-screen-pop. Source: [Create custom desktop layout](https://help.webex.com/en-us/article/ng08gqeb/Create-custom-desktop-layout), Configuring Screen Pop in the Navigation Bar > Example: Screen Pop as a Custom Page. Checked 2026-10-02.