Questions and responses in an exploration

  • Release version: Zurich
  • Updated July 31, 2025
  • 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 Questions and responses in an exploration

    AI Data Explorer in ServiceNow Zurich enables users to ask specific questions about their data and receive responses that include data visualizations, summaries, and suggested follow-up questions. Users launch AI Data Explorer from a data visualization, list, or an existing exploration to interactively query data held in indicators or configured tables.

    Show full answer Show less

    How It Works

    • Users enter natural language questions about data within the semantic data layer, which includes indicators, database views, and Workflow Data Fabric tables.
    • The system prioritizes indicators as data sources, then falls back to tables if no relevant indicator is found.
    • Access to protected application scopes must be configured to query data from those scopes.
    • Once a question is submitted, it is converted into a database query and processed; users cannot submit another question until processing completes, though they can cancel.

    Response Components

    • Expandable actions on responses such as duplicate, delete, copy, or move.
    • The original question is editable to refine or generate new output.
    • A title and summary of AI findings, with optional extended analysis for deeper insights.
    • A list or data visualization representing the response, which can be added to dashboards and resized.
    • Technical source details are viewable to understand query filters, grouping, metrics, and data sources.

    Tips for Effective Questioning

    • Name specific tables: Reference exact or partial table names to improve query accuracy.
    • Clarify terms: Use precise language to guide query generation and avoid vague requests.
    • Use full display names: When filtering by referenced records (users, groups, services), full names ensure better matching.
    • Edit and refine queries: Modify filter conditions manually to improve results; the AI learns from these edits within the same exploration.
    • Manage queries: Delete unhelpful queries to avoid degrading response quality over time.
    • Import complex filters: For intricate data needs, import existing visualizations or lists with filters applied to provide context.

    Additional Features

    • Indicator vs. Table Source Selection: The system determines data source preference automatically, defaulting based on system properties when unspecified.
    • Extended Analysis: Enables deeper insights beyond basic responses.
    • Dashboard Integration: Add visualizations directly from explorations to dashboards without interrupting workflow.
    • Response Refresh: Regenerate responses with updated data to keep insights current.
    • Response Management: Edit, duplicate, delete, copy, or reorder questions and answers within or across explorations.

    Practical Benefits for ServiceNow Customers

    This capability empowers customers to interactively explore their data using natural language, gaining actionable insights through visualizations and summaries without needing deep technical query knowledge. It supports data-driven decision-making by allowing iterative refinement of questions, integration with dashboards, and access to protected data when configured. Following best practices in questioning ensures accurate and relevant results, helping customers maximize the value of their ServiceNow data.

    Ask the AI specific questions in AI Data Explorer, to which it responds with data visualizations, a summary, and suggested follow-up questions.

    To ask a question in an exploration, launch AI Data Explorer from a data visualization or list or open an existing exploration. You will see a field with the placeholder "Ask a question about data." For more information, see Launch AI Data Explorer.

    Note:
    • The question you ask has to be about data in either indicators or one of the tables listed in the Query Generation Semantic Table Configuration table. These tables can include database views or Workflow Data Fabric tables. For more information, see Add a table to the semantic data layer.
    • The system first looks for a relevant indicator to be the data source. If it does not find one, it falls back on table data sources.
    • If the data is from a protected application scope, access to that scope must be configured for AI Data Explorer. For more information, see Enabling access to protected scope applications for AI Data Explorer and Query Generation.
    • When you have submitted a question, you cannot submit another question or do other work in the exploration until your question is processed. You can cancel the processing of your question.

    When you write a question in an exploration, the AI converts the question to a database query and returns a response. The response includes the following sections:


    The response returned from a question to AI Data Explorer, showing the summary, data visualization, and suggested follow-up questions.
    • Area 1 An expandable set of actions to take on the response. For more information, see Duplicate, delete, copy, or move an answer in an exploration.
    • Area 2 Your original question. You can edit this question to generate new output.
    • Area 3 The title of the response and a summarization of the AI findings.
    • Area 4 If extended analysis is enabled, you get additional insights after the title and summary. For more information, see Extended analysis.
    • Area 5 A list or data visualization. This response can be an existing visualization instead of a generated one. For more information, see Launch AI Data Explorer.
      You can add the list or visualization to a dashboard or change its height by interacting with controls in its corner. Point at the corner to make the controls appear. For more information, see Add a data visualization from an exploration to a dashboard.
      Controls in the corner of a data visualization, with height adjustment control selected.

    Viewing the response source

    After you receive a response from the ServiceNow AI Platform, point at the response to see the technical details of the response. The source details for a table source include the following information:
    • The source table
    • The filter conditions
    • The metric
    • Any grouping criteria

    For an indicator source, the details include the time series aggregation and the collection date.

    If the exploration is too narrow on the screen, select View source instead of pointing at the response.
    Source details for a response in an exploration that features table data.

    Tips for asking questions

    The goal of AI Data Explorer is to understand your prompts in your own words, delivering the analytics insights you want. However, if you do not know where to begin to formulate questions, or you're unsatisfied with the results, here are some tips:

    Name your table
    If you know the name of the table that contains the data you are interested in, add it to your prompt. Partial names or similar names are fine too.

    Example: Instead of "How many P1s were opened this week,” write "How many P1 requests were opened this week," which references the request tables. Better yet, write "How many P1 catalog requests were opened this week," which references the specific Catalog Requests table.

    Explain what you mean
    Query Generation tries to understand your terms, but you can add details to help guide it. If you get unexpected results, try being more specific about what you're looking for.

    Example: Instead of "Show me all stale incidents," write "Show me all incidents not updated in 5+ days."

    Be specific with names
    When filtering by referenced records like users, groups, or services, try to use their full display names for best results. The AI model may learn from previous queries in the same document, but using full names ensures accuracy.

    Example: Instead of "Cases with Workplace Ops," write "Cases with Workplace Operations."

    Edit and refine queries
    If the generated query isn't quite right, you can manually edit the filter conditions. The AI model will learn from your edits and apply them to future questions in the same document. For more information, see Regenerate a response in an AI Data Explorer exploration

    Example: You ask "Show me critical incidents from the network team" but are not satisfied with the response. Instead of asking repeated variations of the same question, hoping for a better result, edit the filter to find records where Assignment Group is ‘Network Operations’ and Priority is ‘1 - Critical’. Then ask "Show me the inflow trend for these incidents over time”.

    Don't leave bad queries in your exploration
    The AI model uses the previous document context to write the next query. Therefore, if you cannot refine a query to get a useful response, delete it. Otherwise bad queries can accumulate in your exploration, leading to ever-worsening responses.
    Import complex filters
    For complex data that's hard to describe, import data visualizations or lists into your exploration. If the visualization or list is on a dashboard, you can apply any filters on the dashboard before importing. The AI model will use imported queries to understand related questions in the same document.

    Example: Don't ask "Show me servers about to retire by location." Such a prompt is vague and complex. Instead, import a visualization from a dashboard titled "PostgreSQL servers nearing retirement,” with the desired values for the dashboard filters Lifecycle State and Days Until Retirement pre-applied. Then ask "Show me the same servers but grouped by location”.

    Once you have a productive exploration going, with a lot of context, you may find that you can ask more abstract questions and get useful answers. However, these tips might help you get started.