Communication Norms To Set With Your Virtual Assistant

Most virtual assistant relationships fail on communication, not skill. Set these norms in the first week and revisit them monthly.

Why Norms Matter

Every team has communication norms, whether or not anyone wrote them down. Without an agreement, a message sent to the wrong channel gets missed, a “quick call” interrupts deep work, and silence gets misread as disagreement. On a remote team spread across time zones, those misunderstandings cost days.

Written norms turn guesswork into habit.

What To Define

Channels

Decide which tool is for which purpose.

Response Times

• Urgent: within one hour during working hours

• Normal: within four hours or same business day

• Low priority: within 24 hours

Working Hours And Time Zones

List each person’s hours in one time zone and mark the overlap. Note holidays too. See time zones and scheduling.

Meeting Rules

Send an agenda a day ahead, start on time, record for absent members, and send notes and action items within an hour.

Decision Records

Choose one place where decisions are written, such as a shared document or channel. When something is decided in a call, someone posts the summary.

How To Write Your Guide

Keep it to one page:

1. Our channels and what each is for

2. Response-time expectations

3. Our working hours and holidays

4. How we run meetings

5. How we escalate problems

6. Where decisions live

Share it on day one and revisit it every quarter.

Habits That Make Norms Stick

• Lead by example. Follow the rules yourself.

• Reward clear written updates.

• Gently redirect messages sent to the wrong place.

• Ask for feedback: “What is one thing we could change to communicate better?”

Special Cases

Customer-Facing Communication

Add rules for tone, approved templates, and escalation. Globaltize’s pages on the live chat support agent and customer support specialist roles show what structured support communication involves.

Sensitive Conversations

Use video or voice for difficult feedback. Text loses tone.

Common Mistakes

• Using too many tools

• Expecting instant replies across time zones

• Making decisions in private threads

• Never revisiting the rules

A Real-World Example

A remote team of five spread across three countries kept missing each other. Urgent questions sat in email while quick chats were used for big decisions. They wrote a one-page guide: chat for quick things, email for records, video for anything hard. Response times were set at two hours for chat and one day for email. Missed messages dropped almost to zero.

The guide took an hour to write. It saved hours every week.

A Quick Checklist Before You Start

Before you write your norms, gather these inputs:

• Every channel your team uses today

• Working hours for each person

• The types of messages that cause confusion

• How decisions are recorded now

• One person to own the guide

Read more on asynchronous communication or how to manage a remote assistant.

Questions Owners Ask

How long should a norms guide be?

One page. If it is longer, people will not read it.

Who should write it?

The manager, with input from the team. Then review it together.

Related Reading

• Best communication tools

• Async communication guide

• Daily report template

Next Steps

Draft your one-page guide today and tell us who you need. For a free reference, GitLab’s remote work handbook is one of the most thorough public guides to communication in all-remote teams.