Team & People
Business Chat Etiquette: Your Own Rules for Replies, Mentions, and Channels
Intermediate | 1 whiteboard page · Task board: 4 columns (5 parent tasks, 13 subtasks)
Intermediate: Method names appear, but the whiteboard explains the key points. Use the examples as a guide and fill it in, thinking it through for your own situation.
New hires who freeze before hitting send in Slack or Teams use the business chat etiquette template to set their own rules for reply times, mentions, and when to call instead of chat. The whiteboard holds the team chat rules, a matrix that picks the channel by urgency and audience size, opening lines for requests, questions, updates, and nudges, a pre-send check, and a KPT retrospective. The task board has four columns - stuck moments, drafting a rule, trying it out, and locked in - and starts with 5 parent tasks and 13 subtasks, from the audit through the two-week review, all not started. Turning one hesitation into one rule at a time means that after two weeks you decide chat or call in three seconds and stop losing minutes in front of the send button.
Once you have a free account, you can copy this template from the marketplace
Whiteboard preview
Read the whiteboard text as plain text
Business Chat Etiquette
How to use: 1. Ask about the team rules 2. Pick the channel on the matrix 3. Make the opening lines your own 4. Run a KPT review in two weeks
1. Your Team Rules (who, when, and what counts as read)
- Where you want to be in two weeks No more freezing before you send. Pick the channel in three seconds and fill in a template.
- Confirmed with a senior teammate 1. All-hands mentions are for outages and same-day schedule changes only 2. Work hours are 9 to 5, and anything later counts as the next business day 3. An emoji reaction is a fine substitute for a read receipt
- Still undecided - Does a note to the director go by chat, or does it need email? - Do requests to another team go by DM, channel, or email?
- What the team actually does Channel posts come back in about two hours, DMs in twenty minutes Requests with the ask and the deadline on line one come back faster
2. Choosing the Channel (urgency vs. audience size)
Vertical axis: Urgency (top = needs action today / bottom = can wait) / Horizontal axis: Audience size (left = one person / right = the whole team)
- Call first, then post A one-to-one item that needs a decision within thirty minutes. Call first, then leave what you agreed in a three-line DM.
- Post once to everyone An item that meets the all-hands rule from section 1. Post it a single time, and keep every update in the same thread.
- DM it and wait You only need one person to confirm. Assume it will not come back right away, say when you need it by, and switch to other work while you wait.
- Put it in the channel Notes and status updates that people only need to read. Leave it in the channel and skip the individual mentions.
3. Opening Lines by Situation (use them as is, then make them yours)
| Making a request | Asking for input | Sharing an update | Following up | |
|---|---|---|---|---|
| Opening line | Quick ask - could you review the quote? Anything back by 5 p.m. on the 25th would help. | I could use a second opinion. I am torn between option A and option B. Do you have ten minutes today? | Sharing for visibility, no reply needed. Here are the decisions from today's call with Acme. | Following up on the quote I asked about on the 18th. Even a rough sense of when you can look at it would help. |
| Always include | The deadline (date and time) What done looks like (who gets what) A past example to work from | The options and the one you favor, with your reasoning When you need the decision by How far you want them to weigh in | Whether a reply is needed (say so if it is not) Who actually needs to read it The date, if there is a deadline | The date you first asked Your deadline, and what breaks if it slips A fallback (tomorrow morning still works) |
| Common mistakes | Sending ASAP and nothing else. Nobody knows the deadline, so you end up waiting. | Opening with Got a minute? and stopping there. They brace for bad news while they wait. | Dropping a link to the notes with no message. Nobody knows what was decided, so nobody opens it. | Sending Any update? and nothing else. It reads as blame, and the next ask gets harder. |
4. Before You Hit Send (recipients and timing)
- Reread the recipient before you send. When in doubt, go direct
- If you finish writing after hours, schedule it for the next morning
- Never put judgments about people in writing. Say it face to face
5. Mistakes in How You Split and Group
- Firing off five one-line messages and five notifications
- Packing five requests into one long message and getting an answer to the first
- Continuing a new topic in an old thread so nobody can find it later
- Pasting a screenshot without saying what to look at
6. Reading the Room on Emoji
- Skip them on a first message to a client or a director
- Matching how many the other person uses is the safest bet
- A thumbs-up or a check reads more clearly than a face
- Never add them to an apology or a no
7. Retrospective Every Two Weeks (KPT)
Keep (what to continue)
- When I cannot answer yet, I reply first with I will come back to you by five
- Putting the ask and the deadline on line one cut the follow-up questions
Problem (what did not work)
- I talked myself into urgent three times and sent after hours instead of scheduling
- The pre-send check is the first thing I skip when I am rushed
Try (what to test next)
- Stop DMing other teams and post in their channel instead
- Cut the check from three items down to one, the recipient
Task board contents
Stuck moments 18 items
Audit how you chat
Before you fix your habits, make it visible where you hesitate. Everything you list here becomes the raw material for your rules.
List your channels
Write on one page what you use chat, email, phone, hallway talk, and meetings for.
Log 5 stuck moments
Take five moments from the past week where your hand stopped over the send button and card them.
Ask about team norms
Ask a senior teammate what justifies an all-hands mention and how after-hours messages are handled.
Choose your channel
Most hesitation comes down to whether chat is the right place at all. Two axes - urgency and audience size - decide it for you.
Plot your 5 cases
Place the five moments you logged in the four quadrants and see where they cluster.
Set the call trigger
Put a number on the condition: three round trips with no decision, or a call needed by end of day.
Limit @channel use
An all-hands mention stops everyone at once, so narrow it to exactly two situations.
Set your reply times
Blaming yourself for not replying instantly will not last. Say up front how fast you answer, and change how people wait.
Post your reply time
Pick a target you can say out loud, such as two hours normally and thirty minutes for an urgent mention.
Set after-hours rule
Decide when you answer messages that land outside work hours, and what you write when you send at night.
Draft a holding line
Keep one stock line ready, such as I will check and come back to you by five.
Draft your openers
Composing from scratch every time is what eats the minutes. Build an opener for requests, questions, updates, and nudges, then just fill it in.
Template your asks
Put the ask, the deadline, and what done looks like on line one, so the first line alone is enough to act on.
Add two more openers
For questions, lead with the options and the one you favor; for nudges, lead with the date you asked and a fallback.
Review in two weeks
A rule you only decided is forgotten within a week. Take stock with KPT after two weeks and move only what worked into locked in.
Count what stuck
Count the cards you moved from trying it out to locked in, and call three of them a win.
Fix rules that fail
When a rule breaks, suspect the condition rather than your willpower, and retry it one notch looser.
