21 karma · joined July 19, 2016
Having said that, I don't know how you can say that Siris backend is much better from an intent perspective without being able to leverage it properly because of the shortcomings related to the UI. From what I've seen, it doesn't even handle context well. Now it sounds like Siri will be used to do proactive things which is certainly new and different from Google Assistant. Yet, I suspect that logic is just being branded as Siri because it is a push to label Siri as your intelligent assistant as opposed to the weird robot thing you can use to check the weather
Another example is how as an Alexa skill maker, you have to provide utterance / intent mappings. Is that just used to accurately classify intent / entities? Or is it also used to identify which skill to pass a user utterance to as a part of the alexa skill service because there could be very little variation between skill names or inquiries amazon is supposed to actually fulfill when a person is talking ??
1- Being where your customers are. If you are planning on leveraging a chatbot as opposed to a mobile app or website, having some kind of presence of Facebook messenger could increase user engagement because of the lower amount of friction from switching or downloading new apps to interact with a business. It's especially relevant when you consider that social platforms are used for customer support more and more so augmenting this channel with some kind of automated support option makes sense from an ROI perspective.
2. Simpler user experiences. Now this one is definitely idealistic, and where a lot of hype is coming from. But, the general idea is to take websites and mobile apps and create a single interface into the content/services where the hope is that users will have a lower learning curve because they can use everyday language. In reality, bots that I've seen are mostly text based IVRs that confuse the users, and don't make experiences any more enjoyable.
3. Personalization and NL analytics. Assuming your chatbot allows for free form text. You could potentially build more comprehensive profiles of users by mining their conversations and behavior. You could certainly do this today with web and app metrics, twitter posts, support emails, and transcribed voice calls, but now you have a Facebook or social profile tied to a customer which is another dimension of data you can use where in the past you may have had no linkage between your app accounts vs a users social profile.
By no means a comprehensive list, and if you incorporate voice recognition on top of a "chatbot", you can provide an easier way for users to interact with systems when they may not be able to use their hands (driving, lost an appliance remote, running)
The Google team also added the ability to not return the same response for any given request, unless the request falls into generic search. It's not necessary, but gives it that human kind of element, and keeps it interesting.
I didn't try any kind of logical reasoning since it seemed to be heavily reliant on Google search, which is still keyword based to a degree. One day this will probably change, but it's a hard problem to solve given an open domain.
I thought I would see more direct integration with APIs as opposed to defaulting to search. I don't think I saw any in-fact beyond what is offered through search. EG - book me a ride with uber just goes to the search results.
I'm wondering if this team is working together with the home product. If there is also a heavy reliance on search, I can't imagine the user experience will be that great.