3 ms·
I think the biggest problem I've run into with company documentation is that the relevant docs either don't exist at all or are woefully out of date. Sure, ther
by smeej 3y ago
I think the biggest problem I've run into with company documentation is that the relevant docs either don't exist at all or are woefully out of date. Sure, there might be a procedure doc that spelled out how to handle a particular type of issue, but it has probably been updated three times in Slack DMs and twice on Zoom calls since the doc was actually written. And maybe at least once, the company has "declared bankruptcy" on, say, Confluence, and half-converted a few things over to Notion.
If Danswer could surface the "official" answer, such as it is, but then also note how old the authoritative doc is, and which teams have been messaging about it and/or scheduling calls with related names more recently, and then tell me who's responsible on that team for knowing the actual procedure, I'd never need another tool!
- yuhongsun 3y agoWe definitely recommend you trying it out! As far as how outdated information is handled - we pass the most relevant documents along with metadata to the LLM. So in the case you mentioned, the LLM will be provided the procedure doc and the time it was updated, the relevant Slack messages and the times they were sent, and the call transcripts along with when the call happened. The LLM tends to handle this pretty well. Additionally, during the retrieval phase, there's a time based decay applied based on the last time the document was updated. Also there is learning from feedback so users can upvote documents that are useful and downvote documents that are deprecated.
- monkeydust 3y agoThe truth will be in the code!