Guide for ESL

Writing short messages at work: Slack, Teams and text

Slack, Teams and text messages follow habits nobody writes down. Here are the ones that hold across most US workplaces, with five messages rewritten.

Chat tools have their own grammar of behavior, and nobody hands new employees the rulebook. A message that would be fine as an email can land badly in Slack, and a reply that feels polite to the sender can read as cold on a phone screen. For writers working in a second language the stakes feel higher, because there is no time to redraft and every message is visible to the whole channel. The habits below are the ones that hold across most US workplaces. Where companies differ, the guide says so, and the best move on a new team is to read a busy channel for a week before you post much.

Chat is a conversation with a delay

Email is a letter: the reader opens it when they choose and expects a complete thought. A text is a tap on the shoulder. Slack and Teams sit between the two, and most trouble comes from treating them like one or the other. Treat them like email and your messages become walls of text nobody reads. Treat them like texting a friend and you flood coworkers with half-thoughts and notifications. The target is one complete message that the reader can act on without replying first.

Put the question in the first message

In many US offices, a message that says only Hi or Do you have a minute? is considered a small burden. The reader has to stop, reply, and wait to learn what you want. Put the greeting and the question in the same message. The writers in the examples that follow are invented.

BeforeHi Dana
Are you there?
I have a question about Friday
AfterHi Dana, quick question when you have a minute: is the Friday delivery still coming at 8 a.m., or did it move? The vendor is asking me to confirm by noon.

Why it works: Dana can answer from her phone in one line, even two hours later, and the deadline tells her how much the answer matters. Three separate messages also mean three notifications; one message means one.

One message, finished, with the next step

A good chat message answers three things in order: what is happening, what you have already done, and what you need or what happens next. Short lines help. So does one line of context before a request, so the reader does not have to scroll up.

Beforeso the printer on 3 is doing the thing again where it says paper jam but there is no paper jam, I opened it and closed it and tried again and it still says it, I don't know if anyone else has had this but it's kind of a problem because I have the Henderson packet to print before the 2:00 and I don't know what to do, maybe someone can call IT?
After3rd-floor printer is down: shows a paper jam error with no jam, cleared it twice. I've opened IT ticket #4471. For today, use the 2nd-floor printer. I'll post here when it's fixed.

Why it works: the revision has four short sentences, each doing one job, and it closes the loop. Nobody in the channel has to ask what was tried or whether IT knows. Fragments such as 3rd-floor printer is down are normal in chat; they would look wrong in an email.

Texting a supervisor

Text messages reach a supervisor at home, early, and often before coffee. Use them for things that cannot wait: calling in sick, running late, a safety issue. Say who you are if there is any chance your number is not saved. State the fact, what you have done about coverage, and when you will update.

Beforecant come in today sick sorry
AfterHi Marcus, this is Ana from the morning shift. I'm sick and can't come in today (Tuesday). I've texted Jen in case she can cover. I'll let you know tonight about tomorrow.

Why it works: the supervisor learns who, what, and what has been tried, in one read. Nothing here is formal. The sentences are complete, which in a text to a manager is enough formality on its own. Check how your workplace wants call-outs reported; some require a phone call, and a text will not count.

Channels, direct messages, threads, and the @ sign

  • Channel or direct message? If the answer would help other people, ask in the channel. If it concerns one person's schedule, pay, or performance, use a direct message. Assume anything in a channel can be seen by anyone who joins later, and that direct messages can be screenshotted.
  • Reply in the thread. When someone asks a question in a channel, most teams expect the answers under that message, in a thread, so the channel stays readable. Answering a thread's question out in the main channel is a common mistake for new employees.
  • @name sends a notification to one person. Use it when you need that person, and only then. @channel and @here notify everyone, including people on vacation or in other time zones. Reserve them for things everyone must see now, such as an outage. Many teams treat a casual @channel as a real breach of manners.
  • Status and quiet hours. Set your status when you are out or in a meeting, and respect a coworker's do-not-disturb setting. A message sent at 9 p.m. is fine if your team agrees it can wait until morning; say so if there is any doubt: No rush, tomorrow is fine.
Before@channel does anyone know the wifi password
AfterDoes anyone have the guest Wi-Fi password for the 4th-floor conference room? A client arrives at 2.

Why it works: the revision goes in the help channel without alerting the whole company, says exactly which network, and gives the reason, so the first person who sees it can answer.

Short replies and the problem of tone

Chat strips out voice and face, and readers fill the gap with whatever mood they are in. A few patterns are worth knowing. A single word with a period (ok. or fine.) reads as cold or annoyed to many American readers, especially younger ones, even when the writer meant nothing by it. A bare k is worse. Replying to a long message with a thumbs-up emoji is normal on most teams and means seen and agreed. One exclamation point in a friendly message is standard; a reply with none can feel flat, and a reply with three feels frantic.

Beforeok.
AfterGot it, thanks. I'll have the draft to you by 3.

Why it works: the revision acknowledges the message, adds the next step, and gives a time, so the other person does not have to follow up. It takes four seconds longer to type and saves a round trip.

Emoji vary more by company than anything else in this guide. In some teams a smiley softens every request; in others nobody uses one. Watch what people one level above you do, and do a little less.

Abbreviations: which ones are safe

Workplace chat has a standard set of abbreviations that are fine with anyone, including senior managers, and a second set that is fine only among people you know well.

Safe with anyoneMeaning
FYIfor your information (no reply needed)
EODend of day
OOOout of office
ETAwhen something or someone will arrive
PTOpaid time off
TBDto be decided
WFHworking from home
ASAPas soon as possible (a time is better)

LMK (let me know), NP (no problem), BRB (be right back), and TY (thank you) are common and casual; use them with peers once you have seen them used. lol, idk, u, r, tbh, and omg belong to personal texting and look out of place in messages to a supervisor or a client, whatever the company culture. If you are unsure what an abbreviation means, ask in a direct message. Everyone on the team was new once.

What does not belong in chat

  • Complaints about a coworker, by name or by hint. Chat logs are stored and searchable.
  • Anything about pay, discipline, medical leave, or a dispute with the company. Use email, so there is a record you control, or a meeting.
  • Bad news that will surprise the reader. Ask for five minutes on a call, then confirm in writing.
  • Any question that has already taken three back-and-forth messages. Move it to a call; Can I call you for 5 min? is a normal thing to send.
  • Long explanations. If a message needs scrolling, it is an email or a document, with a two-line summary in chat and a link.

A ten-second check

  1. Is the question or the point in the first line?
  2. Can the reader act without asking me anything?
  3. Is this going to the smallest audience that needs it?
  4. Would I be fine seeing this in a screenshot?

Chat rewards short, complete sentences, which is also where second-language writers often have the most control. For when to move up a level in tone, see formal or informal English at work; for the longer form, see professional email in English. Chat runs on two-word verbs (loop in, circle back, follow up), covered in the guide to phrasal verbs at work. If a message keeps growing while you type it, paste it into the clarity checker; it runs in your browser, sends nothing anywhere, and will flag the filler and the sentence over 30 words that usually hides the point.

Try it on your own draft

Paste a paragraph and see what the fox marks. The rewriting stays with you.

Open Clarity checker