Production communication

The thread, filed with the job.

Nobody is going to move their client onto a new chat app, so we do not ask. Link the Gmail thread, the Slack channel and the Chat space to the project, then read and reply to all of it from the job it belongs to.

No credit card needed. Set up in minutes.

The problem

The job's real record is scattered across an inbox, two Slack channels and a text thread. Finding 'the email where they approved the budget' means twenty minutes of searching three apps, and it was sent to your colleague anyway.

01Link the conversations

Every conversation about the job, on the job.

Nobody is moving their client onto a new chat app. So link the Gmail thread, the Slack channel and the Google Chat space to the project they are about, and they all appear in one place, with unread counts, without anything leaving where it lives.

  • Gmail, Slack and Google Chat

    Connect once, then link any thread, channel or space to a project.

  • Projects, clients and deals

    Conversations link to accounts and deals as well, not just projects.

  • Unread counts

    Each conversation shows what is new, and the badge reaches the dashboard.

  • Nothing moves

    The mail stays in Gmail and the messages stay in Slack. The app reads them where they are.

02Read and reply

Reads like Gmail. Replies from the job.

Email looks like email: earlier messages fold away, the latest one is open, and replying is a card that sends from your own Gmail and stays in the same thread. A rough draft can be polished in one click, and you read it before anything is sent.

  • Familiar on purpose

    Gmail threads look like Gmail and Slack looks like Slack, so you always know where you are.

  • Reply from your Gmail

    The reply goes from your address and lands in the same thread in Gmail.

  • Polish, shorten, warm up, firm up

    Rewrite a draft in one click. Nothing is sent until you press Send, and Undo puts your words back.

  • Attach from anywhere

    Files from your device, from the project's assets, or from Google Drive.

03Attachments go to work

Every file goes where it belongs.

An attachment is not the end of the story. File a contract into the project's documents, a photo into the asset library, and an invoice straight into the budget, where it is read and turned into a cost for you to check.

  • Add to assets

    Images and video go into the project's library, one click from the email.

  • Add to documents

    Permits, specs and contracts are filed with who sent them and when.

  • Log as a cost

    An emailed invoice becomes a cost, prefilled from the document for you to confirm.

  • Big files as Drive links

    A Drive file too big for Gmail is sent as a link, and you are warned if it is not shared yet.

  • Honest size limits

    Limits are explained before you press Send, not after the email fails.

04Slack and Chat

The channel, without switching apps.

Slack channels and Google Chat spaces read the way they do in their own apps: flat messages, names and times on one line. Post into the channel from the project, and the message lands in Slack for everyone else.

  • Read the channel

    Messages appear in order, looking like the app they came from.

  • Post from the project

    Write in the project and it posts to the real Slack channel or Chat space.

  • Polish works here too

    The same one-click rewrite is in every composer.

05Every job at once

Every conversation, every job, one page.

The studio-wide communication page groups every linked conversation by the job it belongs to, so a producer can see what is waiting across all of them. Filter to one app and the choice follows you from page to page.

  • Grouped by job

    Conversations sit under the project, client or lead they are linked to.

  • Filter by app

    Show only email, only Slack or only Chat, and the filter is remembered.

  • Relationship history

    Email linked to a client rolls into that account's timeline by itself.

The difference

Connect, don't replace.

Every 'all-in-one' tool fails the same way: it asks your client to change how they communicate, and they will not. Studio Flows leaves every conversation where it lives and pulls the reading and the replying into the job, which is the part you actually needed.

  • Zero behavior change asked of clients, agencies or crew
  • The job's record assembles itself from where work already happens
  • Leave anytime and every thread is still exactly where it always was
Gmail thread2
Slack channel2
Chat space2

Bright Water · Communication

Read and reply from the job. Nothing moves.

Three conversations from different tools filing into one project.

More it handles

Client and lead threads

Conversations link to accounts and deals too, not just projects.

CRM auto-logging

Linked email rolls into the account's relationship timeline by itself.

Visual attachments

Attachment cards with previews, not a paperclip and a prayer.

Size limits, honestly

Caps are enforced where they exist and explained before you hit send.

Notifications

The unread badge reaches the dashboard, per project.

Nothing moves

The mail stays in Gmail, the messages stay in Slack. We connect, we never copy.

Run your next job in Studio Flows.

Your first project is free, with no card and no countdown.

Start free

No credit card needed. Set up in minutes.