Communication: chat, email or calls, and why we prefer written
Which channel fits which kind of message between a business and its digital partner, and why we keep decisions in writing.
The short answer
Communication in a good partnership has a shape. Requests, decisions and approvals are written, in one shared channel, so nothing depends on anyone’s memory and work continues across time zones, holidays and staff changes. Changes are shown, not described: a preview link on a phone replaces a paragraph of explanation and a round of misunderstanding. Calls are reserved for what genuinely needs them: planning, the quarterly review, real disagreement or nuance, and incidents. Email carries the record and reaches people outside the channel; the phone is for critical incidents; chat is where the work happens. We prefer written not because we dislike talking but because written is what turns a request into a tracked, sized, delivered and previewed piece of work that anyone can find later.
Which channel for what
| Purpose | Channel | Why |
|---|---|---|
| Requests for changes | The shared channel, written | Sized, queued, tracked; a record |
| Decisions and approvals | The shared channel, written; previews approved by a click | Unambiguous; findable later |
| Seeing a change | A preview link | Shows rather than tells; approved on a phone |
| Planning and the quarterly review | A call, with a written summary after | Nuance and discussion; then a record |
| Disagreement or a hard conversation | A call, then a written summary | Tone travels badly in text |
| Critical incidents | Phone and the escalation route your agreement names, then the channel | Speed; then the record |
| The monthly report, contracts, formal notices | The record; reaches everyone | |
| Questions about the report | The channel or the monthly hour | Both work; the answers become documentation |
The habits
- One channel for the work, agreed at the start; everything else routes into it.
- Requests written with what and why; the partner sizes and queues them.
- Previews for every change, approved with a click.
- Calls scheduled for planning, review and anything with nuance, with a written summary afterwards.
- Decisions made on calls written in the channel the same day.
- Critical incidents by phone, then documented.
- Email for the record and for people outside the channel.
Why written works better for you
You make a request when it occurs to you, not when a call can be arranged. You approve a change from your phone in a minute, having seen exactly what will ship. You can find any decision later. Your colleagues can see what was asked and done without asking you. And when something is disputed, the record settles it in a minute rather than a meeting. The partner gets uninterrupted time to build, which is what you are paying for.
What this means for you
Agree one written channel for requests, decisions and approvals; expect previews instead of descriptions; keep calls for planning, review, nuance and incidents, with written summaries; use email for the record. Written first gives both sides the same history, lets work continue when nobody is on the phone, and makes every change traceable from request to live.
Frequently asked questions
Why not just call when we need something?
Because a call leaves no record, interrupts whatever the partner is doing, and depends on both people being available at the same moment. A written request in the shared channel is sized, queued, done and previewed without anyone waiting for anyone, and it is there six months later when someone asks why. Calls are for conversations; requests are not conversations.
How fast should we expect a reply in the channel?
Acknowledged within the working day for standard requests, and for anything urgent at the response time your agreement states, with the preview or the answer following on the timescale the size implies. What you should not expect is instant replies to everything, because a partner who answers every message immediately is not building anything. The channel is asynchronous by design.
What goes in email?
The monthly report, contracts and formal notices, anything that must reach people who are not in the channel, and a summary of decisions made on calls. Day-to-day requests belong in the channel where they are tracked; email threads are where requests go to be forgotten.