How to Humanize Slack and Teams Messages After ChatGPT
ChatGPT Slack messages read like email in a chat box. Keep them short, one ask, one specific. Human Writes is optional on longer pings—not a substitute for talking.
Slack and Teams are where ChatGPT looks most ridiculous. The model writes an email, then you paste it into a channel that people read on their phone between standups.
The grammar is fine. The length is wrong. There is a greeting, a recap, and “happy to discuss.” Nobody asked for a memo.
Human Writes is optional here. Most pings need a knife, not a rewriter. When the message is a longer DM or a client-channel note, one voice pass after you add the specific. This is not Copilot work email and not a status report.
Seven habits that still apply, compressed: Checklist for Writing Human-Like Emails.
Chat vs email (do not mix them)
| Slack / Teams | |
|---|---|
| One screen | Can be three paragraphs |
| Thread or huddle next | Calendar invite |
| Names already in the channel | Subject line has to work |
| Typo is fine | Typo in a client To: is not |
If you needed ChatGPT to “make it professional,” you probably needed a conversation instead.
Thread vs channel vs DM
| Place | Length | Humanize? |
|---|---|---|
| Public channel | Two lines + link | Almost never |
| Thread | Answer the last message; do not restart the epic | Rarely |
| DM | Can be a short paragraph | Maybe, if it is tense or external |
| Client Slack Connect | Email-quality facts, chat-quality length | Yes, one pass, then cut |
@channel is not a distribution strategy. If everyone needs it, it is probably an email or a doc with a one-line Slack pointer.
What AI chat drafts get wrong
| Failure | Fix |
|---|---|
| “Hope this message finds you well” | Delete |
| Recap of the epic | Link the doc |
| Three asks | One ask |
| @channel for an FYI | DM or a thread |
| Hedge: “maybe we could possibly” | “Need X by 3.” |
Copilot in Teams will happily summarize a thread into a paragraph nobody will read. Treat that like meeting notes: strip invented owners, then cut it again for chat.
Workflow (90 seconds)
- Write the ask in five words without a model. (“Review the PR.” “Yes on Friday.”)
- Add one specific (PR number, screenshot, timestamp).
- If it is still longer than six lines, cut before you humanize.
- For a client Slack or a tense DM, paste into Human Writes once, then cut again.
- Send. If it needs a meeting, say “huddle?” not a speech.
Do not paste confidential HR, unreleased numbers, or customer PII into a consumer chatbot. Use the approved tenant when the company requires it.
Before and after
AI draft:
Hi team, I wanted to take a moment to follow up on our previous discussion regarding the timeline. I hope you are all doing well. Please let me know if you have any questions or concerns. Thanks in advance for your help!
After the knife + optional pass:
Need a yes/no on the Friday deploy by 3. Blocker is the migration in #proj-billing.
Same team. Second version can be answered from a lock screen.
Where Human Writes helps
| Message | Use it? |
|---|---|
| “On my way” / emoji | No |
| Standup bullet | No, except you already wrote the fact |
| Client channel paragraph | Yes, one pass, then cut |
| Apology in a DM | Light pass; keep the incident |
| Launch announcement | After facts locked |
Chat purpose on the site is still your voice, not Story. Keep names and times yours.
What not to do
- Do not humanize a message into more words.
- Do not @here to sound important.
- Do not let Copilot invent a decision that was only a maybe in the huddle.
- Do not treat a detector score as the point. The person with 40 unread channels is the point.
Bottom line
Slack dies when it sounds like Outlook. Cut to one ask. Human Writes is for the rare long ping after the specific is in.
Paste the stiff DM on Human Writes only after it would fit on a phone.