Start here Start here 4 min read
A familiar scene

Polite is the machine's safe default; for someone you already know, safe comes out as distant — and the fix is letting it hear how you actually talk

AI email that sounds like a robot isn't tone-deaf by nature — it just doesn't know how you and this person talk

Cluster11 · Start here
Topicsinstructing · context · beginners
LanguageĐọc bản tiếng Việt →
TL;DR

AI email that sounds like a robot is rarely bad writing — it's that the machine doesn't know how close you and the recipient are, so it picks the safest move: polite, formal, keeping its distance. To a regular you've known for years, that "safe" reads like a step backward in the relationship. The fix isn't telling it to "be friendlier" — it's letting it hear a few emails you've actually written to this kind of person, so it catches your real voice.

A regular customer messages you with a question. You ask AI to draft the reply, to save time. It hands back an email that's spelled right, polite enough, ready to send. But reading it over, something grates: it addresses someone you've worked with for three years like a stranger who just filled in a contact form. "Dear valued customer," "Please do not hesitate to reach out"... correct, and cold. Send this, and they'll notice you're different today.

01Polite is its safe default — not what you needed

This isn't a writing problem. That email is well written — it's just written for the wrong person.

When you say "reply to this email," AI has no way of knowing how close you and the recipient are. It can't see the three years you've worked together, doesn't know you two trade jokes, doesn't know you've always used their first name and never "valued customer." Without that, it does the safest thing a machine knows: maximally formal, maximally polite, maximally distant. Because with a stranger, too polite beats too familiar — it's the move that's never wrong, so it always picks it.

The catch is that your relationship isn't a stranger relationship. The machine's "safe," dropped into something already warm, comes out as distance. It didn't write badly. It wrote for a version of the relationship that doesn't exist.

02Four signs an email sounds like a machine

The hard part is that emails like this look fine — easy to send without noticing. These signs help you catch it in the act:

Four signs — they'll feel it the moment you hit send
An over-formal greeting"Dear valued customer" for someone you call by first name every week. The distance is set in the opening line.
A boilerplate sign-off"Please do not hesitate to contact us for further information." A line everyone uses, so it sounds like no one.
No nod to shared historyit answers as if you'd never worked together — no "last time," no "as we discussed." A blank slate where there's a past.
Right question, wrong humanit resolves the request but misses what a person would add: "things were hectic for you last round — better now?"

Notice none of the four are writing errors — they're relationship errors. The email gets everything right except the one thing that matters most: it doesn't sound like you talking to that person.

03Let it hear how you actually talk to this person

The worst fix is typing "make it warmer and friendlier." Those adjectives are vague — "friendly" to a machine is an averaged notion, not your voice. Voice is hard to describe in words and easy to show by example.

1
Paste 2-3 real emails

"Here are a few emails I've sent to this kind of customer. Match this voice and level of formality." A sample says more than any adjective.

2
Name the relationship

"This is a regular of three years — relaxed, first-name, no 'valued customer.'" Give it the thing it can't guess.

3
Keep the samples for next time

No need to re-paste later — save those samples in one place and just point to them. Your voice becomes reusable.

Two or three old emails in "the right voice" pull its target from "polite for everyone" to "sounds like you talking to this person" — and the second is much closer to you.

Notice this isn't teaching AI to write better. It already writes smoothly. You're teaching it the one thing it could never know on its own: what this relationship sounds like. That's your job, because it lives in your head and in the history between you two, not in the machine.

So next time an AI email sounds like a machine trying to be polite, don't jump to "AI is tone-deaf." Ask instead: did I ever let it hear how I actually talk? Almost always, the answer is no. This is also the doorway to a bigger skill in the craft: giving a structured instruction to steer the voice, and choosing what to put in for the agent to anchor on. That cold email was never the AI being tone-deaf — it just never heard you talk.

The way out

This has a proper method — and someone has walked it first.

Cluster 01 · Steering the agentA vague command isn't short — it's open Cluster 02 · Context & memoryWhat to put in context for an agent
Tags#prompting#context#getting started
Other pains
01No idea where to begin02You ask it to write, it writes bland03Wrong — and dead sure of it04The same chore every morning05No one to cover the hours06Hand-stitched reports that never end07It forgets everything, every time08Hand it off, then hover09Don't ask AI to 'summarize the meeting' — tell it to find the things you actually need10A fluent translation isn't a correct one — it just doesn't know your field's vocabulary yet12Fifty near-identical emails: don't type it fifty times
Back to Start here

Get new pieces by email

Field notes on working with AI agents — occasional, no spam.