Using the deflection topic block to track deflections in Virtual Agent

  • Release version: Zurich
  • Updated July 31, 2025
  • 2 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 Using the deflection topic block to track deflections in Virtual Agent

    The pre-built deflection topic block in ServiceNow Virtual Agent enables you to track when Virtual Agent helps users resolve issues independently, preventing the need for live agent intervention or incident creation. This tracking supports analyzing and optimizing Virtual Agent's effectiveness by capturing deflection patterns and metrics.

    Show full answer Show less

    A deflection occurs when Virtual Agent redirects users to self-service resources such as knowledge base articles or completes workflows without escalating to a live agent. If needed, Virtual Agent can still create incidents in the correct assignment group by asking relevant questions, improving workflow efficiency.

    Deflection Configurations and Patterns

    Deflection tracking is enabled by default but requires setting up deflection configurations and patterns to capture specific metrics. A deflection configuration groups one or more deflection patterns, which categorize Virtual Agent activities during conversations.

    Deflection patterns represent distinct Virtual Agent actions such as:

    • Showing search results (potential deflection)
    • Creating incidents with accurate assignment (confirmed deflection)
    • Completing workflows without incident creation (confirmed deflection)
    • Automatically resolving incidents (confirmed deflection)

    Each deflection pattern corresponds to an outcome in the conversation:

    • Confirmed deflection: Virtual Agent resolved the issue, avoiding incident creation or live agent transfer.
    • Potential deflection: Resolution is unclear, such as when search results are shown.
    • No deflection: Virtual Agent did not resolve the issue, leading to incident creation or live agent transfer.

    ServiceNow provides pre-built deflection patterns in the default deflection configuration, which you can use or customize.

    Deflection Metrics and Analytics

    Deflection configurations and patterns are linked to the deflection topic block used in Virtual Agent conversation topics (for example, the Issue Auto Resolution topic). Metrics are stored in the Deflection Metric [ssadeflectionmetric] table.

    You can view deflection metrics through the Deflection Metrics module within the Self-Service Analytics framework, which requires activation of the Self-Service Analytics Core plugin. Visualizations are also available in the Overview tab of the Conversational Analytics Dashboard, offering insights into Virtual Agent’s performance in deflecting incidents.

    Practical Application for ServiceNow Customers

    • Enable and configure deflection settings to categorize and track how Virtual Agent resolves user issues.
    • Use deflection patterns to monitor types of resolutions and identify areas for optimization.
    • Leverage deflection metrics and dashboards to analyze effectiveness, reduce incident volume, and improve user self-service success.
    • Customize or create new deflection patterns to align with your organization's workflows and Virtual Agent use cases.

    Use the pre-built deflection topic block in ServiceNow® Virtual Agent to track the issues that Virtual Agent helped to resolve or actually resolved for a user. Incident deflection patterns and metrics can help you optimize and analyze the effectiveness of Virtual Agent.

    A deflection occurs when Virtual Agent automatically redirect users to self-service options or knowledge base articles that can help them solve their problems without requiring the assistance of a live agent. As a result, the user might not need to create an incident. If necessary, however, Virtual Agent can ask relevant questions and then create an incident in the correct assignment group. This workflow becomes more efficient because no live agent has to get involved.

    The Virtual Agent deflection tracking is enabled by default, but you must set up the deflection configuration and deflection patterns to capture certain deflection metrics. For more information, see Create deflection configurations and patterns.

    You use deflection configurations to group deflection patterns. A deflection configuration can consist of one or more deflection patterns. Deflection patterns categorize Virtual Agent activities in conversations for tracking deflection metrics. For example, let's say that Virtual Agent adds a user to an email list without creating a task in the Task table to complete the workflow. You can categorize this activity as a self-resolving deflection pattern.

    You can view the deflection metrics for each deflection pattern. A deflection pattern can lead to these deflection outcomes in a conversation:
    • Confirmed deflection: Virtual Agent provided a resolution to the user, which prevented the user from creating an incident or transferring to a live agent.
    • Potential deflection: It is unclear whether Virtual Agent provided a resolution to the user. An example is when search results are displayed to a user in a conversation.
    • No deflection: Virtual Agent did not provide a resolution, and the user created an incident or transferred to a live agent.
    You can either create new deflection patterns, or use these pre-built deflection patterns in the VA Default deflection configuration:
    Deflection pattern Activity Outcome
    VA-Search-served Virtual Agent showed search results to the user. Potential deflection
    VA-Triage & Created Virtual Agent creates an incident in the correct assignment group. This action improves the assignment accuracy. For example, Virtual Agent identifies a reimbursement-related intent in a user conversation and creates a reimbursement incident instead of a general incident. Confirmed deflection
    VA-Self-Resolving Virtual Agent completes the workflow on its own without creating an incident. For example, Virtual Agent adds a user to a distribution list. Confirmed deflection
    VA-Intercept & Resolved Virtual Agent intercepts an incident that was created by a user and provides a resolution to close the incident. An example is when Incident Auto Resolution resolves an incident. Confirmed deflection

    The deflection configuration and deflection pattern that you create in the deflection settings are mapped to the deflection topic block. For example, the pre-built Issue Auto Resolution topic uses a deflection topic block to track deflections. For more information, see Maximizing code reuse with topic blocks and Virtual Agent pre-built topic blocks for NLU.

    The deflection metrics are generated and stored in the Deflection Metric [ssa_deflection_metric] table. To view the deflection metrics, navigate to the Deflection Metrics module in the Self-Service Analytics framework.
    Note:
    The Self-Service Analytics framework requires the Self-Service Analytics Core plugin (com.snc.self_service_analytics_core). For more information, see Activate Self-Service Analytics.
    Figure 1. Deflection metrics
    Deflection metrics for Virtual Agent deflections.

    You can also view the visualization for deflection metrics in the Overview tab of the Conversational Analytics Dashboard. For more information, see .