<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>vadimberman</author><text>You know, there is at least a dozen chatbot providers who can handle these nonstructured dialogues with multiple entry points, ESPECIALLY with pizza.&lt;p&gt;In fact, the pizza order is the No. 1 scenario looked at by the chatbot providers. 
In fact, it was exactly the scenario my old startup took as a case study and the first application we built with it. It could handle the different toppings, the sizes, and more. You could submit all your requests in one move, it would be parsed and sorted into its little slots.&lt;p&gt;The problem? There is only a handful of scenarios similar to the pizza. In most cases in the real world, you have to select from an external database, look at proprietary product names, and more. Another staple of chatbot demos, plane ticketing, only works well when limited to North America (in the English word). Good luck asking for a flight to Kinshasa, Kuala Lumpur, or even Wagga Wagga in Australia.&lt;p&gt;I am not even talking about the switchboards for multiple domains, like in Alexa. These ones only work with &amp;quot;leaky abstraction&amp;quot; (making the user learn magic keywords).&lt;p&gt;Another problem is really stupid. It&amp;#x27;s the availability of the datasets. The funny thing is, ye olde style semantic frameworks fare better than the machine learning ones, because there is not enough data for the machine learning chatbot frameworks, and without it, their mighty capabilities are pretty much the proverbial spherical cow in vacuum. But because the semantic paradigm is not kosher&amp;#x2F;kewl anymore, very few enterprises agree to deploy it.&lt;p&gt;None of that matters though because the users never liked typing a lot. Back in 1980s - 1990s the adventure type computer games switched from (mostly working) command line interface to point-and-click, and very few users objected.&lt;p&gt;My take is, the key is a conversational UI with strong visual feedback. For the pizza scenario above, I would draw icons of cheese and numbers, so that the user can be sure it worked.</text><parent_chain><item><author>Ajedi32</author><text>I think the ultimate goal is to make the &amp;quot;acceptable entry points&amp;quot; so numerous and the variety of acceptable wordings so broad that you can approach the assistant with pretty much any goal you have in mind and it&amp;#x27;ll walk you through how to accomplish that.&lt;p&gt;Imagine if this was a realistic conversation with an assistant:&lt;p&gt;&amp;gt; &amp;quot;Hey Google, I&amp;#x27;d like to order a pizza.&amp;quot;&lt;p&gt;&amp;gt; &amp;quot;Sure, what kind?&amp;quot;&lt;p&gt;&amp;gt; &amp;quot;Let&amp;#x27;s see... cheese, pepperoni, sausage... and maybe some green pepers?&amp;quot;&lt;p&gt;&amp;gt; &amp;quot;Alright. What size?&amp;quot;&lt;p&gt;&amp;gt; &amp;quot;Hmm, so I need to feed 4 people...&amp;quot;&lt;p&gt;&amp;gt; &amp;quot;Sounds like a large?&amp;quot;&lt;p&gt;&amp;gt; &amp;quot;Sure, let&amp;#x27;s go with a large.&amp;quot;&lt;p&gt;&amp;gt; &amp;quot;Alright. There&amp;#x27;s a Dominos nearby, I can order that for $8.99.&amp;quot;&lt;p&gt;&amp;gt; &amp;quot;Sounds good.&amp;quot;&lt;p&gt;&amp;gt; &amp;quot;Alright, I&amp;#x27;ve ordered your pizza. Expected delivery in 15 minutes.&amp;quot;&lt;p&gt;No need for the human to understand what the &amp;quot;entry point&amp;quot; is, because you can approach the assistant with pretty much _any_ entry point and it&amp;#x27;ll give you a useful response. We&amp;#x27;re still not there yet, unfortunately, and I think it&amp;#x27;ll be quite a while before we are.</text></item><item><author>tootie</author><text>Chatbots be they voice or text face the same user interface problems that old school command-line interfaces did 20 years ago before windowing GUIs came about. When you start up, you&amp;#x27;re faced with a void. it&amp;#x27;s extremely difficult to convey to users what the acceptable entry points are and how to phrase them to get what you want. The inputs are far more generous than classic command-line world, but it&amp;#x27;s still vague enough to induce paralysis in end users. If I have a bunch of pull-down menus with clear directives on what I can and can&amp;#x27;t do, I&amp;#x27;m going to be productive much more quickly.</text></item></parent_chain></comment><story><title>Facebook’s Virtual Assistant M Is Dead</title><url>https://www.wired.com/story/facebooks-virtual-assistant-m-is-dead-so-are-chatbots/</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>Spooky23</author><text>Obvious problem is you didn’t order pizza, you ordered Dominos, and your selection is limited to who ever signs a deal with Google or pays them off for top billing.&lt;p&gt;Correcting that means now you’re arguing with Google&amp;#x2F;Alexa&amp;#x2F;Siri, which is an infuriating experience.</text><parent_chain><item><author>Ajedi32</author><text>I think the ultimate goal is to make the &amp;quot;acceptable entry points&amp;quot; so numerous and the variety of acceptable wordings so broad that you can approach the assistant with pretty much any goal you have in mind and it&amp;#x27;ll walk you through how to accomplish that.&lt;p&gt;Imagine if this was a realistic conversation with an assistant:&lt;p&gt;&amp;gt; &amp;quot;Hey Google, I&amp;#x27;d like to order a pizza.&amp;quot;&lt;p&gt;&amp;gt; &amp;quot;Sure, what kind?&amp;quot;&lt;p&gt;&amp;gt; &amp;quot;Let&amp;#x27;s see... cheese, pepperoni, sausage... and maybe some green pepers?&amp;quot;&lt;p&gt;&amp;gt; &amp;quot;Alright. What size?&amp;quot;&lt;p&gt;&amp;gt; &amp;quot;Hmm, so I need to feed 4 people...&amp;quot;&lt;p&gt;&amp;gt; &amp;quot;Sounds like a large?&amp;quot;&lt;p&gt;&amp;gt; &amp;quot;Sure, let&amp;#x27;s go with a large.&amp;quot;&lt;p&gt;&amp;gt; &amp;quot;Alright. There&amp;#x27;s a Dominos nearby, I can order that for $8.99.&amp;quot;&lt;p&gt;&amp;gt; &amp;quot;Sounds good.&amp;quot;&lt;p&gt;&amp;gt; &amp;quot;Alright, I&amp;#x27;ve ordered your pizza. Expected delivery in 15 minutes.&amp;quot;&lt;p&gt;No need for the human to understand what the &amp;quot;entry point&amp;quot; is, because you can approach the assistant with pretty much _any_ entry point and it&amp;#x27;ll give you a useful response. We&amp;#x27;re still not there yet, unfortunately, and I think it&amp;#x27;ll be quite a while before we are.</text></item><item><author>tootie</author><text>Chatbots be they voice or text face the same user interface problems that old school command-line interfaces did 20 years ago before windowing GUIs came about. When you start up, you&amp;#x27;re faced with a void. it&amp;#x27;s extremely difficult to convey to users what the acceptable entry points are and how to phrase them to get what you want. The inputs are far more generous than classic command-line world, but it&amp;#x27;s still vague enough to induce paralysis in end users. If I have a bunch of pull-down menus with clear directives on what I can and can&amp;#x27;t do, I&amp;#x27;m going to be productive much more quickly.</text></item></parent_chain></comment><story><title>Facebook’s Virtual Assistant M Is Dead</title><url>https://www.wired.com/story/facebooks-virtual-assistant-m-is-dead-so-are-chatbots/</url></story>