Decide whether a message should go by email, chat, call or meeting.
Choose the channel for a message on purpose, based on what the message needs to do. Most people do the opposite. If the last message was a chat, they reply by chat, and the channel ends up choosing itself.
Picture a team chat where someone asks about the delivery schedule for a client in Jurong. After twenty-three messages, four people have given four slightly different answers. Someone has replied to the wrong message, and the question is still open. A five-minute call at message three would have settled it.
Writing is good for three things. It records decisions so people can find them later. It lets people respond in their own time, which matters when they are in different meetings or time zones. It also lets the reader think before answering, which helps when there are numbers or details to check.
Talking is good for three different things, whether it happens on a call, in a video meeting or face to face. It carries tone, so nuance and feeling get through. It is fast for back and forth, so a problem with many moving parts can be solved in minutes. It also handles disagreement better, because people soften quickly when they can hear each other.
To pick a channel, first ask what the message needs to do. It might need to record something, let people reply in their own time, carry tone, settle a back and forth, or let a group decide together. Then match it to this rough guide:
Email: decisions, approvals, anything formal, anything with attachments, and anything people outside the team need to see. Chat: quick questions with short answers, coordination during the day, and updates the team needs right now. Call: anything with nuance, a disagreement, a problem with many moving parts, or brainstorming. Meeting: when several people need to discuss and decide together. Module 6 covers how to run one.
The guide bends to circumstances. A quick question to a colleague in Manila may be better as a chat than a call because of the time difference. What matters is that you thought about the message and chose the channel on purpose.
The three-message rule says that if a chat thread has gone back and forth three times without getting closer to an answer, you stop typing and suggest a short call.
You can often spot a stuck thread before you count. Each reply raises a new question. People quote earlier messages to correct them. Someone writes "what I meant was". The replies get shorter in tone each round.
When you see these signs, stop typing and suggest a call with two options. For example: "This might be quicker to talk through. Do you have five minutes now, or at 3pm?" Most people are relieved when someone suggests the switch. If the other person is in a meeting or in another country, propose a specific time instead of leaving it open.
Some messages should never arrive only in writing. These are bad news, criticism of someone's work, a decision that affects someone personally, and anything you are angry about. Say these by voice first, then follow up with a short written summary.
The reason comes from Lesson 2.3, "Why your message sounded ruder than you meant". Text strips out tone, and these are the messages where tone matters most. A written criticism gets read and reread, often late at night, and each reading makes it feel harsher. The same point made on a call, in a tone that shows you are on their side, is far easier to hear.
Take a nurse manager at a public hospital who has to tell a staff nurse she has been moved off the night shift she asked for. A WhatsApp message saying "Your request was not approved due to staffing needs" is accurate, but it will feel cold. The manager could instead have a two-minute conversation at the start of the shift, explaining why and what might be possible next month, and follow it with a short written confirmation. That lands very differently.
If a message makes you angry, do not reply in writing until you have cooled down. If you must reply quickly, stick to the facts and suggest a time to talk.
The big weakness of talking is that it leaves no record. Two people can leave the same call remembering different agreements, and a week later nobody can prove which version is right.
After any call that decided something, send a recap. This is a short written summary sent by email or chat, within the hour if possible. Two lines are usually enough to cover the decision, who does what, and by when. After a call about the Jurong delivery, a recap to Darren might read: "Confirming: the delivery moves to Thursday 10am. You'll tell the client by today 5pm, and I'll update the dispatch schedule."
That recap does three things. It catches misunderstandings while they are cheap to fix, because if Darren remembers it differently, he will say so straight away. It tells anyone who was not on the call what the outcome was. It also creates a record, so a decision made by voice can still be found later. Whoever writes the recap gets to frame it, which is a small advantage worth taking.
Most people use one channel for nearly everything. People who live on chat use chat, and people who live in Outlook use email. That habit is not exactly wrong, but most people have never looked at it closely.
The activity below asks you to look back over your recent conversations. Find where your default channel helped, and where a different channel would have saved time or spared someone's feelings.
List your last ten work conversations, write down the channel you used for each, and mark the ones that would have gone better on a different channel.
Junxiong-WFG Organisation is an authorised representative of AIA Financial Advisers Private Limited (Reg. No. 201715016G).