đŸ€– Support Data + AI = Your Customer Success Crystal Ball 🔼


Userlevel 5
Badge +3

Unless you’ve been living under a rock for the past year, you’ve heard countless CEOs share their insights on how emerging AI functionalities are going to transform our lives. You may have even seen Gainsight’s own Nick Mehta transformed into an AI Bot at Pulse 2023! 

VnX2BSxzW9LOBpyFCPrRlY1GKN3YUmUVFE02P6aEUvEvpVadrXQvxoiu9fC4MHJdo-jT2C47RvnncSSltxeJ6Cc66tiHn5PbaX57Bm4eYU8q8LrpStAmNc8gPEWRQweMAsVfju03BMRPv1j8zGquElA

Needless to say, Gainsight is doing some amazing things with AI. Predictive analytics, health scoring, automated workflows, customer segmentation, personalized recommendations and using natural language processing technology for deeper insights are just a few of the innovative ways Customer Success teams can leverage Giansight’s AI solutions. 

A common thread woven within each of Gainsight’s AI-powered solutions is the analysis of data, including support tickets, to summarize, predict, and make CSMs’ day-to-day lives a bit easier. Specifically, let’s dig into how Gainsight’s AI can help teams transform support ticket data into a crystal ball to predict future trends. 🔼

Scorecard Optimizer

Consider support ticket data when building out customer scorecards using the simple recipe below:

0I7PRebTT5NCqySNScXWXHqquWDciIDQGoHYP8dLTQ835Qg1lOHvCZZ0FLZzKkl0-ffDDBJOo6U_yUVTjaMjLtHewBNG2Gt4j7AGL9KG6L6MuHvdUTLUI_X9mf76k5cfSFRl13J9WMQzl92_yqxwHqo

While this formula is a sound method for analyzing the way in which support trends impact customer health, how can you know if this is an effective prediction for your own organization? Use Gainsight’s AI-powered Scorecard Optimizer to offer optimal configuration recommendations and improve the effectiveness of existing scorecards. 

To ensure Scorecard Optimizer is looking at support cases when making recommendations:

  1. Navigate to Administration > Scorecard and click the Optimizer Data option 
  2. Select Customer Data and navigate to the Support section. This section displays the total records in the Case object and the time frame of these records. Note: if no data is available, click Add Data, which will take you to the Support Connectors page to easily load support data in CS using an OOTB connector (Zendesk, ServiceNow, Jira, Freshdesk). Alternatively, use the Rules Engine Load to Cases action type to load support data.

Next, run the Scorecard Optimizer to gather insights to the effectiveness of the support case measures in your scorecard and enjoy some AI-recommended improvements based upon YOUR data to narrow the scorecard focus and improve the overall usability of this predictive measure.        

RoYMyC72ocbhNOueY1oUZEMcOQrQAoW7WFPyna0q68YCw4u8UWJrsPAYt7qGHCEuq2VSB5cBNiaMfvpygkRtkk3ugOuPlt4EfFYF4CixzrTiwQxjl8hS1xrIRaHmumrWqbQ8N0tCvMI-R1Aznzzy5fc

The following AI-powered use cases for support data in CS (Text Analytics and Customer Cheatsheet) require that the support case data exists in Gainsight’s Timeline. See the options below for populating Timeline with support case data. 

  • Option #1: Use Rules Engine and Load to Activities action type to update the Timeline with support case data. This action type would allow you to create a custom milestone, such as “support ticket closed,” and log the activity in Timeline when the milestone occurred. It is not recommended to include every support ticket in Timeline, however, as that could lead to a noisy and difficult to digest Timeline feed as well as a cluttered customer journey widget.   
  • Option #2: To avoid a cluttered customer journey, you can alternatively create an External Action with an API call  and then use Rules Engine and the Call to External API action type. While this method requires more manual configuration than Option #1, it would allow you to apply more discriminatory criteria about what information to post to Timeline. (For example, use filtering criteria such as “high priority,” “at-risk,” “# of days ticket is open,” etc.) Additionally, there is no need to log support activities as customer milestones with this option.  

Text Analytics  

Monitor sentiment in support cases using Gainsight’s Text Analytics. This feature scans survey feedback as well as timeline feeds from various categories to provide advanced analytics, including sentiment assessment, enhance customer experience, predict trends, identify potential churn, and recommend necessary steps to increase product usability. 

Note: In order for support case text to be considered in Text Analytics, the text must exist in Timeline or Surveys. 

  1. Load support ticket data to Timeline using one of the recommended options above  
  2. And/or use the Rules Engine and Load to Survey action type to load NPS or CSAT survey results from your support system to the corresponding Gainsight Survey object. 
  3. Configure Text Analytics by selecting Timeline and/or Surveys for Source Type data  
  4. Add out of the box Topics and Keywords to get better text analytics results based on support requirements (i.e., ticket, issue, bug, request, blocker, resolve)

tqZcJj8YFv0T5FxxheHHVGxXX-XDwRVUPAybr6BFUQdnixt7SBR9F5An_grp876XMzvIbaUlSubRc0l14jjGuPUV9JUSEZVAdUd1WucBXrwO-WTBHkAGMT3sYMG8JjQLMuOepsLP05HjdRljH1DUoAM

View sentiment trends over time and use Text Analytics Widgets for even deeper insights:

  • Companies: View aggregated sentiment score, NPS, CSAT, and revenue by company 
  • Impact Analyzer: uncover how different drivers like scorecard measures or customer sentiment impact business goals like NPS and renewals 
  • Takeaways: Analyze and extract meaningful textual key points and manually added topics from various customer interactions from the Timeline support case data
  • People: View the list of Company Persons along with their Role, Email, Company Name, historical Sentiment score, and their latest survey response 

Customer Cheatsheet 

The Customer Cheatsheet widget on the C360 uses AI to create a narrative summary based on key customer metrics, strategic priorities, risks, product requests, renewals, executive changes and much more using the last six months of their Timeline entries. Meaningful insights on sentiment, product feedback, customer goals, growth opportunities, and potential risks are often embedded in conversations between key customer contacts and support agents. These insights need not remain siloed in support tickets any longer. Allow AI to sift through the noise, pull out meaningful nuggets, and summarize the data with a succinct narrative to save time and direct attention to what’s most important. 

Note: In order for support case data to be included in Customer Cheatsheet, the support data must exist in Timeline. 

  1. Load support ticket data to Timeline using one of the recommended options above  
  2. Next, configure C360 by dragging the Customer Cheatsheet widget into the Summary canvas and Voila! No other configuration necessary. AI will scan through Timeline entries and provide a robust narrative summary of your customer. 

 tD74WdWAJi60wvHke1TuwREJJ3iUqAguyDZwo8EyN_wT137GIvzmrYrH0zSAYBmMkUUcGCFVw_1pj-rK0bl0q_Asy7iyE0Sx06LBeG82G33DjddBNwfahXqDkOk-IIwqQFqPphU7_sFNjaLiTcJv75E

As you can see, Gainsight's AI-powered solutions aren't just transforming Customer Success—they're practically giving it a crystal ball. From refining scorecards to reading between the lines of support tickets, these tools turn data into gold. With AI, it's not just about predicting the future; it's about making it brighter, one support ticket at a time. 😎


4 replies

Userlevel 7
Badge +4

So, when did Timeline start turning into a catch-all data repository vs. it’s original purpose:

Key word: KEY

Timeline is getting so cluttered its no longer a great place for “teammates and management to get up to speed quickly” and “reduce need for leadership to ask for one-off updates” and requires custom views and a mastery of filtering in order to make sense of it.

Why does one have to copy case data from source (i.e. Salesforce) to both Cases AND Timeline for these AI features to work? Can’t the AI features be directed to consult the same source?

Userlevel 5
Badge +3

Great point @darkknight  and something to be mindful of when making the decision whether or not pull support data into Timeline for the purposes of Cheatsheet. It will be exciting to see how Gainsight’s AI functionality continues to grow and improve as time goes on! 

Userlevel 4
Badge +4

Great points! This gave me lots of ideas when thinking about CC+CS too. Very timely!

Userlevel 3
Badge +3

So, when did Timeline start turning into a catch-all data repository vs. it’s original purpose:

Key word: KEY

Why does one have to copy case data from source (i.e. Salesforce) to both Cases AND Timeline for these AI features to work? Can’t the AI features be directed to consult the same source?

 

Agree with @darkknight here, I feel the AI model should be able to reference the Case data, especially being in a native MDA object. An account with 100s or 1000s of contacts could become a very busy timeline very quickly with case data, especially in times where there’s an issue or outage.  Additionally, playing devil’s advocate, say the above scenario happened and there were a large number of case timeline entries, I’d be interested to see if cheatsheet then became abnormally weighted with case insights, reducing the importance of other entries added from other sources (automated or manually).

 

Additionally, we have case data we’re able to associate with individual products/relationships, and (as far as I know in May ‘24) scorecard optimizer isn’t yet enabled at the relationship level.

 

Something to revisit in time for us, appreciate the walkthrough on this @AngelaBrown!

 

Stuart

Reply