A few questions: • Why do I need a phone call when I’m already on my laptop? Isn’t that extra friction? • Would you actually book the flight/hotel Dot picked without manually checking everything yourself price, payment, cancellation policy, baggage, etc.? • If I still have to review screenshots, verify details and make the final decision, how much time is actually being saved? • Would love to see how this handles real failure cases too. • Also, how was Wi-Fi the main culprit when it was able to answer your 2nd query in the live demo?

👋 - we wanted to show off calling on the phone but also you can engage with dots on multiple channels in parallel. It's kinda like being on a zoom/meet call with a person where they might pull up something on a screen, send a message in the chat all while you talk. Some people also verbally process more. - you could have it send you the summary confirmation before booking. But also for a business trip some of these things are handled by the travel portal that's being used in this case - depends on how much you multitask. My dot regularly does multiple of these sort of scenarios in parallel or I kick things off and check back in later. So it's freeing up bandwidth more than being strictly faster than you locking in. - what kind of failure cases are you most concerned about? - it was a joke and nod to the steve jobs one.

Thanks for the reply! What I meant by failure cases was more about real-world failures during the actual workflow for example, a flight becoming unavailable, the price changing before checkout, a payment failing, a cancellation policy not matching what Dot understood, or Dot making an incorrect assumption about one of the constraints. I’d be really interested to see how Dot detects these situations, recovers from them, and keeps the user informed without requiring them to manually redo the whole process. That’s the kind of failure handling I was referring to.