Performance overview

  • Release version: Xanadu
  • Updated September 2, 2024
  • 4 minutes to read
  • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Performance Overview

    The Performance Overview provides a detailed analysis of KPIs and metrics essential for assessing the benefits of your IT Service Management (ITSM) implementation. It focuses on various self-solved scenarios and automated resolutions that enhance user experience and operational efficiency.

    Show full answer Show less

    Key Features

    • Self-solved Percentage: Measures how often users resolve issues independently, including contributions from Virtual Agent, Knowledge articles, and automated resolutions.
    • Self-solved Metrics:
      • Using Virtual Agent: Tracks automated conversations that lead to issue resolution without human agent interaction.
      • Using Knowledge: Counts successful problem resolutions from knowledge articles accessed by users.
      • Using QnA: Monitors resolutions achieved through AI Search interactions.
      • Using Proactive Engagement: Assesses issues resolved through proactive detection and user engagement.
    • Automated Resolutions: Measures the frequency of tickets resolved automatically through workflows, including Incident Auto Resolution and Request Fulfillment.
    • Password Reset Apps: Tracks successful account unlocks and password updates performed by users.
    • Call Deflection: Evaluates the effectiveness of self-service options compared to direct agent interactions.

    Key Outcomes

    By utilizing these KPIs, ServiceNow customers can effectively analyze their ITSM performance, identify areas for improvement, and enhance user satisfaction through increased self-service capabilities and automation. This ultimately leads to improved productivity and operational efficiency across the organization.

    Performance overview details all the KPIs and metrics that help you analyse the benefits of your ITSM implementation.

    • Self-solved percentage: Calculated from the daily average number of times your users achieved a resolution without intervention from Tier 1 Agents in the report range. Includes numbers from Self-solved using Virtual Agent, Self-solved using Knowledge and Automated resolutions (For example, Incident auto-resolution via Virtual Agent). See the formula:
      [Self-solved (VA, KB, QnA, Proactive Engagement) + Automated resolutions] / [Total Tickets Resolution + Self-solved (VA, KB, QnA, Proactive Engagement) + Self service using Password Reset apps]*100 
      • Self-solved using Virtual Agent: Number of automated conversations that helped the user solve their problem. This is determined when users complete a virtual agent conversation and does not engage (Interactions) with a human agent in the next 24-hour window.

        Considers both Virtual Agent powered by NLU and LLM (Now Assist VA)

        Note:
        To use a different method to determine this KPI, see Configure Success Dashboard indicators KPIs.

        To update the live agent script include see, Update the live agent script include.

      • ITSM issues solved using NOW Assist VA (LLM): Number of times the users were able to resolve their issues by interacting with Now Assist Virtual Agent (NAVA) conversation. This is determined when a user completes a Now Assist Virtual Agent conversation and doesn't create an incident or engages (Interactions) with a human agent in a 24-hour window.

        To update the live agent script include see, Update the live agent script include.

      • Self-solved using Knowledge: Number of times users were able to solve their problems by reading knowledge articles. This is determined when users read knowledge article(s) and do not create ticket or engages with a human agent in a 24-hour window.
        Note:
        To use a different method to determine this KPI, see Configure Success Dashboard indicators KPIs.

        To update the live agent script include see, Update the live agent script include.

      • Self-solved using QnA: Self-solved using the AI Search when a user interacts with a Virtual Agent or on Portal and gets a summarized answer from AI Search. This is determined when users are presented with a AI Search QnA result and do not go on to create ticket or engage with a human agent in a 24-hour window.

        To update the live agent script include see, Update the live agent script include.

      • Self-solved using Proactive Engagement for DEX The number of digital experience issues Self-solved using Proactive Engagement for DEX. This is determined when DEX proactively detects issues and Proactive Engagement helps users self-solve them.

        To know more about the Proactive Engagement see, Proactive Engagement.

      • Automated Resolutions: Number of times the ticket was resolved automatically. In the base system, the indicators contributing to this metric are Incident Auto Resolution and Request Fulfilled Automatically.
        • The Incident Auto Resolution value is determined by the deflection node configured in the Issue Auto Resolution Virtual Agent topic.
        • The Request Fulfilled Automatically value is the number of requested items that are fulfilled using automated workflows. When the catalog item uses an automated workflow, the Fulfillment automation level field of the catalog item must be set to Fully-automated for it to be included in this metric.
        • Accounts unlocked using Password Reset apps: Number of times users were able to unlock their accounts successfully using Password Reset apps.
        • Passwords updated using Password Reset apps: Number of times users were able to update their account passwords using the Password Reset apps.
        Note:
        To use a different method to determine this KPI or add more sources (for example, automated catalog workflows), see Configure Success Dashboard indicators KPIs.
      • Total ticket resolutions: Number of incidents resolved + Number of requested items closed + Number of Agent interactions not resulting in tickets (closed).
    • Call deflection: Calculated from the number of times per day requesters performed the actions, Ticket submissions using Service Catalog, Ticket submissions using Virtual Agent, Self-solved using Virtual Agent and Self-solved using Knowledge without Tier 1 agent intervention. See the formula:
      [Catalog ticket submissions + VA ticket submissions + Self-solved (VA) + Self-solved (KB)]/ [Total tickets submitted + Self-solved (VA) + Self-solved (KB)] x 100 
      • Catalog ticket submissions: Incidents and requested items submitted using Service Catalog in Service Portal or Now Mobile app.
      • VA ticket submissions: Number of times the ticket was submitted using Virtual Agent. In the base system, this is determined by the ITSM - Triage & Created deflection pattern instrumented in the Virtual Agent topic. The topics shipped with ITSM VA Conversations already have these nodes instrumented but must be instrumented in all other topics that create incidents.
        Note:
        If you use a different method to determine this KPI or add more sources (for example, automated catalog workflows), you can use the steps described in Configure Success Dashboard indicators KPIs.
      • NOW Assist ticket submissions: Number of times the ticket was submitted using NOW Assist. In the base system, this is determined by the ITSM - Triage & Created deflection pattern instrumented in the NOW Assist topic. The topics shipped with NOW Assist Conversations already have these nodes instrumented but must be instrumented in all other topics that create incidents.
      • Total tickets submitted: Incidents created + RITMs created.
    • Structured tickets: Total number of requested items completed successfully in the report range.
    • Productivity moments per user: Productivity Moment is calculated when the ServiceNow products helped a user to be more productive while working in their day to day operations.
      • Productivity in search per user: The number of times the NLU prediction model accurately understood the intent of the user's conversation or auto-selected a topic.
      • Productivity in routing per user: Successful predictions of incident fields such as assignment group, or category by Predictive Intelligence solutions, counted when the prediction made by the solution is the same as final value when the incident was closed.
      • Productivity in fulfilment per user: Includes any productivity gains achieved where ServiceNow is helping the employees to save time to resolve a ticket
      Note:
      If you use a different method to determine this KPI, you can do so using the steps described in Configure Success Dashboard indicators KPIs.