Earlier quoted context omitted.
Thanks. The really fascinating thing is have a direct "stream of conscience" from our customers. With a 1000+ conversation a day you really get to see the problems they are having with our products, processes, UX etc As well as their responses to things in the news etc. Our product teams love it.
That's a lot of conversations! Have you considered using some machine learning techniques?
Bottery – A conversational agent prototyping platform
71–75 of 75 posts
Re: Bottery – A conversational agent prototyping platform
#72Earlier quoted context omitted.
I have been building/running a pretty successful chatbot for a large corporate for over a year now. We use Inkles Ink to script the conversation flows and maintain state. Works very very well. https://github.com/inkle/ink
Hey - @joethephish here from inkle! Really cool to to hear that you're using ink for that :) Would love to know more detail about where this is being used if you're able to share!
Re: Bottery – A conversational agent prototyping platform
#73Re: Bottery – A conversational agent prototyping platform
#74Earlier quoted context omitted.
I have been building/running a pretty successful chatbot for a large corporate for over a year now. We use Inkles Ink to script the conversation flows and maintain state. Works very very well. https://github.com/inkle/ink
Hey - @joethephish here from inkle! Really cool to to hear that you're using ink for that :) Would love to know more detail about where this is being used if you're able to share!
Re: Bottery – A conversational agent prototyping platform
#75Last year, we had built almost the same thing. It's Open Source but unfortunately, haven't added any documentation (will do when I get time) - https://github.com/yak-ai/wild-yak Lessons learnt: - Works much better than AI driven bots at the moment - Don't pretend to do intelligent things. Be just a dumb textbot. - Force people into selecting options as much as you can - When accepting data as text, give an example of…
We are too obsessed about UI widgets, but forgot one thing: the screen space is just 2D, you cannot put too many things in the 2D space, so we introduce levels, but lower-level interactions are often neglected by users, a dilemma.
But with dialog-style UI, we introduce the extra dimension of time. When we distribute user interactions on the time dimension, sometimes limited screen space is no longer a problem.