The same way it would know where “my door” is in your example: From previous context, other calendar integrations, and information/settings you’ve given it (or

The same way it would know where “my door” is in your example: From previous context, other calendar integrations, and information/settings you’ve given it (or given it access to). “There’s a court available 150 miles away; the Uber will be at your door at 3PM to get you to the court by 6” is a legal but non-sensical solution in your version of the interaction. You have to have some kind of implicit rules and some kind of explicit configuration whether that’s “when I say my door, I mean X” or “when I play tennis, the default duration is an hour and I prefer club Y over town court T1 over town court T2.” And an implicit “people don’t want to spent more time in transit than at an activity, so first constrain search and issue a notice to the user if a solution chosen violates this”.