Warn me the new flight clashes with a recording that is only in Slack
Every CEO Dan Shipper was changing a flight out of San Francisco with his Dot when the agent interrupted its own flight research with a warning: the option might overlap with head of video Randy Counsman's Wednesday morning recording. There was no such recording on Shipper's calendar — the Dot had read a Slack discussion he had never seen, clocked the proposed schedule, and connected it to the flight he was about to pick.
How it works
- Shipper asks his Dot to help change the flight
- Dot researches options
- Dot warns an option may overlap with Randy's Wednesday morning video recording
- No recording exists on his calendar
- The commitment turns out to have been proposed in a Slack thread he had not seen
Why it’s worth knowing
The conflict was not on any calendar — the agent found a colleague's proposed recording buried in a Slack thread its owner had never opened, and raised it at the exact moment the flight choice made it matter.
Where it’s from
Summarized from a public post on every.to. See the original ↗