How to Find an Old Conversation in Slack
Find an old Slack conversation with names, channels, dates, and remembered phrases, then preserve the important context outside the thread.
Start with the detail you remember
You rarely remember a whole Slack message. You remember a person, project, client, document, or distinctive phrase. Begin with that clue and avoid broad words such as meeting, update, or question.
If Maria discussed contract changes in a project channel, try:
contract from:@maria in:#project
Change one part at a time if nothing appears: remove the channel, try a related word, or widen the date range.
Narrow by person, channel, and date
Use from:@name when you remember who wrote the message. Use in:#channel when you remember where it happened. If the channel is uncertain, search without it because the exchange may have moved into a direct message or another project channel.
For approximate dates, search a window rather than the whole workspace:
contract from:@maria after:2026-07-20 before:2026-07-28
If that fails, widen the range. Memory for recency is imperfect; a calendar event or email timestamp can identify the correct week.
Search related words
The message may say renewal instead of contract, approval instead of sign-off, or Friday instead of a date. Search a short list of synonyms, document names, customers, products, and teams one at a time.
Once you find a relevant result, open the surrounding conversation. Check nearby messages, replies, reactions, linked files, and the full thread before starting another search.
Follow the conversation into other tools
A decision may begin in a meeting, continue in Slack, and finish in email. Search each source with the same names, topic, and date range.
In Gmail, combine from:, to:, subject:, before:, and after:. In meeting transcripts, search for the project, attendee, or unusual phrase. For text messages, start with a person and distinctive word rather than scrolling; see find an old text message quickly.
If you cannot remember the app, reconstruct the sequence from calendar events, Slack, email, documents, and meetings. The guides to recovering last week’s work context and finding WhatsApp saved messages address adjacent archives.
Capture the useful part after finding it
Do not copy an entire thread unless every message matters. Save a compact record containing:
- The decision or answer.
- The people involved.
- The date.
- The next action and owner.
- Links to the Slack message, email, transcript, or document.
After an important meeting, a 60-second voice memo can capture what was decided, what you agreed to do, and what you expect to forget. Give it a descriptive name or store it with the project.
The goal is not to document every conversation. Capture the few details that would be expensive or frustrating to reconstruct.
Choose the search surface that matches the source
- Slack search: best for recent Slack-only exchanges; availability depends on the workspace’s plan and retention policy.
- Email search: best for formal decisions that reached Gmail or Outlook.
- Meeting transcripts: Otter, Zoom AI, Fathom, and similar tools help when the meeting was recorded, though long transcripts and keyword mismatch remain limitations.
- Post-call voice memo: useful for preserving the decision while fresh, but requires a habit and can become hard to retrieve if left in an anonymous audio library.
- dEssence: can hold deliberately saved messages, voice memos, links, and notes together for plain-language retrieval. It knows only what you choose to save.
If a message matters as a long-term record, do not leave the only copy in a chat thread. Move the decision into the project or documentation system where you expect to find it later.
dEssence limitations: it is available now, has no native iOS or Android app, and the free plan covers up to 20 saves a day. Pro is $10 a month. Its save surfaces are the Chrome extension, Telegram bot, and web app; it is free to start with no card.