Search Slack history for previously answered questions
Build an internal "has this been asked before?" app. someone types a question into a page and it searches our slack history to check if it's already been answered. this is how I see this working: - a page with a single search box where someone types their question - an AI step takes the question and generatess a few seearch query variants (synonyms, different phrasings, likely tool names) so we don't miss answers that were worded differently - we then search slack (only connector for now, but can add more later) with all variants and collect the candidate messages/threads - then a second AI step acts as a strict grader: for each result, decide if it ACTUALLY answers the question or just shares keywords. this is only useful if it is accurate. score each one, throw away anything that doesn't clearly answer it. i'm afraid we do need to be harsh... wrong "this was answered" is worse than no answer - we should also factor in age... results have timestamps, prefer recent ones, and flag anything old as possibly outdated and might need double checking - if good results survive: show a synthesized answer at the top, then source cards below: each with a snippet, the date, and a deep link (slack permalink) to the original thread. every claim in the answer must come from a linked source (!!!) - if two sources conflict, prefer the newer one and say so. again might need double checking - if nothing survives grading: don't make something up. say "this doesn't look like it's been asked before" and suggest asking in the right channel (.. should we suggest a channel?) - show a confidence indicator on the answer, and a visible staleness warning if the best source is more than ~6 months old - loading state should show pipeline progress ("searching slack… grading results…") not just a spinner because i guess this won't be the quickest. keep the ui clean and simple and usable... ideally one box, one answer, sources underneath. accuracy is the most important thing + let's do the index approach. build a separate ingest workflow: for a configured list of channels, backfill the full history (paginate conversations.history all the way back), and store each message as a record with text, user, timestamp, channel, thread context, and permalink. skip join/system messages. then a scheduled incremental sync (every 15 min or so) that only pulls messages newer than the last stored timestamp per channel. switch the search app to query this index instead of live-scanning slack, and keep the grading pipeline exactly as is. also show the index's coverage on the page ("searching 6 channels, history back to jan 2025") so it's honest about what was and wasn't looked at. Tools used: Slack, an LLM for query expansion and result grading, 3B named volume (message index storage)
What this prompt builds
This workflow helps new employees find answers that already exist in company Slack history. It uses AI to search indexed Slack messages, grade results for accuracy, and either return a sourced answer with confidence scoring or suggest where to ask the question. A separate ingest workflow maintains a searchable index of configured Slack channels.
The problem
New employees waste time searching for information that already exists scattered across Slack channels — digging through old messages to find license links, setup instructions, or answers to common questions. This workflow indexes Slack history from configured channels and lets anyone search it with a natural language question. AI generates search variants to catch different phrasings, grades each result for accuracy and relevance, and either returns a synthesized answer with timestamped source links and confidence scoring, or honestly states the question hasn't been asked and suggests a channel to post in.
Solution and impact
Teams eliminate duplicate questions and reduce onboarding friction by surfacing institutional knowledge that's already been shared. The workflow maintains an indexed, searchable history of configured Slack channels with automatic incremental updates, flags stale or conflicting information, and never invents answers — it only returns results it can cite with permalinks. Employees get instant, sourced answers or clear guidance on where to ask, saving hours of manual searching and preventing information silos.