SupportLogic Data Integration Guide

Overview

SupportLogic pulls the data from your support ticketing system and analyzes it to create actionable insights and time-saving workflows for customer support managers, agents, customer success, and more. Signals and sentiment are extracted from your support cases and analyzed to generate early warnings, predict escalations, alert of potential customer churn, and surface coachable insights for your agents.

The data integration process is designed to be:

  • Secure: Control of your data always resides with you. Self-service OAuth is used to establish a data connection and never stores the credentials to your CRM. Data is encrypted end-to-end both in transit and at rest.
  • Granular: You keep full control over the data that gets synced. Use the permissions of the API user provided by your CRM administrator to control which tables, columns, and records are synced.
  • Non-intrusive: The ingestion process ensures that your CRM system is never overwhelmed and that API limits are never exceeded. Data is piped using differential sync (meaning only modified records are synced) and initial syncs are scattered to reduce the load on your system. Ingestion is designed so that users of your CRM system will never notice a difference in performance.
  • Flexible: Your data can be ingested directly from your CRM or from a secondary data source of your choosing (such as Cloud SQL) as long as schema is preserved.

During onboarding, your data and case lifecycle are analyzed to include your existing customizations. Machine learning (ML) models are then tuned to your case history to deliver insights specific to your organization.

SupportLogic integrates with your identity provider to support single sign-on (SSO). IT involvement is required during onboarding to set up SSO permissions. In total, onboarding requires coordination across three integrations that typically involve IT:

  • CRM user access
  • SSO integration
  • Communications tool integration (Slack or Teams)

This guide explains how your data connects to the pipeline and the process used to integrate your case history and custom fields.

Data Connection

Your data is transformed through an ELT (extract, load, transform) connection. An ELT (rather than ETL) setup allows for a more robust integration, with the following benefits:

  • Lighter system load
  • Shorter load time, making extraction easier on your system
  • Decoupled load and transform, meaning data analysis models can be rolled out faster

The data connector is TLS 1.2+ certified and runs securely over SSL using REST APIs hosted in an isolated virtual private cloud (VPC). From the VPC, your data is transformed using a set schema.

See Data Sync Detail and the diagram below for a high-level overview of the data pipeline.

High-Level Data Pipeline View

Data Filtering

SupportLogic takes the security of your data seriously. Several options are available for filtering any data you wish to exclude from the application. There are four ways to limit the data that gets processed:

  • Option 1: Limit the permissions of the CRM user account used to connect to the pipeline. This method stops unwanted cases or case info from leaving your CRM.
  • Option 2: SupportLogic has a Global Platform Filter that filters out record types, queues, and anything else that is not needed to be seen in the UI. This method adds a middle entity between your CRM and the pipeline and blocks cases or case info from getting to the pipeline.
  • Option 3: Filter data from the SupportLogic UI, using data scopes and profile scopes. This method ingests all cases and then uses global rules to block case and data types within the SupportLogic application.
Filter Options Throughout the Data Pipeline
Excluding Rows or Columns

Data exclusion boils down to two methods:

Column-based exclusion: Columns are the data fields attached to each support case (date opened, case comments, requester name, and so on). The data connector performs this type of exclusion by default and certain columns can be excluded during setup.

Row-based exclusion: Rows are the actual support cases (each case represents a row in the database). There are multiple methods for excluding specific rows of data:

  • Limit the permissions of the read-only CRM account used for data extraction.
  • Copy specific rows to a secondary data source, then connect to the pipeline.
  • Sync all data and then filter it immediately upon arrival in the system.

Customization

To ensure your customizations are included in the integration, SupportLogic establishes communication channels with the following personnel in your organization:

  • CRM Administrator/Data Architect
  • SSO Administrator
  • Communications Administrator

We integrate the custom fields in your standard tables as well as the custom fields in your custom tables and recommend syncing as many of your custom fields as possible during the initial sync. The following processes help capture your CRM customizations:

Customer Surveys

  • An initial survey on the display of data within the SupportLogic user interface and the data structures involved in your ticketing system, such as those used for case comments.
  • A followup survey on the specific case escalation process, data, and objects—specific to your usage and implementation.

Lifecycle Walkthrough

We go through the typical lifecycle of a case, your escalation process, and any regular reporting performed across your cases, escalations, and agents. The following is also discussed:

  • Bot usage
  • Case comment mechanism
  • Inter-team communication (Email, Slack, Teams, and so on)
  • Case reassignment
  • Priority and severity levels
  • Engineering ticketing systems (JIRA, and so on)
  • SLAs
  • Follow-the-sun models
  • Survey data
  • Important case fields

API Writeback

SupportLogic supports bidirectional sync via a writeback API, enabling users to make updates to CRM records directly from within the SupportLogic interface. This capability simplifies workflows by allowing customer support managers and agents to take action on cases without switching systems.

Supported writeback actions include:

  • Change case status
  • Update case priority
  • Assign or reassign a case
  • Add a case note
  • Post a public comment or reply to the customer

These actions are available once the appropriate write permissions are granted by your CRM administrator to the SupportLogic API user. During onboarding, you specify which case fields should be write-enabled. SupportLogic configures and tests the integration using sample data to ensure accuracy and reliability.

In addition to workflow actions, SupportLogic can push predictive signals such as sentiment and attention scores into your CRM. These scores are written to custom fields that are created collaboratively during onboarding, or they can be accessed via the Data Cloud. Once in your CRM, these scores can be used for reporting, filtering, and prioritizing cases.

CRM Widget

SupportLogic offers embedded CRM widgets that allow your team to view SupportLogic insights natively within your CRM. There are two supported widget options:

  • A lightweight iFrame widget, which is quick to deploy and requires minimal configuration
  • A Salesforce-native widget, available via AppExchange (class and lightning)

The iFrame widget operates by dynamically inserting the SupportLogic case view into the CRM interface using the case ID. It becomes active once a case has been ingested into the SupportLogic platform, which typically occurs within 10 minutes of case creation.

SupportLogic also offers a custom-managed app version of the widget for customers who prefer to maintain their own deployment. This custom widget supports insights at the case, account, and agent levels and provides deeper contextual integration.

Supported platforms for the lightweight widget include Salesforce, Zendesk, Freshdesk, ServiceNow, Dynamics, and Jira.

Your SupportLogic Solutions Architect will work with your CRM administrator to configure the CRM widget.

Slack & Teams Integration

SupportLogic integrates with both Slack and Microsoft Teams to deliver real-time, actionable alerts to your support and customer success teams. These integrations allow users to stay informed and take action without leaving their messaging environment.

Slack offers the most comprehensive functionality, including:

  • Acknowledging escalations directly from alert messages
  • Taking case-level actions such as assignment or status changes
  • Viewing summarized case, account, and agent insights
  • Navigating directly to the relevant case in SupportLogic or the CRM

SupportLogic alert cards in Slack are designed to reduce context switching and help teams collaborate around real-time signals. Microsoft Teams support includes alert delivery and context, with Slack offering a broader range of in-message interactivity.

Gainsight Integration

When you connect SupportLogic to your CRM, the signals in your ticketing system can be pushed to the Timeline or a Custom Object within Gainsight.

SupportLogic then connects to Gainsight via API. To enable this, we recommend that you create a user in Gainsight with appropriate permissions. On the SupportLogic side, you can provide Gainsight connection details such as Gainsight domain, Gainsight API key, and the email of the user that created for this integration. Once the connection is established, SupportLogic will automatically push notable events to Gainsight.

Three types of predictions are sent to the Gainsight Timeline:

  • Language patterns from support cases that predict a Customer Churn Risk
  • Predictions on cases that are Likely to Escalate (LTE)
  • Negative sentiments expressed by the customer in support cases, such as Profanity, Frustration and Lack of Progress.

For additional information on how signals appear on Gainsight, see the Gainsight integration page.

Data Mapping

The initial integration can be done in less than 7 hours, with the total setup process typically taking 4-6 weeks. This process is spent understanding the nuances of your data and tuning it to match the schema. We spend the bulk of the time analyzing, understanding, and replicating your support model.

Data scientists then verify a series of test cases to ensure the machine learning models are processing correctly. At this point in the integration, we collaborate with you to ensure your case data is successfully translated, revisiting the mapping schema to fix any issues. Once the data schema is set, the previous year of your data is loaded and used to train the ML models to your specific customer and case history, setting trend analysis.

The ML models take your data and combine and manipulate it to create signals, sentiments, and new categories of data. Raw data elements are then combined with the frequency of tangential data points to create new metrics that are statistically analyzed. Our schema is centered around the following objects in your CRM system, each containing different types of data that help tune the ML models to accurately detect and predict.

  • Account/Customer
  • Escalation Status
  • Case/Incident/Ticket
  • Group/Queue
  • Case History
  • User/Agent
  • Case Comments

For a detailed look at the minimum recommended data objects, see data schema by CRM at the end of this guide. For additional information on the usage of these objects, contact your SupportLogic Account Executive to speak with a Solutions Architect.

Ontology Tuning

Ontology tuning means specific terms that appear in your support environment can be added to the application to make your workflow easier. For example, the term “network” can cover a collection of terms such as tcp, ip, tcp/ip, network, Ethernet, udp, ping, dns, and so on. When you search for “network” within SupportLogic, it automatically encompasses all the similar terms defined in your ontology. This enables you to search for terms and keywords across all cases, as well as report on occurrences of those terms.

Key Points

The ML and workflows in SupportLogic SX are designed to give you fast time to value. After onboarding, we create a schedule to discuss your use of SupportLogic, capture any issues you may encounter, and discuss feature enhancements that can improve your experience as you use the application across your organization.

General Time Commitment:

  • CRM Admin: 1–2 hours to set up the initial connection and filters
  • Support team: ~10 hours across the onboarding period to validate and support training

Continue to the sections below for specific information on CRM setup and data schemas.

For additional details on data integration or to see a demo of the application, contact your SupportLogic Account Executive.

Data Sync Details

FeatureDetails
Syncing methodologyDifferential incremental sync—never overwhelming your source.
Sync frequency 5 minutes or more (1-minute sync planned).
Connectivity management Completely self-service, integrated natively into the application.
Data blocking Omits specific tables, rows, or columns from sync.
Column hashing Anonymizes sensitive data.
Full re-sync support Fixes data integrity issues with a full re-sync. Syncs can be performed at table level.
History Maintains table history and tracks schema changes.
Priority first sync Fetches most recent data first.
Connection status/alert Sends automatic alerts to the destination of your choice.

Freshdesk Integration Guide & Schema

To connect your Freshdesk instance to SupportLogic SX, you need:

  • A Freshdesk account with active subscription.
  • An account with owner/admin privileges.

Find Subdomain

Find your subdomain in your Freshdesk URL. For example, if your URL is https://yoursubdomain.freshdesk.com, then your subdomain is yoursubdomain.

Find API Key

  1. Go to your Freshdesk dashboard (for example, https://yoursubdomain.freshdesk.com/helpdesk).
  2. Click on your profile image in the top right corner, then select Profile settings.
  3. In the Profile settings page, find your API Key on the right side of the page and make a note of it. You will need it for configuration.

Finish Configuration

Work with a SupportLogic Solutions Architect to finish configuration:

  1. Enter your chosen destination schema name in the connector setup form.
  2. Enter your subdomain that you found in Step 1
  3. Enter your API key that you found in Step 2.
  4. Click Next to complete the data sync.
Freshdesk Schema
ObjectUsage
companyTracks back-and-forth conversations between your agents and the customer. Used to analyze sentiment.
company_domainTracks customer information.
agentTracks Freshdesk users (typically an individual account or user who has opened a case—this can be a customer or engineer).
contactTracks any user that does not have a full account in Freshdesk but has been attached to a case or case comment.
ticketTracks case information.
conversationTracks conversations and messages within cases. Used to analyze sentiment.

Jira Integration Guide

To connect your Jira instance to SupportLogic SX, you need your Jira host name, your port, and a connecting user with the following permissions:

  • Administer Projects or Browse Projects to view projects, their issues, and related entities like versions,
    components, and boards. Learn more in Jira’s managing project permissions documentation. If you use issue security schemes, the user must have a sufficient security level.
  • Administer Projects to view project roles and their actors.
  • Browse users and groups global permission to view users and groups. Learn more in Jira’s managing global permissions documentation.
  • Administrators or Service Desk Team project role to have an access to Jira Service Management (formerly Jira Service Desk). 
  • Administer Jira global permission to view permission and issue security schemes and related entities, as well as to register webhooks for capturing deleted entities like issues and projects.
Jira Cloud Setup Instructions
  1. In the connector setup form, enter the Destination schema name of your choice.
  2. Enter the name of your Jira Host.
  3. Enter your Port number.
  4. Choose the Authentication Type. If you choose Basic, create an API token. In the User field, enter the email address for the Atlassian account you’ve used to create the token. Use the created API token as a Password. If you choose OAuth, configure the Application Link. Click Authorize to allow access to your data. NOTE: Refer to Atlassian’s OAuth Troubleshooting Guide if you see the “oauth_problem=XXXXX” error when you click Authorize.
  5. Choose the issue sync mode: From all projects or From selected projects.
  6. If you choose From selected projects, select the projects whose associated issues you’d like to sync.
  7. Click Save & Test to complete the data sync.

Microsoft Dynamics Integration Guide & Schema

To connect your Microsoft Dynamics instance to SupportLogic SX, you need:

  • A Microsoft Dynamics 365 account
  • An Azure Active Directory tenant

Find Domain Name

  1. Log on to your Azure account.
  2. Click your account on the top right-hand corner, and then select Switch directory.
  3. On the Directory + subscription pane, choose the Active Directory tenant that has a subscription to Dynamics365.
  4. In the Manage Azure Active Directory section of the Azure portal dashboard, click the View button.
  5. On the left-hand navigation menu, select Overview.
  6. In the Overview section, make a note of the domain name that appears below your organization name. You will need it for configuration.

Find Resource URL

  1. Log on to your Dynamics 365 instance.
  2. Click Settings, and then select Customizations.
  3. Select Developer Resources.
  4. In the Developer Resources window, copy the Service Root URL. You will need it for configuration.

Finish Configuration

Work with a SupportLogic Solutions Architect to finish configuration:

  1. Enter your chosen destination schema name in the connector setup form.
  2. Enter the domain name that you found in Step 1.
  3. Enter the resource URL that you found in Step 2.
  4. Click Save & Test to complete the data sync.
Microsoft Dynamics Schema
ObjectUsage
accountTracks customer information.
systemuserTracks Dynamics users (typically an individual account or user who has opened a case—this can be a customer or engineer).
contactTracks customer information.
incidentTracks case information.
adx_ portalcommentTracks conversations and messages within cases. Used to analyze sentiment.
emailTracks conversations and messages within cases. Used to analyze sentiment.
stringmapTracks case history information.

Salesforce Integration Guide & Schema

To connect your Salesforce instance to SupportLogic SX, you need:

  • Access to an active Salesforce account
  • A Salesforce Enterprise level account plan or higher, or purchased Salesforce API calls
  • Enable field history tracking (optional). Read the Salesforce documentation to learn how to enable field history tracking.

Disable session IP locking

If you have Session IP Locking enabled or get an INVALID_SESSION_ID error, go to the Session Settings page and uncheck the Lock sessions to the IP address from which they originated box. It is very rare that this setting needs to be updated (<1% of cases), because by default it is already disabled for the majority of users.

Create new user and profile in Salesforce

To set up a Salesforce connector, you can use any Salesforce user within your organization that has permission to read data from Salesforce’s APIs. However, we recommend creating a dedicated user and limit data access for this user only to data you want to sync. You can limit data access for a user by creating a profile in Salesforce and assigning it to the user.

To create a new user and profile in Salesforce, do the following:

  1. Log on to Salesforce. You must have administrative privileges to create a user.
  2. Go to Setup in the top right corner of your screen.
  3. Under the Administration tab on the left side of the screen, click on the Profiles tab.
  4. Click New Profile.
  5. Select Read Only from the Existing Profile drop-down menu.
  6. Enter a memorable name in the Profile Name field. For example, SupportLogic User Read Only.
  7. Click Save. The Profile page will open.
  8. Click Edit in the Profile Detail section.
  9. Scroll down to the Standard Object Permissions section and set the Read permission for the objects that you want sync.
  10. Scroll down to the Custom Object Permissions section and grant the Read permission for the objects that you want sync.
  11. Click Save.
  12. Under the Administration tab on the left side of the screen, click the Users tab.
  13. Click New User.
  14. Fill in all the required details.
  15. In Profile, select the user profile you created (SupportLogic User Read Only).
  16. You can follow the steps mentioned in Option 2. Limit the connecting user in Salesforce documentation section to grant permission on field levels using permission sets.

(Optional) Limit permissions to tables or columns

Data is synced based on the viewing permissions of the connected user. If you don’t want to sync a certain type of data to into your destination, limit the permissions of the connecting user. There are two ways to limit the data that we extract from your Salesforce account. You can either disable tables in the connector dashboard or limit the connecting user in Salesforce.

Option 1: Disable tables in the connector dashboard

  1. In the connector dashboard, navigate to the Salesforce connector details page.
  2. Go to the schema tab and disable the tables and columns which you do not want to be synced.

If you are concerned about unintentionally syncing sensitive data to your destination, click the gear icon to open the Schema Change Settings menu, then select Allow columns.

Option 2: Limit the connecting user in Salesforce

SupportLogic connects to your Salesforce instance through the credentials of the connecting user, so to limit our access to the data, limit that user’s access.

You can do this in Salesforce through Permission Sets.

It’s best to limit the connecting user’s access before you initially connect the user through our setup form. Otherwise, you may have some dead objects in Salesforce that will no longer be updated after you’ve restricted the user’s permissions.

  1. Log on to Salesforce. You must have administrative privileges to set permissions.
  2. Go to Setup in the top right corner of your screen.
  3. Under the Administer tab on the left side of the screen, click on the arrow next to Manage Users.
  4. You should now see a drop-down menu below the arrow. Select Permission Sets in the drop-down menu.
  5. We recommend that you create a new set of permissions specifically for the user that you will use to connect to SupportLogic. Name it something memorable, such as “SupportLogic Permissions”.
  6. Users can have multiple sets of permissions assigned to them. If you’d like to be certain of what data we have access to, assign only one set of permissions to the connecting user.
  7. Press New > Enter in Label > Choose Appropriate User License Type
  8. You’ll see the settings for the new Permission Set (for example, “SupportLogic Permissions”). Select Object Settings.
  9. Select which fields you would like this connecting user, and therefore SupportLogic, to have access to. The default setting is No Access.
  10. The only permissions relevant to SupportLogic are that we can read the data, though the user themselves may need to be able to do more. The difference between the Read permission and the View All permission is that Read gives access to view records that are created by that user or are shared via rules, roles, or manual sharing. View All gives access to all records of that type (for example, the Account type). Note: To enable the user to access all the files in the org, provide the user with the Query All Files permission. The connector can not sync the ContentNote, ContentDocument, and ContentVersion objects without the Query All Files permission.
  11. When you’ve chosen the appropriate permissions, go to Administer > Manage Users > Users and select the user whose account you will use to log in through the connector.
  12. When you’re on that user’s page, scroll down to Permission Set Assignments and click Edit Assignments.
  13. Move connector Permissions from Available Permission Sets to Enabled Permission Sets and click Save.

Finish Configuration

  1. There are two separate services for Salesforce. Choose the connector for the environment you’d like to use: Production environment or Sandbox environment.
  2. In the connector setup form, enter the Destination schema name of your choice.
  3. Click Authorize to authorize the API. You will be taken to the Salesforce login page.
  4. Log on to your Salesforce account to authorize the connector to connect to it.
  5. Return to the dashboard and click Save & Test to complete the data sync.
Salesforce Schema
Object Usage
accountTracks back-and-forth conversations between your agents and the customer. Used to analyze sentiment.
userTracks Salesforce users (typically an individual account or user who has opened a case—this can be a customer or engineer).
contactTracks any user that does not have a full account in Salesforce but has been attached to a case or case comment.
caseTracks case information.
case_commentTracks all conversations and messages in a case. Used to analyze sentiment. Between email_message, case_comment, and case_feed, we must map at least one object that contains support conversations.
case_historyTracks the history of actions in a case.
record_typeTracks group information.
email_messageTracks conversations and messages within cases. Used to analyze sentiment. Between email_message, case_comment, and case_feed, we must map at least one object that contains support conversations.
EscalationThis is an abstract object we build to analyze escalations. We can also start from your custom escalation objects or custom fields within the Case or Task objects.

ServiceNow Integration Guide & Schema

To connect your ServiceNow instance to SupportLogic SX, you need to enable table auditing and a ServiceNow Service Account with access to the following tables:

  • sys_db_object
  • sys_dictionary
  • sys_audit_delete
  • Any tables you want to sync

Note: You don’t have to include the tables listed above to the connector schema. Including these tables only slows up the sync due to the large size of these tables.

Note: You can simply grant admin and snc_read_only roles to your service account if you want to avoid setting up complex ServiceNow access control lists.

Setup Instructions

  1. Find your ServiceNow Instance ID
  2. Log on to your ServiceNow account.
  3. Look in the URL to find your Instance ID
  4. Make a note of your Instance ID. You will need it to fill in your connector setup form.

Set Up OAuth

  1. In your ServiceNow account, select OAuth > Application Registry in the left menu.
  2. Click New.
  3. Select Create an OAuth API endpoint for external clients.
  4. Enter an application name (we suggest SupportLogic) in the Name field.
  5. Make a note of the Client ID. You will need it to fill in your connector setup form.
  6. Specify Client Secret and make a note of it. You will need it to fill in your connector setup form in the connector dashboard. Alternatively, you can leave the Client Secret field blank to automatically generate the value when you save the OAuth application data. You can see the generated client secret by clicking the Unlock button.
  7. Leave Accessible from as the default value of All application scopes.
  8. Make sure that the Active checkbox is selected.
  9. Leave the default values for Refresh Token Lifespan and Access Token Lifespan.
  10. Click Submit to register the application.

Finish Configuration

Work with a SupportLogic Solutions Architect to finish configuration:

  1. In the connector setup form, enter the Instance ID you found in Step 1.
  2. Enter the Client ID and Client Secret that you found in Step 2.
  3. Enter your Service Account username and password.
  4. Click Save & Test to complete the data sync.
ServiceNow Schema
ObjectUsage
core_companyTracks customer information.
sys_userTracks ServiceNow users (typically an individual account or user who has opened a case—this can be a customer or engineer).
taskTracks case information.
sys_journal_fieldTracks conversations and messages within cases. Used to analyze sentiment.
sys_history_lineTracks case history information.
sys_history_setTracks case history information.

Zendesk Integration Guide & Schema

To connect your Zendesk instance to SupportLogic SX, you need:

  • Your Zendesk Support domain name. Your Zendesk Support domain is the beginning of your help desk URL. It’s usually your company name, for example “domainname” in “domainname.zendesk.com”.
  • A Zendesk account with an Administrator role. If you don’t know if your account is an Administrator, proceed to the In Zendesk section.

In Zendesk

  1. To check if your account is an Administrator, log on to Zendesk and go to your profile.
  2. Verify that your user type is Administrator.
  3. If you don’t have an administrator login for Zendesk, involve someone else in your company who does.

Setup Instructions

Work with a SupportLogic Solutions Architect to finish configuration:

  1. In the connector setup form, enter the Destination schema name of your choice.
  2. Enter your Zendesk Support Domain name.
  3. Click Authorize. You will be redirected to Zendesk’s login page.
  4. Log on to your Zendesk account and follow the instructions to authorize connector access.
  5. You will be redirected back to the connector dashboard.
  6. Click Save & Test to complete the data sync.
Zendesk Schema
ObjectUsage
organizationTracks customer information.
userTracks users of Zendesk (both customers and agents).
ticketsTracks ticket information. Escalation is an abstract object we build, implemented as a custom field in the Tickets object. We track that a ticket was escalated and when it was escalated (and possibly when it was de-escalated if that occurrs before it is closed).
ticket_commentTracks ticket conversations. Used to analyze sentiment.
groupTracks group information.

Don’t miss out

Want the latest B2B Support, AI and ML blogs delivered straight to your inbox?

Subscription Form