| My issue with these services is they always tout these use cases like: >"Can you make me dinner reservations?" or >"Can you help me plan my next vacation?" I'd really love to better understand who is actually asking those types of questions in such a vague fashion, and what their use case is. When I'm picking something as simple as a restaurant, I typically want options, I want to read reviews, I want to consider distance, parking, attire, etc. While their AI/human trainers might be able to handle this level of complexity eventually, the actual phrasing of the question would likely be much more complex than "can you make me a dinner reservation." Doubly so for something like a vacation which has a lot more moving parts. But I respect that I'm reflecting on a sample size of one...me. So I'd love to hear from others with more insight into the data around this. Are people actually searching with such generalized queries when it comes to tasks like this? Do most people not sweat the details of things like which restaurant to eat at, or where to spend hundreds or potentially thousands of dollars on a vacation? Not trolling, serious question. |
I'm thinking "get me a dinner reservation next sunday with patio seating for 5 in the east village at an upscale tapas place".
As I mentioned elsewhere on this page, my thesis around conversational interfaces isn't that they start off broad and use more Q/A to refine your query. That's slow, and people are visual.
Rather, their power lies in the user being able to express a complex query in one go - which is equivalent to tapping 10-15 filters and scrolling through results - ideally combining data from sources that aren't limited to one service.
You can now execute related actions to your result set through the same interface, without needing to shift to a single purpose app that would allow you to take the action, but for most purposes, won't keep your context.