Write chat messages on Teams, Slack or WhatsApp that someone can answer in one reply.
Work chat feels like conversation, so people tend to write it like speech, one line at a time. The person receiving it isn't sitting across from you. They are juggling other chats, meetings and work, and every half-message makes them stop, switch tasks and come back.
Take a common case. At 2.47pm you get a Teams message reading "Hi" from someone in another department you have never spoken to. You reply offering help and go back to work. At 3.15pm they ask, "Do you have the Q3 file?" You ask which one, and you find out at 3.40pm. In between, you were in three other chats, a meeting and a spreadsheet. The exchange took an hour for a question that needed one message and one reply.
The biggest single fix is to stop sending "hi" on its own and waiting for a reply. Put the greeting, the context and the question in one message. A longer single message is fine, because the reader can answer it whenever they next look, in one go, without asking you anything back.
Many people send "hi" first because launching straight into a request feels rude. In chat, the polite thing is to respect the other person's time, and a greeting in the same message as the question does that. Saying who you are and why you're asking also removes the awkwardness of messaging a stranger.
Jun Wei works in finance. Their first attempt arrives as three fragments: "Hi", "Are you free?" and a vague request for help with the shipment report. The better version is one message: "Hi Aisyah, I'm Jun Wei from Finance. Could you send me the Q3 shipment report for the Pasir Panjang warehouse? I need it to close the monthly accounts by Thursday. If you're not the right person, could you point me to whoever is? Thanks." Aisyah can reply whenever she next checks her phone, in one go, without asking anything back. Before she replies, she already knows who Jun Wei is and why they're asking.
Build your own messages the same way. Start with the greeting, your name and your department. Name exactly what you need: which file, report, location or system. Say why you need it and give the deadline. If the person may not be the right contact, ask them to point you to whoever is. If you want to add some warmth, include a line such as "Sorry to message you out of the blue."
In busy team chats, questions and answers drift apart, and an answer that comes late can't be matched to its question. Say someone posts a roster question at 9am and someone else posts about the printer at 9.05. When the answer to the roster question arrives at 10.30, it is hard to tell which question it answers.
On one ward, the nurses swap shifts through a WhatsApp group. One nurse asks if anyone can take their Saturday PM shift. Three other conversations follow, then someone writes "OK I can", and nobody is sure who agreed to what. A reply that quoted the original request would have settled it.
Keep one topic per thread. In Teams and Slack channels, reply inside the thread under the original message so your reply sits with its question. In WhatsApp groups, use the reply feature so your answer quotes the question. If you have two unrelated questions for the same person, send them as two separate messages so each can be answered and found on its own.
Most chat tools let you flag a message as urgent or important, and words like "URGENT", "ASAP" and "need this now" do the same job. These flags work only when people use them rarely. If you put them on everything they lose their meaning, and a message that really is urgent gets ignored along with the rest.
Save urgent words for things that can't wait until tomorrow, such as a client on the phone, a shipment about to leave with the wrong paperwork, or a system that is down. For everything else, give a real deadline instead of "ASAP", such as "by 4pm today", because the reader can plan around a time. If something is truly urgent and the person hasn't replied, call them. An urgent chat message that sits unread for an hour was sent through the wrong channel.
Voice notes are popular in Singapore, especially on WhatsApp, and they're quick to send. You can talk through a problem while walking to the MRT. For the person receiving one, they're slow. They need a quiet place or headphones, they have to listen at your speed, and they can't skim for the part that concerns them. A two-minute voice note often holds what a three-line message would have said. Voice notes are also hard to search, so a decision or date mentioned in one can't be found the next week.
At work, ask before you send one, with something like "Easier if I send a voice note on this?" Some colleagues are happy with voice notes. Others would rather read, especially people in open offices or long meetings. When you do send a voice note, follow it with a one-line text summary of the main point.
Problem reports need the same care. A bank analyst needs help from a colleague in IT. Their first version is five fragments: "Hello.", "U there?", "The dashboard is not loading.", "Urgent.", "Pls help." The better version is one message. It greets Marcus and says the credit risk dashboard has shown a loading error since 10am. It says the analyst has tried two browsers and cleared their cache, and that they need the dashboard for the 2pm risk committee pack. It asks Marcus to check, or to say who should, and it has a screenshot attached. Marcus can start work at once, because he knows what is broken, when it started, what has been tried and why it matters by 2pm.
When you report a problem, say what is broken, when it started, what you have already tried, why it matters and by when, and attach evidence such as a screenshot.
The activity below gives you practice with the hardest case: a first message to a stranger, where you have no shared history and they owe you nothing.
Write the one chat message you would send to a colleague you have never spoken to, asking for a file you need by Thursday.
Junxiong-WFG Organisation is an authorised representative of AIA Financial Advisers Private Limited (Reg. No. 201715016G).