In short
- Choose a meeting when you need real-time back-and-forth or the conversation carries emotion: conflict, negotiation, bad news, brainstorming.
- Choose a recorded video when you need to show something and the client can reply in writing.
- Choose email for anything that needs a record, and chat for quick facts and yes-or-no questions.
- The best client meetings often start with a short video sent the day before, so the call is about decisions, not explanations.
Use a meeting when the conversation needs live back-and-forth or carries emotion; use a video when you need to show something and the client can reply in writing; use email or chat for facts, dates and quick questions. That’s the whole rule for meeting or video in client work. The hybrid that often works best is a short video sent the day before the meeting.
Meeting or video: the short rule
Before you book a call or hit record, ask:
- Does it need a conversation, or a message? If the client’s answer will change what you say next, several times, that’s a conversation. Meet.
- Does it need to be seen? If you’d have to describe a screen, a design or a sequence of clicks in words, record a video.
- Does it need a record? If it’s a decision, a date or a list, write it. Even after a call or a video, put the outcome in writing.
Most client communication ends up in the middle: something to show, a question at the end, an answer that fits in a sentence. That’s a video with a written question underneath.
| Use | Live back-and-forth or emotion | Something to show | Needs a record |
|---|---|---|---|
| Call or meeting | ✓ | ~ sometimes | ~ write the outcome after |
| Recorded video | ✗ | ✓ | ~ write the question under the link |
| ✗ | ✗ | ✓ dates, decisions, lists | |
| Chat | ✗ | ✗ | ✗ quick facts only |
Call, video, email or chat: what each is good at
| Format | Best for | Weak at | Typical client example |
|---|---|---|---|
| Live call or meeting | Discussion, emotion, negotiation, building trust | Showing details, leaving a record, fitting calendars | Kickoff, a complaint, a scope negotiation |
| Recorded video | Showing and explaining, tone of voice, rewatching | Back-and-forth, quick yes or no | Design round two, a bug, a quote walkthrough |
| Decisions, dates, lists, anything to find later | Tone, anything visual | Confirming the launch date, sending the contract | |
| Chat | Quick facts, small questions, nudges | Long explanations, decisions that need a record | “Is the logo in the shared folder?” |
Common client situations, sorted
Here’s how the rule applies to the messages agencies and freelancers send every week.
| Situation | Best format | Why |
|---|---|---|
| First meeting with a new client | Call | Trust is built live; you also need to hear what they don’t say |
| Project kickoff | Call, with onboarding videos after | Meet the people, then let the logistics be rewatched |
| First concept presentation | Video, then a call if needed | The client sees it calmly first, reacts less on the spot |
| Design review, round two | Video | It’s mostly showing what changed |
| Weekly status | Video | One-way information plus one decision |
| Quote or proposal | Video, then a call if they want one | They can rewatch while deciding; the call handles questions |
| Bug report | Video | Seeing the steps beats any description |
| Missed deadline or other bad news | Call, then email | Bad news on video feels like hiding |
| Scope disagreement | Call | It’s a negotiation |
| Handover of a finished site | Video, sometimes with a short call | It will be rewatched for weeks |
| Confirming a date or a detail | Chat or email | It’s a fact |
The first concept presentation surprises people most. Recording it lets the client react in private before replying; our guide to presenting a design without a meeting shows how.
Signs a conversation needs to be live
Some conversations go wrong when they’re recorded, however good the video. Book a call when you notice any of these:
- Conflict. The client is unhappy, or you are. A video can’t hear the frustration and adjust.
- Negotiation. Price, scope, deadlines. Both sides need to respond to each other in real time.
- Bad news. A delay, a mistake, a budget overrun. Telling someone live shows respect, even if you follow up in writing.
- Brainstorming. Ideas build on each other. Taking turns by video slows that down to a crawl.
- Several people who disagree. If the client’s team is split, sending them a video gives each person time to dig in. Get them in one room.
- The third round of the same misunderstanding. If two messages haven’t fixed it, a third won’t.
- A new relationship. Early in a project, a little live time makes every later video land better.
Our guide on when not to send a video to a client goes deeper into these.
Signs a meeting should have been a video
The opposite mistake is just as common. A call is probably a waste of everyone’s time when:
- one person talks for most of it, sharing their screen;
- the agenda is “update” and nothing needs deciding;
- the client asks for the recording afterward because a colleague couldn’t join;
- you spend the first ten minutes finding a time that works;
- the outcome could be one yes-or-no answer.
A weekly status call is the classic example. Our guide on replacing it with a video status update shows how.
The hybrid: a video before the meeting
Many of the best client meetings start with a video. You record the explanation, the client watches it before the call, and the meeting is only about questions and decisions.
The day before
Record the explanation and send it
Walk through the design, the quote or the plan as you would at the start of the meeting. Add one line on what you'll decide together.
Start of the call
Their questions, not a recap
If they haven't watched it, that's fine: play the key minute together.
End of the call
The decision
Say it out loud and write it down for both of you.
Same day
A short recap
By email, or as a one-minute video, with what was agreed.
The message that goes with the video says what the call is for, so the client knows why it’s worth two minutes today.
Hi Sofia, two minutes on the launch plan before tomorrow’s call. There are two options; tomorrow we just need to pick one.
https://justrec.app/v/k3f9Qa
This works especially well for quotes, where the client may want to show the explanation to a partner before discussing price. Our guide to walking a client through a quote by video has the details.
And a video after the meeting
A recap video is useful when the call covered something visual and not everyone was there. Show the screen you discussed, say what was decided, and say what happens next. Two minutes is plenty. If the recap is only decisions and dates, an email is better.
Agree on the rules with your client
The decision gets easier when the client knows what to expect. At kickoff, say which things you’ll handle by call, which by video, and how fast you reply to each. Our async communication policy template gives you a starting point, and async video for agencies shows how a studio can set these rules internally.
For the full picture of recorded video in client work, read our guide to async video for client communication.
Frequently asked questions
When should I use a meeting instead of a video?
When the conversation needs real-time back-and-forth, or when emotions are involved: a complaint, a negotiation, bad news, a brainstorm, or a first meeting with a new client.
When is a video better than a meeting?
When you mostly need to show and explain something, and the client can answer in writing: a design round, a status update, a bug, a walkthrough of a quote or a finished site.
Is a video better than an email?
For anything visual or that needs tone, yes. For facts, dates, lists and decisions, email is better, because it's searchable and easy to answer. Many good client messages are both: a short video with the key points written underneath.
What if the client always wants a call?
Respect it for things that matter to them, and offer a video for the rest: send it before the call so the meeting is shorter, or as a recap afterward. Some clients come around once they see how much time it saves; some never do.
