Skip to Main Content
IBM Data and AI Ideas Portal for Customers


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:

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

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Additional Information

To view our roadmaps: http://ibm.biz/Data-and-AI-Roadmaps

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is: https://hybridcloudunit-internal.ideas.aha.io


Status Submitted
Workspace Watson Assistant
Created by Guest
Created on May 17, 2019

Native integration with Language Translator

The pattern to build assistants supporting languages not supported by Watson Assistant is to add a machine translation service, such as Language Translator, before interacting with WA, ensuring that such interaction is performed in a language supported by WA, regardless of the end user language.

Such pattern can be easily implemented with an application orchestrator or from the client application. But such pattern can not be implemented if user wants to leverage the channel integration connectors (Facebook, Slack and others to come). To solve this problem, WA should provide either a native integration to LT or a webhook BEFORE executing the intent and entity analysis.

Using a native integration ensures only Watson LT can be easily integrated raising usage on such service and putting Watson LT in the map. Providing a webhook opens the possibility to use other translators in the market, such as Google or Microsoft. Both options solve the problem. Which one depends on overall Watson/WA strategy.