I desperately wanted to tackle knowledge retrieval problems when I worked at Slack, to the point where I built prototypes during nights/weekends to try and get

I desperately wanted to tackle knowledge retrieval problems when I worked at Slack, to the point where I built prototypes during nights/weekends to try and get internal traction. Slack easily has one of the most valuable and important datasets in the world for training corporate agents. IMO, the most useful rejects were: - Subscribe to a search query. Get an RSS-like digest of Slack messages, external document updates, CRM interactions, etc. - Auto-responder I called "escal.ai," named after Slack's internal naming convention for help/support channels. These channels were prefixed with #escal-<subject>. I built a variation of https://arxiv.org/pdf/1901.05415.pdf https://arxiv.org/pdf/1901.05415.pdf to handle asymmetric retrieval tasks, where the answer to a question was typically a Slack post in another channel.