Designing channels
- By topic, not by person. A channel per client or per project outlives the people in it.
- Fewer than you think. A channel with two messages a month trains people not to look at channels.
- Public by default. A private channel is invisible to search for everybody else, which is exactly the knowledge loss a shared tool is supposed to prevent.
- One channel for the rollout. During onboarding, a single place for questions is worth more than a tidy structure.
Threads are the mechanism that keeps a busy channel readable. The rule that works is simple: a reply is fine in the channel, a conversation goes in a thread.
The assistant
An assistant can be invoked inside a conversation to summarise a thread, draft a reply, or answer a question with the thread as context. It reads the conversation it is invoked in and nothing else — not other channels, not direct messages, not other modules.
#delivery — thread
Client wants the launch moved a week earlier.
That collides with the content migration. We would need to cut the blog import.
/summarise
The client has asked to move launch forward by a week. The blocker is content migration; bringing the date forward would require dropping the blog import. No decision has been made and nobody has been asked to confirm with the client.
Every invocation costs something, and the total is visible per module in Admin → AI usage and in Chat's own usage screen. It is not a large number for most teams, and it is worth knowing where to look before it is.
It reads a conversation. It does not read the ledger, the pipeline or the project. If somebody in the thread stated a figure wrongly, the summary will repeat it. For numbers, go to the module that owns them.
What this does not do
The assistant sees one conversation, not your whole history.
Messages send when you send them.
An edited message shows as edited; previous versions are not kept.
Reactions are a fixed set.
Questions
Can the assistant read a whole channel?
No — the thread it is invoked in.
Can we turn the assistant off?
Yes, per organisation in the module's settings.
Are private channels visible to admins?
They are not exposed in the product interface.