Channels, threads & search
How this is scored
The daily surface: channel model, threading, mentions, files, and whether search can find a decision made eighteen months ago.
0 — Flat group chats with no threads; search covers recent messages only, and history is capped.
3 — Channels and direct messages with basic search, but threading is awkward or absent and file handling is a plain attachment list.
5 — Public and private channels, real threads, mentions and reactions, file sharing with previews, and full-text search across the whole history.
8 — Cross-organisation or guest channels with clear boundaries, message editing history, pinned and saved items, search with filters by channel, person and date, and a documented history limit or none at all.
10 — The archive is a working knowledge base: search that ranks well across years, threads that stay readable, channel lifecycle management (archive, rename, merge) without losing history, and export of a conversation in a form a human can read.
The Platform Engineer
Channels are real and well-typed — organisation, teams, external and personal — with unified search across messages, users, channels and departments plus search tags to narrow results, and conversations archived for future reference. Threads are only confirmed in passing on the AI integration page, and I found no public information on pinned items, message-edit history, or a documented history limit. A solid daily surface, nothing that makes the archive a working knowledge base. 2 3 8