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 Submitted
Created by Guest
Created on Feb 27, 2025

Standardize Teams integration behaviour

The behaviour of Watsonx Assistant differs from Web to the Teams integration, while we would expect it to have the same behaviour (i.e. replicate what we have during preview).
The support case (CS4233476) linked show the issue details, which is summarized as :

In the context of a RAG chatbot:


1. A user enters a valid question, direct it to an assistant action where the assistant says some text to acknowledge and say that we are looking for information in our datasources. Then, it calls another action performing that search with an extension.

2. The action and extension execute and generate the response and send it to the user.


The issue is that using Teams, the acknowledgement message is not sent when the user enters a question, but only after the response has been generated (all messages arrive at the same time, not acknowledgement and a few seconds later the answer). This makes the user unaware of whether the bot has taken his demand or is not responding for some reason.


A workaround is to request a user input after the acknowledgement message, but that do not make sense as we have nothing to ask. Setting the skip_user_input variable has no effect. So there is currently no admissible workaround for this issue.


The current chatbot is used by ~30 people and this is impacting users every session. As the project is going to extend to more user, solving this issue would improve the user experience greatly.


Idea priority Medium