Remote Communication Mistakes Agencies Make (and How to Fix Them)
According to Project.co's annual survey, 66% of people have stopped working with a company because of poor communication. Not because of quality. Not because of price. Communication.
For agencies, this hits harder than most businesses. You are communicating on two fronts at the same time: coordinating your internal team across projects and timezones, while keeping external clients informed and confident. Most remote communication advice is written for single-company teams. It ignores the client side entirely.
This article covers 8 remote communication mistakes agencies make, each with a specific fix you can set up this week. The fixes draw from real frameworks used by remote-first companies, and from what we practice at Rock.
"All of that context switching back and forth significantly reduces cognitive capacity and makes it very difficult to produce value with your brain at anywhere near your capabilities." - Cal Newport, Author and Professor at Georgetown University, from an interview with Fortune
The 8 Mistakes at a Glance
- Messages with no clear action - Lead with the ask, not the context
- Meetings to avoid writing - Share the agenda 24-48 hours before or cancel
- No single source of truth - One workspace where clients see the task board
- "Urgent" is a feeling, not a definition - P1/P2/P3 framework in your contract
- Feedback without context - No feedback without a "because"
- Operating in the dark or drowning clients - Replace updates with visible progress
- Decisions dying in chat - Name a decision owner in every request
- Invisible communication patterns - Audit quarterly or automate with AI
1. Every Message Is a Wall of Text with No Clear Action
Long messages are not the problem. Messages that do not tell the reader what to do next are. A 4-paragraph project update without a question or deadline just sits there. The client reads it, does not know what they need to do, and does not respond. Two days later your PM follows up: "did you see my message?"
According to Grammarly's 2024 State of Business Communication report, US businesses lose $1.2 trillion per year to poor communication. A lot of that is messages that go nowhere because the action was unclear.
The fix: Lead with the ask, not the context. Clients skim. Agency owners skim. If the action is buried after 3 paragraphs, they stop reading before they reach it.
Copyable message structure: [Announcement or ask first] + [Timeline] + [Context for those who want it]
Example: "We need your direction on the homepage wireframes by Thursday. Three options are in the task board. Option B tested best against the brief, so we will move forward with that one if we do not hear back. Here is a quick summary of each direction: [context]."
In Rock, you can turn a chat message into a tracked task with Tap to Organize. The ask becomes an assigned task with a deadline instead of a message that scrolls away.
2. Defaulting to Meetings Because Writing Is Harder
Meetings feel productive. Writing a clear async message takes effort. So teams default to "let us hop on a call" for things that do not need real-time discussion. Research from Atlassian found that US companies waste $399 billion per year on unnecessary meetings, and 62% of meetings have no stated goal.
What we do at Rock: We share a meeting agenda 24-48 hours before every meeting. At the start of the call, we ask if everyone has read through it. If not: for short agendas, we give 5 minutes to read. For longer ones, we reschedule. This sounds strict but it saves more time than it costs. People stop showing up unprepared once they know the standard.
The decision tree is simple. If informing: send a written update. If deciding: use a decision template (see mistake #7). If brainstorming or building a relationship: meet.
Other remote-first companies agree. Atlassian published a "Think Before You Sync" framework with 5 questions: Is it urgent? What is the goal? How many people? Will one person talk most of the time? How complex? Doist takes it further with "flipped meetings": all context is pre-shared in a thread, attendees read and comment before the call, and the meeting itself covers only unresolved points. A 60-minute meeting becomes 20.
3. No Single Source of Truth for Project Status
The client asks "where does the project stand?" Your PM checks the chat, then email, then the task board, then asks the designer. 15 minutes later they piece together an answer. This is the "chase loop": the agency chases the client for approvals, the client chases the agency for updates, and nobody has one place to look.
According to McKinsey, knowledge workers spend 28% of their workweek on email and another 20% searching for information across tools. That is nearly half the week spent finding things instead of making things.
The fix: Pick one place where project status lives and make it visible to both your team and the client. Not a spreadsheet you update manually. A live workspace where tasks, chat, and files coexist.
This is Rock's core design. Every space has chat, a task board, notes, and files in one view. The client can open the space and see what is in progress, what is blocked, and what is done without asking anyone. The chase loop breaks because the answer is already visible.
"But should internal tasks not be separate from client-visible ones?" Often, yes. In Rock you can run separate internal and client-facing spaces. The key: use @mentions to link a client task to an internal task across spaces. They are connected but the client only sees what is relevant to them.
The principle: If a client has to ask "what is the status?", your system is broken. The status should be visible before they think to ask.
4. Treating "Urgent" as a Feeling Instead of a Definition
When urgency is subjective, everything feels urgent. A client messages on Saturday about a font change. A developer drops their plans to fix it. Neither person is wrong because nobody agreed on what "urgent" means.
The fix: Define urgency levels in your project agreement and walk clients through them during onboarding.
Copyable urgency framework:
- P1 - Critical: Blocking revenue or launch. Site down, payment broken, security issue. Response within 1 business hour.
- P2 - High: Blocking the team's current work. A decision or asset needed to continue. Response within 4 business hours.
- P3 - Normal: Everything else. Feedback, questions, non-blocking requests. Response within 1-2 business days.
When a client flags something as urgent, the framework gives you professional language: "Thanks for flagging this. Based on our agreement, this looks like a P3 since it is not blocking the launch. We will address it by [date]."
There is a bonus here. If a client needs something handled as P1 but it falls outside the original scope, that becomes an extra billable. The urgency framework doubles as scope protection. For more on setting response time expectations in contracts, see our guide on virtual communication practices.
5. Giving (and Accepting) Feedback Without Context
"Can you make the logo bigger?" is not feedback. It is an instruction without reasoning. Your designer makes it bigger. The client says "no, not like that." Two rounds wasted because nobody asked why.
This goes both ways. Agencies give vague feedback to freelancers. Clients give vague feedback to agencies. The fix is the same.
Copyable feedback format: [What to change] because [the reason]. [Reference].
Example from a client: "Can we make the header warmer? Because our audience is first-time parents and the current tone feels too corporate. Here is our Instagram as a reference for the tone we are going for."
Example from an agency: "We would recommend dropping the third section because analytics show 80% of visitors leave before reaching it. Here is a shorter layout that puts the CTA higher."
The rule: No feedback without a "because." If you cannot explain why, the feedback is not ready to give. This applies to both sides. Train your clients on this format during onboarding and it will save you dozens of revision rounds over time.
6. Either Operating in the Dark or Drowning Clients in Updates
Agencies fall into one of two traps. Some go quiet between deliverables and the client feels abandoned. Others send constant updates, FYI emails, and status pings until the client starts ignoring everything. Both are communication failures. One comes from neglect, the other from anxiety.
According to Harvard Business Review, collaboration consumes over 85% of most people's work weeks, up 50% over the past two decades. A large part of that is reactive communication: updates nobody asked for, meetings that could have been a message, and messages that could have been nothing.
The fix: Replace both extremes with visible progress. Instead of telling clients what is happening (over-communication) or forgetting to (under-communication), show them. A visual task board where clients can see what is in progress, what is done, and what is next.
This is where Rock makes a real difference. When the client has access to the project space and can see the task board at any time, you do not need to send proactive updates. The status is visible. You message when you actually need input. The client checks when they want to. Nobody drowns, nobody feels in the dark.
"The time spent by managers and employees in collaborative activities has ballooned by 50% or more over the past two decades." - Rob Cross, Reb Rebele, and Adam Grant, Harvard Business Review
The test: At the end of each month, look at your sent messages to a client. How many did the client ask for vs. how many were unsolicited? If more than a third were unsolicited, you are over-communicating. If the client has asked "what is the status?" more than twice, you are under-communicating.
7. Letting Decisions Die in Chat Threads
Someone asks a question in chat. Three people weigh in. The thread gets long. Nobody summarizes. Nobody decides. Three weeks later, someone asks the same question again.
According to Microsoft's Work Trend Index, the average employee spends 57% of their time communicating and only 43% creating. When decisions stall in chat, that ratio gets even worse because the same conversation happens multiple times.
The fix: Both the question and the answer need a clear format. The question needs to be directed to a specific person. The answer needs to come from a named decision maker.
Copyable decision request format:
- [What happened / context in 2-3 sentences]
- [Impact / why this matters now]
- [2-3 options with trade-offs]
- Decision needed by [date]
- Decision owner: [name]. If that is not you, please tag the right person.
The last line is key. If nobody is named as the decision maker, the thread becomes a discussion instead of a decision. Naming someone creates accountability.
In Rock, Tap to Organize converts a chat discussion into a note or task. When a thread produces a decision, one tap captures it so it does not scroll away. Set Aside lets you flag messages that need a decision later, so nothing falls through the cracks.
8. Missing the Communication Patterns You Cannot See Manually
Some communication failures are obvious: missed deadlines, angry clients, burned-out team members. But most problems are invisible until they compound. Who on your team is handling 80% of the client communication? Which projects have the longest response times? Where do decisions get stuck most often?
According to the same HBR study, just 3-5% of employees handle 20-35% of all value-adding collaboration in most organizations. If you do not know who that is on your team, they are probably burning out right now.
The manual approach (quarterly, 30 minutes):
- Pull meeting count per client. Trending up means scope creep or trust issues. Trending down means healthy or disengaged. Check which.
- Check response times. How many client messages sat unanswered for 24+ hours?
- Count stalled decisions. How many times did someone ask "did we ever decide on X?"
- Ask your team: what is one communication thing that is working and one that is not?
The automated approach: If you use Rock's API, you can connect an AI (ChatGPT, Claude, Gemini) as a bot in your space. Have it analyze communication patterns across your projects: who is overloaded, where response times lag, which projects have the most stalled decisions. The bot reads everything in the space and gives you recommendations specific to your team. No manual audit needed.
What to change based on results: If meetings are climbing, propose async reports. If decisions stall, implement the decision template from mistake #7. If one person handles most communication, redistribute before they burn out.
Final Thoughts
These 8 mistakes share a root cause: agencies build communication habits for convenience, not for outcomes. A meeting is easier than writing clearly. Copying a client on everything is easier than deciding what they need to see. Leaving "urgent" undefined is easier than having the conversation upfront.
You do not need to fix all 8 at once. Start with the one your team complains about most. Set it up properly, document it, and review it next quarter. The templates and frameworks in this article are meant to be copied and adapted, not followed as rigid rules.
"Better remote communication is not about sending more messages. It is about making the right information visible at the right time, so nobody has to chase it." - Nicolaas Spijker, Marketing Expert
It comes down to clear rules, predictable schedules, and visible progress.
__________________________________________________
Want to bring your agency's messaging, tasks, and client collaboration into one workspace? Rock combines chat, task boards, notes, and files in every project space. Clients join directly. One flat price, unlimited users. Get started for free.
