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 Under review
Created by Guest
Created on Apr 17, 2026

Four configuration options are missing in Audio Settings panel

The current Audio Settings in WatsonX Orchestrate lack the granularity required for production-grade voice channel deployments. During our ongoing PoC with a banking client (SIP channel), we identified four missing configuration options that are necessary to meet the client's requirements and deliver a quality voice experience. The absence of these controls limits our ability to fine-tune voice behavior, reducing the client's confidence in the platform's flexibility for their use case.

Missing configuration options

1. Enable / Disable Pre-Hold Message

No toggle to fully enable or disable the pre-hold message at the configuration level. Clients should be able to turn this feature on or off according to their interaction design.

2. Pre-Hold Message Timing Configuration (Delay / Duration)

No way to configure when the pre-hold message is triggered — neither the delay before it plays nor its duration. Clients need control over timing to align with expected agent response latency and avoid the message firing too early or too late.

3. Enable / Disable On-Hold Music

No option to enable or disable on-hold music. Clients must be able to control whether music plays during hold periods, as this varies across use cases and brand guidelines.

4. Disable Pre-Hold Message on First Interaction

No option to suppress the pre-hold message specifically on the first conversation turn. This is needed to avoid playing a hold message before the agent's initial response (e.g. agent introduction), which creates a poor first impression.

Idea priority High