Third-party data integration for CSM
Summarize
Summary of Third-party data integration for CSM
The third-party data integration feature in ServiceNow Customer Service Management (CSM) enables agents to access real-time data from external applications directly within Agent Workspace without storing this data in the ServiceNow instance. This integration addresses the common challenge of fragmented agent experiences caused by using multiple systems and enhances productivity by consolidating customer context from various sources, such as Salesforce, into a unified view.
Show less
Key features
- Real-time data retrieval: Uses remote tables to fetch frequently changing data from third-party systems dynamically when accessed by agents.
- Display flexibility: Allows viewing of third-party data in lists, forms, pop-up windows, sub tabs, and related items within Agent Workspace, including embedded iframes and direct links to external records.
- Secure integration: Employs OAuth 2.0 – JWT Bearer grant type for secure connections and supports domain separation to restrict data access based on user domains.
Configuration essentials
To enable third-party data integration for CSM, system administrators must:
- Activate required plugins: Remote Tables, OAuth 2.0, IntegrationHub, and Customer Service.
- Set up OAuth 2.0 – JWT Bearer grant for authentication between ServiceNow and third-party applications.
- Create and configure remote tables and remote table script definitions to map and retrieve external data.
- Manage connection credentials using aliases and configure appropriate access controls (ACLs) on remote tables.
- Customize lists and forms to present the third-party data effectively within Agent Workspace.
Benefits for ServiceNow customers
- Enhances agent productivity by consolidating customer data from multiple systems into a single interface.
- Improves customer service quality with comprehensive, up-to-date information available in real time.
- Reduces data redundancy and storage needs by avoiding duplication of third-party data.
- Supports secure and compliant data access through domain separation and OAuth authentication.
The third-party data integration feature enables you to retrieve data from third-party applications and display the data in Agent Workspace for CSM without having to store it in your ServiceNow instance.
Many enterprise customers use ServiceNow applications as part of their IT ecosystems. In these environments, ServiceNow applications coexist with other applications and exchange data through different types of integrations. For customer service agents who typically use a wide variety of applications, this can create a fragmented experience that impacts agent productivity and increases customer wait time.
A frequent integration takes place between ServiceNow and Salesforce applications. In this integration, customers use Salesforce to manage pre-sales activities and ServiceNow to manage post-sales activities. These post-sales activities represent service assurance.
To provide high quality service, agents using the Customer Service Management (CSM) application need a complete understanding of the customer's context, and this includes access to customer data maintained in other systems. A common example of this integration is enriching a CSM customer profile by providing a list of opportunities related to the customer's account. These opportunities are retrieved from Salesforce in real time and are presented in Agent Workspace for CSM.
Using the third-party data integration feature, data from third-party applications can be retrieved as needed. Agents can view the data in lists and forms. This feature uses remote tables to store the third-party data in memory on the application server. Remote tables are useful for data that changes frequently because the data is retrieved in real-time when a user accesses the data from the ServiceNow AI Platform.
Activating third-party data integration
- Remote Tables (com.glide.script.vtable): Adds the Remote Table Script Definition table (sys_script_vtable) and adds the Remote Table flag to the Tables (sys_db_object) table. Active on the base instance.
- OAuth 2.0 (com.snc.platform.security.oauth): Adds the OAuth-related tables and extension points needed to support OAuth 2.0 –JWT Bearer grant type. Active on the base instance.
- IntegrationHub (com.glide.hub.integrations): Provides the ability to build reusable integrations with third-party systems and call them from anywhere in the platform. IntegrationHub requires subscription and is available in several subscription packages. Different packages allow for different levels of automation and provide different subsets of predefined third-party integrations, or spokes. For more information, see Request IntegrationHub and IntegrationHub available spokes.
- Customer Service (com.sn_customerservice)
Configuring third-party data integration
- Setting up the OAuth 2.0 – JWT Bearer grant type, which provides the connection between the ServiceNow instance and the third-party application.
- Setting up aliases to manage connection information and credentials when integrating with external systems and providing alias reference to the IntegrationHub action.
- Creating a remote table to store the third-party data.
- Creating a remote table script definition that maps the data from the third-party application table to the remote table.
- Configuring ACLs for the remote table to provide user access to the third-party data.
- Configuring the lists and forms that display data from the remote table.
Using third-party data integration
- View read-only data from third-party applications in lists and forms.
- View data from multiple third-party applications in one browser tab.
- View data from third-party applications in pop-up windows, sub tabs, and related items using iframes.
- Open links to third-party application records from forms.
Domain separation
Remote table script definitions are domain separated. If users do not have access to the same domain as the remote table script definition record, they cannot access records from the remote table specified in the script definition.
The data within the remote table is not domain separated.
For more information, see Domain separation and remote tables.