/* ---- Google Analytics Code Below */

Monday, June 26, 2017

A Chat Bot for Company Knowledge

I got a note recently that I should try Obie as a chat bot based on corporate knowledge provided in Slack.  I have now used Slack for several projects,  fine as a chat space for team projects,  somewhat quirky,  hard to integrate with typical and existing knowledge streams.    One of our AI goals had been to figure out how to link AI with corporate knowledge streams, old and new, static and dynamic, internal, supplier and public knowledge, structured and unstructured.    A remembrance engine we called it.  Perhaps a Knowledge Graph?   Is that what we are approaching here.?  Back to the wall we ran into:   How will it be maintained?   Just by updates in chats?   Back to the general problem of intelligent dialog.

Q&A With the Developers of Obie: A Chatbot for Company Knowledge  by Roland Meertens 

 Tasytt launched Obie: a Slack chatbot for company knowledge. Teams can ask "what, how, or where" questions such as "What is our computer policy". Obie either finds the answer in one of your documents or will ask you to provide him with the answer so he can give it next time someone asks the same questions.

Obie has integrations with several existing services: Google Docs, Confluence, Google sites, Evernote and Dropbox. This means companies don't have to start from the ground up with training Obie. Giving Obie access to this existing knowledge ensures a short training period for Obie.

InfoQ reached out to founder and CEO Chris Buttenham to ask him some questions about Obie.

InfoQ: We tried Obie a little bit in our Slack, but had the idea that it did not analyze our previous conversations. Is this a feature that will be added in a future version?

You could probably imagine you’re not the first to ask this question! Although it would seem that content living in Slack would be a natural place Obie would start, we actually feel that most conversations are fairly unstructured and somewhat useless when it comes to organizing team knowledge. We’re definitely considering adding content that lives within Slack as something Obie can reference, but we feel the low hanging fruit is the rich content scattered across multiple sources within an organization.    ... " 

No comments: