We think both chat and navigational UIs have a time and place. This should really be an essay, but I'll try to keep it short. Chat isn't being used to say we u

We think both chat and navigational UIs have a time and place. This should really be an essay, but I'll try to keep it short. Chat isn't being used to say we use chat. Chat allows us to easily use humans on the backend to interpret things that computers are just much, much slower at doing right now and would require a lot of engineering work for a wide breadth of user states that are currently unknown due to lack of data / users. I personally do believe the _ideal_ (golden/dream state) UI would be a "navigational" one that makes a lot of assumptions but states them all, asks a lot of certain dynamic questions, and presents information in different styles depending on context. Humans are quite good at this (most people love Slack'ing their assistant to book travel), but we really haven't found a UI that does this well for travel and don't believe it's the best way to start attacking the underlying problems. However, I agree that some parts of the travel journey should be a navigational app though and not chat-based. For example, checking an itinerary is better done through navigational UI-- I don't want to reference a chat transcript for that. (TripIt is ok here and works off of your email, we might make something of our own later).