Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use agnostic platform like API.AI? #9

Open
mgottholsen opened this issue May 19, 2017 · 6 comments
Open

Use agnostic platform like API.AI? #9

mgottholsen opened this issue May 19, 2017 · 6 comments

Comments

@mgottholsen
Copy link

Does it make sense to use something like API.ai to build the conversational interface, and then click & generate the integration you want to deploy to (Alexa, Google Assistant, FB etc)?

@ghost
Copy link

ghost commented May 19, 2017

I've got the same question. We're also looking into this.

@JustinHerman
Copy link

Right now we're in the process of going through many of the lessons learned from the hackathon, and on-boarding new elements. We will have a full update next week on next steps -- we are in a very good spot right now thanks to your efforts.

@youmustfight
Copy link

youmustfight commented Jun 29, 2017

I moved away API.ai handling conversation because managing and building the conversational flow felt cumbersome within their interface (this was a few months ago though). Now I just use Wit.AI for processing an incoming statement and manage the flow in our own state machine. The downside to API.ai IMO is that you can't use parts of the messaging platform APIs in as creative or useful a way for your use-cases (Ex: Check out the Trivia Blast bot on Facebook Messenger)

@mikeendale
Copy link

I think Wit.ai is a better option to use conversational interface. They have a much better intent handling

@GuyClinch
Copy link

GuyClinch commented Jul 6, 2017

Interesting article:
• Artificial intelligence (AI), in the form of voicebots, has taken center stage, “seemingly nudging chatbots out of the limelight even though we all started using them last year,” writes John Brandon. “The truth is,” Brandon contends, that “voicebots didn’t outshine chatbots because of the speech recognition features and ease of use — at least, not entirely. What really happened is that Microsoft, Apple, Google, and Amazon overshadowed chatbots — and, by extension, took the attention away from Facebook Messenger and other texting tools.” He expresses, “We prefer direct access to the weather, not an app running a bot. We realized an AI should provide first access, not a second or third layer back.” Venture Beat

@GuyClinch
Copy link

My opinion RE: the Venture Beat post is that this is not an either/or proposition but an all-of-the-above. There's a billion different conversation styles in the wild and the successful communication platform is agnostic to how the customer consumes. It's no longer "build it and they will come," it's reach me in how I prefer at any given moment or circumstance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants