Thank you for using the Watson Dialog service on Bluemix. We’d like to inform you that we are retiring the Watson Dialog service on August 9, 2016. On July 11, 2016, we released the generally available Watson Conversation service to replace Watson Dialog so that you can build more compelling bots and virtual agents.
Watson Conversation includes a rich set of tooling that allows users to easily create an intent classifier, extract entities, and design dialog flows without having knowledge of xml or coding. Please see this blog post for more details on Watson Conversation.
Here’s what you need to know:
End of Marketing Date: September 8, 2016
As of September 8, 2016, the service tile will be removed from the Bluemix catalog, and you will no longer be able to provision new Watson Dialog instances. However, existing instances will continue to be supported.
End of Support Date: August 9, 2017
For a period of 365 days after the service retirement date, through August 9, 2017, all existing instances will continue to be available to users through their Bluemix dashboard, and will continue to be supported by Watson Dialog.
Any instance still provisioned as of the End of Support Date will be deleted.
Users are therefore asked to unprovision their Watson Dialog service instance(s) prior to the End of Support Date.
We encourage existing Watson Dialog service users to move to the Watson Conversation service on Bluemix now. Please see this blog post for more details about the key differences between the two services that you will need to know.
As always, we’re here to help! Please reach out to us in the support forums, or on Twitter.
—The Bluemix Team
Please Note: Deprecation of Japanese-enabled Dialog API will be separately announced.
Our application is using dialog service and system has gone live. There is a high risk to finish migrating from dialog to conversation service before Sep.8. Is there any automation tool to help us to accelerate migration in your team.
Latently, Bitfusion, and IBM Cloud partnered to provide a deep learning development platform and best-in-class GPU infrastructure allowing you to publicly replicate all AI and ML scientific papers via the Latently Deep Learning Certificate (LDLC) program.
More and more chatbots are being developed and there are good reasons for it. Not all chatbot projects succeed. Often, missing user acceptance is stated. The dialog system might not have hit the nerve, might not have fitted into the target environment. Would you talk with a friend who does not remember your name is repeating the same five phrases over and over again? I would not. So what can be done to make chatbots more lively, more human-like? Here are some best practices and ideas on how to implement them.
Gotta read this if you have never used Watson Natural Language Understanding (NLU) before or if you had signed up for NLU's Free Plan. If you use the NLU Standard Plan, nothing changes but feel free to read on!