Build with Watson Apps

Expand all | Collapse all

Responding to non-English responses

  • 1.  Responding to non-English responses

    Posted 21 days ago
    Hi All, 

    I would be interested to hear how people who are building public facing bots address the issue of non English language users. 

    I was thinking of having the welcome message state that non English language users can access information via a given URL. 

    How have people dealt with with this issue?



    Marty Kelly

  • 2.  RE: Responding to non-English responses

    Posted 21 days ago
    Edited by Daniel Toczala 21 days ago

      Great question.  In the library for Watson Assistant  you will see a link to an article on a Guide to Multiulingual Chatbots.  That is a great place to start.  Often we will see our customers, like Harris County, use multiple buttons to launch chatbots, and do a language-specific chatbot for each supported language.  Some of this depends on the subject matter - some knowledge domains lend themselves to easy language translation (so a single chatbot, with language translation used to convert to your customer's primary language), while others may be complex where straight language translation will not capture nor c ommunicate subtle ideas and concepts.

    Daniel Toczala
    Community Leader and Customer Success Manager - Watson

  • 3.  RE: Responding to non-English responses

    Posted 20 days ago

    You could tie in language translator to identify the language, and if not the language you expect, have a dialog node that redirects them to use English or whichever is native. But as Tox pointed out there are ways you can potentially support multiple languages easily.

    Here is another guide I wrote with code samples too:

    Mitch Mason