Crew talk, beside the job it is about.

Internal crew messaging only.

One thread, one crew

Only its participantsA conversation belongs to your company, and the people in it are the only ones who can read it.
A job on the threadA conversation can point at a job, so the talk and the record it is about stay together.
Unread you can trustYour own read position per conversation drives the count. A failed refresh keeps the last known number instead of showing zero.
Plain messagesText, an author, and a time. No attachments, no reactions, no threads inside threads.

Example workflowIllustrative composition of the shipped team conversation.

Reading and replying, without leaving the work.

The messenger opens over whatever page you are on, so answering a crew question never costs you the record you had open.

Step 1
Open it from anywhere
The Team button sits in the dashboard header on every page, and the command palette has an entry for it.
Step 2
See what is waiting
The launcher carries the true count of your unread conversations, and your newest unread ones each get their own row in the notification bell.
Step 3
Read the thread
A conversation opens on its most recent hundred messages, newest at the bottom, each one showing who wrote it and when.
Step 4
Reply, and clear it
Your reply posts to the same thread, and marking the conversation read clears it from your count.

Open a job, start the thread, and see who is still waiting on an answer.

Which conversations you can see depends on which ones you are in, and what a teammate can see depends on their own access.