The Conversation Service of IBM, as its name indicates, is dedicated to conversations only, while the conversational (dialogs) aspect with Microsoft is handled by the bot framework.

Note that IBM’s Conversation Service API allows to send a piece of text and return the matching intent(s) and entities without a conversation context.

Chatbot for you xxx-79

Granularity may be achieved with Bluemix by creating multiple containers and spreading your Watson services over them but that’d require you to use multiple browser tabs to manage them all.

In Azure, you can mix all your services spreaded over different locations within the same ‘container’ in a single UI view.

With LUIS, I used an entity of type incident & another one of type request.

Then, I trained LUIS the following way: by tagging the items in bold to either incident or request.

So, it is technically not impossible to use the Conversation Service outside of a conversation but that’s kind of deviating from its intended purpose.

Creating intents is about the same user experience for both IBM & Microsoft.

While this offers greater accuracy, it is first and foremost a limiting factor because it’s completely static here.

There is no so-called intelligence in this way of extracting entities.

For one of the bots I wrote, I had to extract incident & request numbers relating to IT services.