Studio Chat
Keep conversation attached to the cue it's about, instead of scattered across email and messaging apps.
Conversation next to the work
Studio Chat replaces the email and messaging threads that usually orbit a score. It slides out over whatever you're doing, so you don't leave the cue to talk about it.
- Channels per project — only members of that project see them.
- A thread on every cue, so notes and revision decisions stay pinned to the cue.
- Direct messages for the quieter conversations.
Mentions, cue refs and timecodes
- @ a teammate to notify them.
- Reference a cue by number and it becomes a link to that cue.
- Paste a timecode and clicking it jumps the player to that moment.
The timecode one matters more than it sounds. "The brass is late" is an argument; a timecode that jumps everyone to the same bar is a decision.
Raising something about a specific cue
- 1
Open the cue and use its own thread.
Not a general channel — the thread is attached to the cue, so the conversation is still findable from the cue later.
- 2
Paste the timecode you mean.
It becomes clickable, so everyone lands on the same moment instead of describing it.
- 3
@ the person who needs to act.
A note nobody is tagged on is a note nobody owns.
Finding conversations again
Cue threads are grouped in the sidebar by project, then by reel or episode, so a thread is where the cue is rather than somewhere in a global scroll. Unread counts and mention badges surface the ones that actually need you.
Common questions
Should notes about a cue go in chat or on the cue?
Use the cue's own thread — it is chat, but attached to the cue. That way the conversation is still findable from the cue months later instead of buried in a general channel.
Can directors see our chat?
No. Channels are visible only to members of that project. Someone reviewing through a link is not a member and sees only what the link was for.
Is it real-time?
Yes — messages, typing indicators and unread counts update live.
What happens to messages I send while offline?
They're held and sent when you reconnect. See the offline topic for how that works and where to check on it.