Slack is where most workplace misunderstandings happen. It's fast, informal, and read without context — which means a two-line message that sounds fine in your head can land as cold, demanding, or passive-aggressive to the person reading it.
Below are real examples across the most common Slack scenarios, with professional, direct, and friendly versions of each — so you can choose the right tone for the right relationship.
Want to see how Tonero rewrites messages? Try the live demo → — see a real rewrite in seconds, no install needed.
Status check-in
Any update?
Quick check — where do we stand on the migration? Wanted to confirm before the 3pm call.
Following up on the migration — could you share a brief status update? We have a stakeholder call at 3pm and it would be great to have current context going in.
Hey! Just wanted to check in on the migration — how's it looking? Happy to help if anything's blocked before the 3pm call.
Asking for a file or resource
Send me the Q2 report.
Could you share the Q2 report? Need it for the board deck I'm building today.
I'm preparing the board presentation and would like to include the Q2 report. Could you share the latest version when you get a chance?
Hey — working on the board deck and could really use the Q2 report. Do you have it handy? No rush if you're in the middle of something!
Flagging a problem or delay
This isn't going to be ready on time.
Heads up — the API integration is running behind. Current estimate is EOD Friday instead of Wednesday. Let me know if that changes priorities.
I want to flag a delay on the API integration. We're now targeting EOD Friday rather than Wednesday. I'm happy to walk through what's causing the hold-up if that would be useful.
Hey — wanted to give you a heads up that the API integration is going to take a bit longer than expected. Looking at EOD Friday now. Sorry for the delay! Let me know if you want to talk through the timeline.
Giving feedback on someone's work
This isn't what I asked for. Can you redo it?
Reviewed the draft — a few things need to change before we share it externally. Can we jump on a quick call today?
Thank you for the draft. I have a few notes before this goes out — I think there are some areas we can sharpen. Would you be available for a brief call today to go through them?
Hey — thanks for putting this together! I have a few thoughts on how we can make it even stronger before we send it out. Want to hop on a quick call to talk it through?
Saying no or pushing back
That doesn't work for me.
Can't take this on this sprint — I'm already at capacity. Happy to pick it up in the next cycle or identify someone who has bandwidth now.
I appreciate you thinking of me for this. Given my current workload, I wouldn't be able to give it the attention it deserves this sprint. I'd suggest either deferring it or routing it to someone with more availability right now.
Ah, I wish I could! I'm pretty slammed this sprint and don't want to half-do it. Could we revisit next cycle, or is there someone else who might be able to take it on now?
Tips for Slack specifically
- Use threads. Replying in a thread keeps channels clean and signals you're being intentional, not reactive.
- Don't send "hi" alone. Just send the full message. The other person shouldn't have to wait to find out what you need.
- Avoid ALL CAPS except for genuine emphasis — it reads as shouting.
- One topic per message. If you have three questions, list them. Don't bury the second and third in a wall of text.
- Status notifications are your friend. Setting "In a meeting" or "Focusing" tells people not to expect an instant reply — reducing the social pressure on both sides.
Related: Teams message examples → · Gmail message examples → · Tonero for Slack →
Get the right tone in Slack — automatically
Tonero adds a one-click tone toolbar to every Slack text box. Professional, Direct, or Friendly — in one click, no tab-switching. Free to start.
Get Tonero it is free