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 Team Lead
Channels come in organisation, team, external and personal categories with permission controls over who can post or add people, and unified search spans messages, users, channels and departments with tags to narrow results. The word "threads" appears only where the AI-server page lists what an agent can reach, with nothing on how threads read for a human. I found no public information on mentions, reactions, file previews, search filters by person and date, or any documented history limit, which is exactly what decides whether the archive can answer an eighteen-month-old question. 2 3 8