I was in an area where I couldn't do any narration/voice with the demo and it still did really good just from the visuals + DOM, pretty awesome. Thanks for sharing.
Our value-add here would be providing the pipelines for one-click deployment (SMS, Facebook, Slack etc) and structuring of conversation flow, in addition to things like post-deployment analytics and insights on how users are talking to your bot. In terms of NLP, we actually take an agnostic approach to whether users want to use Wit.ai (or api.ai etc) in conjunction with our service, or use our NLP offerings. Thanks for the question!
The platform is only hours old in terms of public availability, but here's a pretty cool customer service demo bot that scans a knowledgebase first, but can create a helpdesk ticket if human assistance is required: https://www.youtube.com/watch?v=e9IMsJW4ca0
Maybe I'm missing something, but can't a normal website do all that?
Or is the idea that you can feed message-only channels like email and Facebook messanger to it? But then you could just say "We don't really provide email support; see our website here: ..."
Kind of feels like using telephone menus when you don't have to.
(Nothing against your platform though - it looks very well done!)
Should be on the home page, perhaps even above the fold already asking you a question with a side-by-side of the flowchart components being activated/highlighted.
That's a super good UI suggestion, thanks. We just launched our public beta about 6 hours ago and have been thrilled with the response and very unique bots being created (particularly when people leverage IFTTT and Zapier too) ... we'll definitely be surfacing as many cool uses as possible ASAP :)
