[avocabros]

Sounds cool and I hope you can make it work; what I don't understand, though, is how to solve for the hidden preferences which are the major barrier when scheduling.

E.g. I'm friends with so-and-so and I don't want to be a jerk and schedule a 4:30PM Friday meeting (regardless of whether this is sensible, it's the reality). Or, I see continuous blocks of meetings on someone's calendar with only one open slot, presumably where they'll eat lunch; I shouldn't take that slot. Except for that one guy who I know doesn't eat lunch. Alternatively, I'm getting on a flight at 3PM and working the last 2 hours from a plane; I haven't actually blocked by calendar (people are lazy), so I can't actually do meetings then. Or, I know there's a conflict but someone told me to book over it.

You can go on with the "hidden context". Perhaps this works in some industries where calendars can be trusted, but I've always found the "hidden preferences" to make scheduling optimization essentially impossible. How do you know, for example, when it's okay to reschedule a meeting? How do you say, well, if X person can't be there but Y can, it's okay, but ideally they'd both be there, but not if we have to move it further than a week out from today, then it's fine; but I'll check with X and Y anyway on that?

[skorisep]

This!!! This is exactly where we shine. There is still a lot of work that we have to do (especially on an individual level). But we try to understand as much about an industry, organization, culture, and person as possible to infer those human dynamics that make scheduling such a human problem.

And each industry differs with this respect. So we collect the data and generalize it across our customers if they fit the group: all while giving them enough flexibility to schedule their own individual way.

This is why we believe it is important to have a self-learning and adapting system as well.