The Meetings That Should Be Emails, and the Emails That Should Be Calls, in Agency Work

Every brand and agency team has a version of the same story. A project that should have taken six weeks took ten. When you trace it back, the delay wasn't creative. It wasn't budget. 

It was a status call that should have been a Slack message, a feedback email that generated more questions than it answered, and a decision that got stuck in a thread when it needed a twenty-minute call to resolve.

Format mismatches are one of the most consistent sources of friction in agency relationships, and one of the least discussed. Everyone agrees that communication is important. Almost nobody agrees upfront on what kind of communication belongs where. The result is teams that are simultaneously over-meeting and under-aligned, buried in email threads that never quite move anything forward while also sitting in calls that didn't need to happen.

The fix isn't fewer meetings or shorter emails. It's matching the format to the job.

Why Agency Work Is Overrun With Meetings and Never-Ending Email Threads

Agency relationships are structurally prone to communication overload, and understanding why helps clarify what to do about it.

Most agency engagements involve multiple stakeholders on both sides, across multiple workstreams, with different levels of context and different preferences for how they like to communicate.

The default response to that complexity is more touchpoints: more calls to make sure everyone's aligned, more email threads to create a paper trail, more check-ins to feel like things are moving.

The problem is that frequency isn't the same as clarity. A weekly status call where neither side prepared an agenda doesn't create alignment, it creates the feeling of alignment while the actual decisions, blockers and direction changes pile up between calls. 

An email thread where feedback arrives across three separate messages from four different stakeholders doesn't move the project forward, it gives the agency a parsing problem to solve before they can do any actual work.

The underlying issue is that most teams default to the format they're most comfortable with rather than the format the situation requires. Comfort drives the meeting. Caution drives the email chain. Neither drives the project.

The Meetings That Should Be Emails (Status, Recaps and Simple Decisions)

The easiest category to fix is also the most common source of wasted time: meetings that exist primarily to share information that could have been read.

Status Updates and Weekly Recaps

If the primary purpose of a meeting is to report on what happened since the last meeting, it should be a written update. A well-formatted status email (what's done, what's in progress, what's blocked, what's next) takes ten minutes to write and two minutes to read. The same information delivered verbally in a call takes thirty minutes and is harder to reference later.

Status calls feel useful because they're synchronous and social. But the synchronous part isn't adding value if there's nothing to discuss. Save the live time for conversations that genuinely require back-and-forth. Let the status live in writing where it can be skimmed, searched and referenced without anyone having to take notes.

Simple Decisions With Enough Context

Not every decision needs a meeting. If a question has a clear answer that doesn't require significant negotiation or nuance, it belongs in an email or a Slack message with the relevant context attached. "Can we move the deliverable deadline from Thursday to Friday?" is not a call. "Here are two options for the campaign direction, and here's our recommendation" is not a call if the brand team can review and respond asynchronously.

A good test: if you can write the decision and its options in two paragraphs, and the response is likely a thumbs up or a clear preference, it's an email. If the response is likely to generate questions that generate more questions, it might be a call. 

Post-Meeting Recaps

The recap email that covers what was discussed on a call that just happened is one of the great redundancies of agency work. If the call had a clear agenda and someone took notes, the recap is the notes. If it didn't have a clear agenda, the recap often reveals how little was decided which is a sign the meeting itself was the problem.

The Emails That Should Be Calls (Nuance, Feedback and Hard Tradeoffs)

The opposite problem is equally common and often more damaging: situations that genuinely require real conversation getting pushed into email because it feels safer or more efficient.

Creative Feedback

Creative feedback sent over email almost always creates more work than it resolves. Written feedback (even when well-intentioned) tends to be interpreted differently than it was meant. "This doesn't feel quite right" means something specific to the person writing it and something different to the person receiving it. The creative team either makes changes based on their interpretation or asks clarifying questions, which generates another email, which generates another round of interpretation.

A fifteen-minute call where the brand team walks through what they're reacting to (and why), and the creative team can ask questions in real time usually resolves what an email thread drags out across days. If the feedback is substantive enough to affect creative direction, it needs a call. Email is for confirming that changes were made correctly, not for making them.

Sensitive Conversations and Course Corrections

If the news is difficult — a missed deadline, a budget question, a concern about whether the work is heading in the right direction it belongs in a call, not an email. Written communication strips tone in ways that make difficult conversations more fraught than they need to be. A concern delivered in an email can read as an accusation. The same concern raised on a call, with the right tone and space for response, is a conversation.

This doesn't mean avoiding hard topics in writing entirely. It means raising them live first, then following up in writing to confirm what was discussed and agreed.

Decisions With Real Tradeoffs

When a decision involves competing priorities, significant budget implications or a genuine disagreement about direction, email is the wrong tool. These conversations need live back-and-forth where both sides can hear how the other is reasoning, respond to what's being said and work toward something neither side could have arrived at in writing.

The tell is usually the email thread itself. When a written exchange has gone three rounds without reaching resolution, someone should have picked up the phone two rounds ago.

How to Use Async Docs, Looms and Clear Agendas So Every Touchpoint Has a Job

Between the meeting and the email sits a genuinely useful middle ground that most agency relationships underuse: async communication that's richer than text but doesn't require everyone to be available at the same time.

Async Docs for Feedback and Briefs

A shared document where feedback can be left, responded to and resolved in context is often better than either a call or an email for creative review cycles. Both sides can work in their own time, the thread of the conversation is visible to everyone and nothing gets lost in translation between what was said on a call and what made it into the notes.

This works especially well for brief revisions, copy edits and structured creative feedback where the comments can live next to the specific thing they're commenting on. It doesn't work as well for emotional feedback, big-picture direction changes or anything where tone and nuance matter enough to require a real conversation.

Looms for Complex Walkthroughs

A two-minute Loom that walks through a question, shows the relevant context on screen and explains the reasoning is often more useful than three paragraphs of email trying to describe the same thing. It's faster to record than to write, faster to watch than to read and easier to understand because it shows rather than describes.

Looms work well for: explaining a complex piece of feedback, walking through a creative direction, showing a technical issue, or giving context that's hard to convey in text. They don't replace calls for conversations that need two-way interaction.

Clear Agendas That Give Every Meeting a Job

The meeting that needs to happen is fine, but what isn't is a meeting that no one prepared for. Every call with an agency should have a stated purpose, an agenda shared in advance and an expected outcome. If you can't articulate what decision will be made or what will be different after the call, the call probably doesn't need to happen yet.

Agendas don't need to be elaborate. "We're reviewing the three creative concepts and deciding which direction to develop" is a complete agenda. It tells everyone what to prepare, focuses the conversation and makes it easy to know when the call has accomplished what it set out to do.

The Communication Traps That Slow Down Creative and Marketing Projects

Even teams with good intentions fall into patterns that create friction without realizing it. A few are especially common in agency work.

The Approval That Lives Nowhere

A decision gets made on a call. Someone says they'll follow up. The follow-up email is vague. Two weeks later, the agency is working from what they thought was decided and the brand team is working from what they said in the follow-up email. This happens constantly, and it's almost always the result of not having a clear system for where decisions live and who owns confirming them in writing.

Feedback From Multiple Directions

The agency receives creative feedback from the brand's marketing lead. Then from the CMO. Then from someone in sales who saw it in a hallway. Each set of feedback is sent separately, sometimes contradicting the others. The agency now has a coordination problem, not a creative one. 

Consolidated feedback — one document, one person responsible for collecting input before it goes to the agency is one of the highest-leverage communication norms a brand team can establish.

The Thread That Never Ends

A simple question gets sent by email. The response raises another question. Six exchanges later, the original question is buried and no one is sure what's been decided.

If a reply requires more than two sentences, the conversation probably needs to move to a call or an async doc where the full context can be visible.

Setting Communication Norms With Your Agencies So Work Moves Faster

The most effective agency relationships establish communication norms at the start of the engagement, not after the first avoidable delay.

This doesn't require a lengthy protocol document, but a direct conversation at kickoff about how the two teams will work together: what goes in email, what warrants a call, how feedback gets consolidated, what the expected response time is for different types of communication and who the primary point of contact is on each side.

When starting a new agency project, these questions are worth addressing explicitly before the first deliverable is due. Assumptions about communication style are one of the most common sources of early friction in agency relationships (and one of the easiest to preempt with a short conversation at the beginning).

A useful set of questions to cover at kickoff:

• What's the fastest way to reach you for something urgent?
• What's the turnaround expectation on email?
• Who needs to be on calls, and who can be kept to email updates?
• How will we consolidate feedback before it comes to you?
• What's the preferred format for creative direction changes?

None of these are complicated questions, but teams that answer them at the start work faster than teams that discover the answers through friction.

How to Use Breef to Find Agencies With Strong Ops and Communication Practices Built In

Communication problems in agency relationships aren't always the brand team's fault. Some agencies are simply better operators than others; clearer in how they run projects, more proactive about flagging blockers, better at distinguishing the communication that needs a call from the kind that can live in a doc.

Breef helps brands find vetted agencies that work well, not just agencies that present well. The pitch process on Breef is structured to surface how agencies think and communicate, not just what they've produced. A brief that clearly describes how you like to work gives agencies the opportunity to show whether they're a fit for your team's operating style before the engagement starts.

The brands with the smoothest agency relationships are usually the ones who screened for operational fit alongside creative fit from the beginning. Production quality is easy to evaluate from a portfolio. Communication style and project management discipline are harder (and they matter just as much once the work is underway).

Ready to find agencies that work as well as they create? Book a demo call with Breef and find partners who make the work feel easier, not harder.