Skip to main content


Gainsight Inc.

Exceptions in Scorecards

Gainsight NXT

This article supports Gainsight NXT, the next evolution of the Customer Success platform. If you are using Gainsight CS Salesforce Edition, you can find supporting documentation by visiting the home page, and selecting CS > Salesforce Edition.

Not sure what your team is using? Click here.


This article explains what exceptions are and how an admin can configure exception criteria in a Scorecard, to ignore the measure weights and set scores based on the exception criteria.


The overall Score for a Scorecard is calculated based on the Weightage assigned to each Measure. However, an Exception allows you to set the Overall Score for the Scorecard based on some specific criteria and not based on the Measure Weights assigned. In other words, Exceptions can be used when you want to ignore the existing Measure Weights and use a different approach to set the Overall Score for a Scorecard.

  • To learn more about Scorecard weights, refer the Configure Section part of the Create Scorecards article.
  • In this article, a Scorecard is created primarily to know the number of Support cases and resolution time.
  • The Scorecard has two Measures; Support Volume which is based on the number of support tickets and Support Resolution time which is based on the time taken to resolve tickets.
  • The Support Volume Measure has a good score (green) if the number of Support tickets are low.
  • The Support Resolution time Measure has a good score (green), if the average time taken to resolve the tickets is low.
  • It is assumed that the Overall score must always be maintained at 60. The Overall Score must not go below this threshold level.

The Measure Weightage assigned to each Measure is as shown below:

1- Measure Weights.png

Both the Measures are given equal weightage and thus contribute equally to the Overall Score.

However, some customers might accidentally log duplicate tickets, or log tickets for a problem which already has a solution in the documentation, or log a ticket for some other inappropriate reason. In such cases, the number of tickets goes up which effects the Support volume Measure negatively and also impacts the Overall Score.

However, if the tickets are being resolved within a stipulated time, the Support Resolution Time Measure has a good score. Tickets being resolved quickly implies that even though there are lots of tickets, the support team is working efficiently to resolve them.

In such a scenario, you may want to create an exception such that if the Support Resolution Time Measure has a good score (green), but the Support Volume has a bad score (in red zone), then the Overall Score should be set to minimum threshold level of 60 by ignoring the Measure Weights.

Create an Exception   

To create an Exception:

  1. Navigate to the Scorecard Configuration section and click EXCEPTIONS.

2- exceptions.png


  1. Perform the following tasks in the Configure Exceptions window:
    1. Enter a name for the Exception in the Name field.
    2. Select a Measure from the Measures field (here, Support Resolution Time).
    3. Select an operator from the Operator field.
    4. Set the Score for the selected Measure.
    5. Click + to add additional criteria.
    6. Select the AND operator.
    7. Select a Measure from the Measures field (here, Support Volume).
    8. Select an operator from the Operator field.
    9. Set a score for the selected measure.
    10. Set the Overall Score.

3. setting.gif

  1. (Optional) Click + EXCEPTION, to add additional exceptions.
  2. Click SUBMIT.

Explain Score Tooltip

When the Overall Score for a Company or Relationship is influenced by an Exception, a tooltip is displayed near the Overall Score on the 360 page. End users can click on this tooltip to know more details like which Exception has matched the criteria, what is the impact of the exception on the Overall Score (remains same or changed).


  • Was this article helpful?