Ask HN: Is API-first chatbot constructor usefull to anyone Hey, HN. I have a question for you. We use our own bot constructor for years. It allowed us to build numerical chatbots and chatbot-based products, mostly for HR. It's quite simple, has almost none visual interface and has full REST API to create, consume and connect chatbots. It's not an NLP or AI-based in any way, good old Finite-State-Machine in XML form, with keywords support (with some additional NLP processing like stemming and so on), regex and etc, so you can build entire chatbot by building XML in pure code. You can plug any NLP engine, like MS QnA or Dialogflow if you wish though. It also provides wide abilities for integration like POST and GET requests, Azure Functions integration, some limited memory, user profiles and string parsing capabilities. Some messaging capabilities like Push and Broadcast available as well. I wonder is it worth to make it available to the public? Any thoughts on this? |