Skip to content
Bullpen

Team chat etiquette: seven rules a remote team can actually keep

Bullpen · · 4 min read

Team chat etiquette is not about emoji or tone. It is about making sure the right person sees the message, can answer it without a follow-up, and can find the answer again next month.

Here are seven rules that cover most of it. None of them needs a policy document.

The usual way

Most teams never write their chat rules down. People copy whatever the first few colleagues did.

  • "Hi" on its own. Then a wait. Then the actual question, ten minutes later.
  • Questions in DMs. The answer helps one person, and the next person asks again.
  • Everyone tagged. @channel for something three people needed to know.
  • Long threads that never close. Forty replies, and nobody is sure what was decided.
  • Decisions made on a call. The outcome lives in whoever was there.

Each habit is small. Together they make chat feel noisy and unreliable, so people start ignoring it.

Seven rules for team chat

  1. Ask the whole question in the first message. Skip the lone "hi" or "got a sec?". Write what you need, what you already tried, and when you need it by. The other person can answer in one go.
  2. Post in the channel, not a DM, when others might need the answer. A DM is for something private. Anything about the work goes where the work lives, so the answer is there for the next person.
  3. Reply in the thread. Keep a topic in one thread so the channel stays readable and the whole discussion sits in one place.
  4. Tag people for a reason. Mention the one or two people who need to act. Save whole-channel mentions for things everyone truly needs to see today.
  5. Say when you need an answer. "Today", "by Friday", or "whenever" removes the guessing, and lets people choose what to read first.
  6. Move to voice when a thread goes in circles. If ten replies have not settled it, talk it out for five minutes. Then post the outcome back in the thread in one line.
  7. Close the loop in writing. When something is decided, write the decision where the question was asked. Chat is only useful later if the outcome is there to find.

Rules 6 and 7 are the ones teams skip most, because the call happens somewhere else and nobody wants to write the summary.

How Bullpen fits

Bullpen is team chat with walk-in voice rooms and AI helpers on the roster, and it is set up so the good habits take the fewest steps.

Voice sits next to the channel. Each channel has a walk-in voice room that stays open. When a thread stalls, someone says "in the room" and whoever is free joins. No invite, no link to paste. Walk-in voice rooms at work covers how the rooms work day to day.

The summary writes itself. When people talk in the room, Wren posts the notes and action items back to that channel. Rule 7 happens without anyone volunteering to type it up. Recaps that land in the channel goes into that in more detail.

Old answers are easy to find. Ask Scout what was decided, and the answer comes back in the thread with a link to the message it came from. That only works when people followed rule 2 and posted in the channel. When DMs hide the decision explains why that matters.

Deadlines get a reminder. Mention Nix in the thread where someone promised something by a day, and the reminder lands in that same channel when the day comes. How to keep track of follow-ups in team chat shows the routine.

Start with one rule this week

Pin rule 1 in your main channel, and ask everyone to put the whole question in the first message for one week.

Start free to set up a bullpen where the conversation, the call, and the decision all land in the same channel.

All posts