Skip to Main Content
IBM Data Platform Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data Platform organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:


Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,


Post your ideas

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea


Specific links you will want to bookmark for future use

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.

IBM Employees should enter Ideas at https://ideas.ibm.com



Status Under review
Created by Guest
Created on Apr 17, 2026

Add STT/TTS trace and log visibility in voice channel

When using the voice (SIP) channel in WatsonX Orchestrate, there is currently no way to inspect what the STT engine transcribed from the user's audio input, nor what text was passed to the TTS engine for synthesis.

This creates a significant observability gap during development, testing, and production troubleshooting. When a voice interaction produces an unexpected result, it is impossible to determine without external tooling whether the issue originated in transcription (STT misread the user), in the agent logic, or in speech synthesis (TTS rendered the response incorrectly or incompletely).

Developers and implementation teams are left guessing at the root cause, which significantly increases debugging time. The platform should expose STT transcription results and TTS input strings as part of the interaction trace, ideally alongside the existing agent reasoning and tool call logs. Log retention and filtering by session or interaction ID would further increase the utility of this feature.

Idea priority High
  • Guest
    May 25, 2026

    The current lack of visibility into the STT/TTS payloads within the Watsonx Orchestrate voice channel creates a severe bottleneck for development and production support. transcribe

    When an interaction fails, we currently cannot isolate whether it’s an acoustic issue (STT misinterpretation) or a cognitive issue (LLM/Agent logic).

    To make the platform truly enterprise-ready for voice, we urgently need:

    • STT/TTS payload visibility injected directly into the interaction trace/session logs.

    • Session ID filtering to trace a single call end-to-end.

    Hope to log this as a critical feature request with the platform team.