Skip to Main Content
Shape the future of IBM watsonx Orchestrate

Start by searching and reviewing ideas others have posted, and add a comment (private if needed), vote, or subscribe to updates on them if they matter to you.

If you can't find what you are looking for, create a new idea:

  1. stick to one feature enhancement per idea

  2. add as much detail as possible, including use-case, examples & screenshots (put anything confidential in Hidden details field or a private comment)

  3. Explain business impact and timeline of project being affected

[For IBMers] Add customer/project name, details & timeline in Hidden details field or a private comment (only visible to you and the IBM product team).

This all helps to scope and prioritize your idea among many other good ones. Thank you for your feedback!

Specific links you will want to bookmark for future use
Learn more about IBM watsonx Orchestrate - Use this site to find out additional information and details about the product.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Created by Guest
Created on Mar 26, 2025

Analytics: Integration with Case Management System

Request: integrate data from case management systems like ServiceNow. Specifically, he wants to upload data (e.g., via CSV) to compare ticket volumes before and after chatbot implementation.

Details: be able to upload historical ticket data from systems like ServiceNow into the Watsonx Orchestrate analytics dashboard. This would allow for a comparison of ticket volumes before and after the chatbot was deployed, providing a clear picture of the chatbot's impact. He suggests consuming only a few key columns from the ticket data (e.g., ticket number, timestamp, region, priority).

Example: comparing "last year I had 25,000... tickets logged in ServiceNow. This year I have maybe 18,000 tickets logged in ServiceNow" and wanting to know the adoption and percentage of tickets from escalations. He also suggests uploading a CSV with columns like "INC," "timestamp," "region," and "priority."

Business Justification: This provides a holistic view of the impact of the chatbot on support operations. By comparing pre- and post-implementation ticket data, businesses can accurately measure the chatbot's contribution to ticket deflection, calculate ROI, and make informed decisions about future investments. It streamlines data analysis by centralizing information from different systems.

Idea priority Urgent
  • Admin
    Kelly To
    Sep 9, 2025

    In this agentic era, the focus is no longer on chatbots and Assistants. For customer care use cases, it may still be valuable to understand ticket volume before and after the agent, but this isn't something we'd measure as part of live agent monitoring. This sounds more like something that would exist in a custom dashboard existing outside of WXO

    Clients will have access to APIs for traces, evaluation metrics and monitoring metrics, so they will be able to export the data, bring it into their own custom dashboards and do this analysis there.

  • Admin
    Laurent Tillette de Clermont-Tonnerre
    Apr 30, 2025

    wxO agent will be able to take in documents and allow users to query those but here hte ask is to corrolate data from 3rd party apps with that of wxO which seems very custom.

    We can take that as a req for the new agentic framework to consider int he future.