It's true the one in our home page is a bot to illustrate a simple scenario with some of the features that Xatkit includes (if you ask the bot for a demo)
Hi there.
I can help you get up to speed with a REST API
Just give me the URL of the OpenAPI definition of your API
> What is an example of an OpenAPI definition?
Loading the API from . Please wait...
Oops, I couldn't parse your definition
Here is the error message:
no protocol: Xatkit
Clearly, in the above example, you didn't provide what the bot was expecting and since the bot is a research prototype, it had not enough training to identify that you were not providing an API file but asking a clarification question.
No, the bot owner should the dashboard to realize that a user (you) asked this question that made the bot failed and should prepare a new version of the bot that can answer it
In chatbot systems, the machinery doesn't do very much. It's anticipating almost all possible user responses that makes the thing work, if it does. All the engine really does is take the user's question and match it to some big FAQ file someone put in. Plus there's some kind of phone-tree like path to guide users through whatever the chatbot wants them to go. (Not where the user wants to go.)
In game development, this is called The Dev Team Thinks of Everything.[1]
[1] https://tvtropes.org/pmwiki/pmwiki.php/Main/DevelopersForesi...
This seems to be a generic problem with chatbot companies. I have yet to find one with a bot intelligent enough to answer basic questions about the chatbot product. Most chatbots are about as smart as "press 1 to pay bill, press 2 to return product..." with a weak natural language system on top. A basic web site is more useful.
[1] https://xatkit.com/