Remote work etiquette is mostly about making life easy for people who can’t see you. Pick the right channel for each message, set clear expectations about response times, write updates that make sense without a meeting, run video calls with respect for everyone’s time, and plan around time zones. Teams rarely spell these norms out, so first-time remote workers learn them by making mistakes. This guide gives you the norms up front, with templates you can copy.
One rule overrides everything below: if your team has a written communication guide or handbook, read it in your first week and follow it.
Choose the right channel
Many communication problems in remote teams start with the wrong channel: a decision buried in a direct message, or a status update that should have been a written note instead of a meeting.
| Channel | Use it for | Avoid it for |
|---|---|---|
| Team chat (Slack, Teams) | Quick questions, coordination, and short announcements in the right channel | Decisions that need a permanent record and long debates |
| Clients and external partners, formal requests, and approvals | Fast back-and-forth inside your team | |
| Issue tracker, pull requests, docs | Decisions about the work, specs, and technical discussions | Social chat |
| Video or voice call | Sensitive feedback, conflict, brainstorming, and anything that has stalled in writing | Status updates that could be written |
| Phone call or paging | Real emergencies, like production being down | Anything that can wait a few hours |
A useful rule from GitLab’s communication handbook: if you’ve gone back and forth three times in writing, it’s time for a video call. The same handbook asks people to avoid direct messages and use public channels, so others can chime in, help, and learn from the answer.
Chat etiquette
- Ask your question in the first message. “Hi” followed by a wait forces the other person to sit there while you type. The short explainer at nohello.net is worth reading once. Greet and ask in the same message: “Hi [name], quick question: where do we keep the staging credentials?”
- Use threads. Reply in the thread, not the main channel, so conversations stay readable.
- Write one complete message, not five fragments. Each fragment can trigger a separate notification.
- State the urgency. “Not urgent, Thursday is fine” or “Blocking the release today” helps people prioritize.
- Use group mentions sparingly. Notifying an entire channel is for things that affect everyone now.
- Acknowledge with a reaction when you’ve seen a message but can’t answer yet, then follow up.
- Read messages charitably. Short replies are usually a sign of a busy person, not an annoyed one.
Set response-time expectations
Ask your manager or client how quickly they expect replies on each channel. If nobody has set norms, these defaults are reasonable starting points:
| Channel | Reasonable default |
|---|---|
| Chat, during your working hours | Within a few hours |
| Within one business day | |
| Review requests (pull requests, documents) | Within one business day, or say when you’ll get to it |
| Emergencies | Through the agreed phone or paging route, not chat |
When you can’t answer fully, buy time explicitly: “Got it. I’ll look at this after my 2 p.m. call.” That is better than a fast but careless answer or hours of silence.
Respect other people’s hours too. If you write outside a colleague’s working time, schedule the message for their morning or say “No need to reply until tomorrow.” Nobody should feel obliged to answer at midnight because you happened to be working.
Write async updates people can act on
Written updates replace the hallway conversations that tell an office team what’s going on. Keep them short, consistent, and full of links.
A daily or weekly update template
Update for [date]
Done: Shipped password reset flow (PR #482)
Next: Start on email verification; pairing with [teammate] on Thursday
Blocked: Need API keys for the SMS provider (@[name], by Wednesday?)
Risks: Verification may slip a day if keys arrive after Wednesday
Links: Ticket APP-311, design docA request template
Context: What I'm working on and why it matters now
Ask: The specific decision or help I need, and from whom
By when: The deadline, and what happens if we miss it
Tried so far: What I've already checked, so you don't repeat it
Options: A or B. I recommend A because ...The “Options” line matters most. A message that ends with a recommendation can be answered with “Yes, go with A.” A message that ends with “Thoughts?” usually turns into a meeting.
Video call etiquette
Before the call
- Ask whether it needs to be a meeting. GitLab’s guide to all-remote meetings starts with that question and recommends including an agenda link in every invite, ideally shared 72 hours ahead and at least 24 hours ahead.
- Test your audio and video a few minutes early, especially on a new device or app.
- Join on time. In a remote meeting, everyone waits in silence for the last person.
During the call
- Use a headset and mute yourself when you’re not speaking in larger calls.
- Follow your team’s camera norms. Having it on helps in small groups and with new colleagues. If you need it off, a quick “camera off today, bad connection” is enough.
- Use a quiet, tidy background or a blur, and avoid eating on camera.
- Use the raise-hand feature or chat to avoid talking over people, since audio lag makes interruptions worse.
- Don’t visibly multitask. People can tell when you’re typing elsewhere.
After the call
- Post a summary with decisions, action items, owners, and dates in the relevant channel or document.
- End on time, or a few minutes early so people can take a break before their next call.
Work across time zones
- Put your time zone and working hours in your profile and calendar so people can see when you’re available before they message you.
- Always write times with a time zone, and add UTC when the audience is mixed: “Let’s ship at 15:00 WIB (08:00 UTC).”
- Add your teammates’ zones to your calendar. Google Calendar, for example, can show secondary time zones and a world clock next to your own.
- Use UTC for recurring meetings that span regions. GitLab’s communication handbook recommends this so meeting times don’t move for others when daylight saving time changes your local clock.
- Share the pain. If a regular meeting is always early or late for one region, rotate the time or record it and collect input in writing.
- Hand off cleanly at the end of your day with a short note about what’s done and what’s waiting, so colleagues in later time zones can keep going.
Keep your status honest
Your status indicator is how a remote team knows whether to expect an answer. Keep it current and specific:
- “Focusing until 11:00, will reply after”
- “Lunch, back at 13:00”
- “Out sick today”
- “On leave until Monday, contact [colleague] for anything urgent”
Slack, for example, lets you set a status with an expiry, schedule statuses in advance, and pause notifications while a status is active. Your calendar is a status indicator too, so mark focus time and time off there.
Don’t keep your status “active” to look busy. Remote teams judge you on what you deliver and how reliably you communicate, not on a green dot.
Write things down where people will find them
- Record decisions in the ticket, pull request, or project document, not in a private chat.
- When you learn something the hard way, like a confusing setup step, update the documentation for the next person.
- Link to existing docs instead of re-explaining things in chat.
- Write clearly for colleagues who use English as a second language: short sentences, no idioms, and specific dates rather than “next Friday.”
Common first-month mistakes
- Struggling silently. If you’ve been stuck for more than an hour or two, ask, and share what you’ve already tried.
- Over-communicating to prove you’re working. Constant pings and extra meetings create noise. Regular, structured updates build more trust.
- Making decisions in direct messages. The rest of the team can’t see them, so they get repeated or contradicted later.
- Ignoring time zones when setting deadlines or scheduling calls.
- Treating every message as urgent, your own and other people’s.
Your next step
In your first week, ask your manager three questions: which channel to use for what, how fast replies are expected, and how to flag something urgent. Then send your first written update using the template above.
Etiquette covers how you communicate with others. For the habits that keep you productive and sane day to day, such as routines, focus time, and boundaries, read 10 habits for thriving in remote work. If you’re still interviewing, these same norms make a good impression; see our interview tips for your first remote job.