This is interesting to me because it really pulls together a number of disparate technologies to get towards the goal of being &quot;the AI&quot;. There&#x27;s nothing he talks about that&#x27;s overly complicated on it&#x27;s own, but integrating them all together is the key.<p>Once you have the voice to text (ASR) from Nuance (or any of the other companies in this space), then it&#x27;s a question of properly recognizing the contextual intent. Not a trivial task, but certainly getting easier with technology available. I think the visual models displayed in the demo are fairly telling as to how they handle this. Keywords for a domain (e.g. weather) become useful to determining the intent of the speech, as well as variables used in queries, or the data returned for display to the user.<p>For example, if I ask a question that mentions temperature, and a time, but not a length of time, it&#x27;s fairly obvious I&#x27;m asking for something in a weather domain rather than a recipe domain (and vice versa).<p>I&#x27;d guess the developer integrations he mentions then become a matter of defining those data points&#x2F;variables for the different data source so the &quot;AI&quot; can build the application to execute.<p>It&#x27;s like an enhanced API integration model. You need to know all of the input&#x2F;output parameters to integrate with an API. The intent&#x2F;contextual piece also uses the individual data points for the contextual intent recognition in the voice-to-text area.<p>The other interesting aspect is actually storing the preferences for the commerce side of things. Airlines do this already for saving preference of aisle vs window seats. They&#x27;re taking things a step further to remember those types of &quot;qualifying data&quot; for interactions you have so they can be saved across areas (read: API calls).<p>I suspect there will be a ton of work on behalf of the APIs too handle data in this way too, that&#x27;s what he says when it will take some time to see the direction things go in. If I opened up my existing airline travel APIs to this today, it&#x27;s unlikely anyone could correctly interact in a way that would provide all of the information needed to actually book a ticket. So, there will need to be some back-and-forth communication of those missing items. If someone finds a ticket they want to book and says &quot;order it&quot;, then viv will need a way for the API to communicate &quot;That&#x27;s great, but you also need to provide your TSA known traveler ID number&quot;. Then, because it&#x27;s something an API has asked for, Viv will know it&#x27;s a data point it should save for later.<p>Let&#x27;s hope Viv has un-breakable encryption and security with all of those &quot;personal preferences&quot;...