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.

Add idea Subscribe
Status Under review
Created by Guest
Created on Apr 17, 2026

RELATED IDEAS

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
  • Post comment
  • 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.

    Reply

By clicking the "Post Comment" or "Add Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not include IBM confidential, company confidential, or personal information in any field.
Having problems accessing this portal? Describe the problems in an email to ideasibm@us.ibm.com.