The conversation stays attached to the work.
A channel per project, direct messages for everything else, and a daily log short enough that people actually read it.
A channel per project
Client work gets its own room, so the context is in one place when someone new picks it up six weeks later.
Ticket numbers become links
Type NW-104 and it resolves to the ticket, with its status. The thread and the board stop being two accounts of the same thing.
The daybook
One note a day: what you did, what is next, what is blocked. A crew across three time zones reads it instead of asking, and it becomes the record of the month.
A channel is a project
Open a channel and you get its chat, its board, its hours and its docs. The conversation does not live next to the work; it is part of the same room. Direct messages sit in the same rail for everything that is not about a project.
References resolve
Type a ticket id and it becomes a link carrying that ticket’s current status. Six weeks later the thread still reads correctly, because the status is read at display time rather than frozen into the message.
- Ticket ids link and show live status
- Attachments and screen recordings post inline
- The daily log channel, one note per person
- Readable by someone who joins later
The daybook
One log channel, one note a day: what you did, what is next, what is blocked. Across three time zones it replaces the standup, and it gives a client a record of the week that nobody had to write up separately.