Why AI drafted emails sound robotic to your coworkers

AI drafted emails sound robotic to coworkers because coworkers are the only audience with a baseline for you. A client compares your message to an average business email. A teammate compares it to the last forty messages you actually wrote, and the gap shows up in a single line. That's the whole problem with drafting internal mail in a chat window.

Why your coworkers spot an AI draft faster than anyone else

Recognition runs on contrast. If you have never emailed someone before, a stiff message reads as a formal message. If you message them every day, the same text reads as not you.

There is more writing to compare against than ever. Professionals now spend more than 28 hours a week on written and in-tool communication, a 13.2% rise over the previous year, and most of that growth landed in team chat rather than email (Grammarly, The Productivity Shift, fielded by the Harris Poll between September 24 and October 1, 2024). More volume means a sharper baseline in the reader's head, and more chances for a stiff draft to stand out.

What a team register actually is

A register is the settled way a group writes to each other. It covers the greeting, the sign off, how blunt people are allowed to be, how much context anyone bothers to explain, and whether full sentences are normal or faintly odd.

Voice is who you're on the page. Register is which version of you shows up for this room. Your voice flexes by relationship while staying recognisable, and that flexing is exactly what a model has no way to observe.

AI generated text tends to be more formal, more structured and more emotionally positive than human writing on the same topic (Linguistic Characteristics of AI-Generated Text: A Survey, arXiv, October 2025).

Every team has a register. Almost nobody writes it down, so it lives in details like whether people open with a name, whether a request ends in a question mark, and whether anyone ever types a full stop after a one line answer.

The tells that read as AI inside a company

Most AI tells are the same ones you would spot in a public blog post, but inside a company they land harder, because the reader has a personal reference point.

The throat clearing opener

A first line that says nothing before the actual point. In a company where people write to each other constantly, it reads as a delay, and the reader starts scanning.

The metronome rhythm

Every sentence lands at roughly the same length. Human internal mail is lumpy, with a short line after a long one and the occasional fragment, because people type in bursts between other work.

Stacked hedging

Three qualifiers wrapped around one simple statement. Say the thing once, then say what you're unsure about as a separate sentence.

Vague nouns

The relevant materials, the matter we discussed, various stakeholders. Those nouns are the clearest sign that the writer did not have the details, which is precisely the situation a model is in.

The meta tell

Read the draft back and look for one line only you would have written. If everything in it could have been sent by anyone to anyone, that's the underlying problem, and the other tells are just its symptoms.

Why do AI drafts come out more formal than you ever are?

A model with no information regresses to the average of the writing it was trained on. For email, that average is polite business correspondence and support copy, so the safe default comes out deferential, padded and rigid.

The model also can't see the thread you're replying to. It does not know that this colleague asked twice already, that the deadline is Friday because the printer closes at noon, or that your team says quick one instead of I wanted to reach out.

Instruction tuning makes this worse in one specific way. Models are rewarded for being complete and agreeable, and both push toward more explanation, more softening and longer messages, which is the opposite of how people write to someone they sit near.

If the formality is leaking into everything you write, not just internal messages, start with the guide to sounding less formal in AI writing and treat this page as the internal mail version.

How do you build a register snapshot for your team?

A register snapshot is a short written description of how your team talks to itself, built from messages you already have. It takes about twenty minutes, and it's the most useful thing you can do here, because it turns a guess into a reference you can paste into a prompt.

Step one, collect. Open the channel or folder where your team talks most and copy ten to fifteen short messages that feel typical. Screenshots are fine. Don't curate for quality, curate for ordinary.

Step two, label what you see. For each example note the greeting, the sign off, the average sentence length, whether hedging shows up, and how direct the ask is. You're after the mode, not the best message in the set.

Step three, write five rules you could hand to a stranger. They should be specific and behavioural, something like: no greeting inside the team channel, name the deliverable and the date, one line for the apology, close with the next action rather than a question.

Step four, test it. Draft a real message with the rules in place, then read your version and the model version back to back. The one that matches your team will be the shorter one.

For the same idea applied across different readers, email tone by situation walks through the four registers that cover almost every message you send.

The six minute pass before you hit send

This is the editing pass for a draft you can't or don't want to re-prompt. It's subtraction, not rewriting. Most stiff internal mail is simply longer than it needs to be.

Minute one and two: cut the opener. Start at the first sentence that carries information. That single deletion removes the most recognisable machine signal in the whole message.

Minute three: unstack the hedges. Delete every qualifier you don't need, and keep one only where you're genuinely unsure. We can ship Thursday beats I think we might possibly be able to ship Thursday.

Minute four: replace vague nouns with real ones. The deck, the print deadline, Priya, the thread from Tuesday. Specifics are what make a message read as written by someone who was in the room.

Minute five: break the rhythm. Split a long sentence, then put one short line next to it. Variation is the thing an ear reads as human even when it can't explain why.

Minute six: read it out loud. If a line sounds like an announcement when spoken, rewrite it the way you would say it. Your spoken register is the one your team already recognises.

For a longer version of that pass, how to fix robotic email tone runs the same steps with before and after examples.

Two internal emails, before and after

Here is what a model typically returns for the instruction tell Marcus the deck slips to Friday.

Before: I hope this message finds you well. I am writing to inform you that, due to unforeseen circumstances relating to the review cycle, the timeline for the deck has been adjusted. Please don't hesitate to reach out should you have any questions regarding the status of the deliverable.

After: Marcus, the deck slips to Friday. Review data came in late and I would rather not ship unchecked numbers. I will send the updated version Thursday afternoon.

Same facts, eleven words of substance instead of sixty. The second version leads with the news, gives one concrete reason, and closes with a commitment rather than an invitation to ask. Nothing about it's casual. It's simply direct, and Marcus can act on it in one read.

When formal is the right call on an internal thread

Sometimes formality is correct, and stripping it out would be a mistake. Performance feedback, a written record after a dispute, anything that will end up attached to a document, and first contact with a department you have never dealt with.

The test isn't formal against casual. It's deliberate against default. Formal writing that a person chose reads as careful. Formal writing that a model produced reads as evasive, because the padding hides where the facts stop.

What to do when a coworker asks if AI wrote it

Answer plainly. Denying it when the sender is right costs far more than the draft ever saved, and the person asking usually already knows.

It helps to be clear about what a tool can and can't prove. A detector score isn't evidence of authorship. OpenAI withdrew its own text classifier on July 20, 2023, after it caught 26% of AI written text and mislabelled human text 9% of the time, and it flagged that the tool was unreliable on anything under 1,000 characters.

The more useful answer is the visible one: you drafted it, you gave it the facts, and you rewrote the parts that did not sound like you. That's a normal way to work in 2026, and it's worth saying out loud rather than treating as an accusation.

If a score is genuinely in play, how to interpret AI detector results covers what a percentage actually means and where the margin of error sits.

The short version

Internal mail is the hardest place to hide a draft, because your team compares your writing to your writing. Map the register once, run the six minute pass on every draft, and keep the final line for yourself.

The message that sounds like you isn't the one that scores best on a formality scale. It's the one your colleague can read once and answer without asking what you meant.

Frequently asked questions