When Not to Use AI to Write an Email

Most prompt guides skip the question of when not to use AI to write an email. The harder problem, they assume, is getting the AI draft to sound like you. That assumption is usually right — a condolence message is not the bottleneck most people are wrestling with. But there is a specific set of situations where letting a model write the words makes the outcome worse, not better. The relationship reads the output differently than it reads a sentence the person chose themselves. Knowing the list, and knowing what AI can still safely do in those moments, turns a prompt library into judgment.

This post names eleven situations where you should write the email yourself, explains why AI drafting backfires in each one, and identifies the limited prompts that remain genuinely useful — pressure-testing your wording, predicting how it will land, catching a phrase that reads cold — so the reader leaves with a usable rule rather than a scolding.

Before you start: why AI drafting backfires in specific situations#

There are two structural reasons AI fails certain emails, and neither is about quality. A language model produces the most plausible sentence given what you tell it. For most professional email, 'most plausible' is exactly what you want: a clear, correctly toned, direct reply. The problem comes when the email's value is something a model cannot supply — genuine personal accountability, unique relational history, or specificity that only the person who was actually there can produce.

The first signal is that the relationship is the point, not the information. A condolence, a personal apology, a farewell — these messages exist so the recipient knows a real human who knows and cares about them is acknowledging something real. When the words come from a model, the acknowledgment is technically present but the human-to-human signal is absent. A person who knows you will feel the absence. It may not register consciously as AI-written, but something will feel off — too smooth, too balanced, too complete.

The second signal is that the email carries accountability or legal weight you cannot delegate. An apology for something you personally did is not a task you can route through a text generator any more than you can outsource the feeling of remorse. A formal legal notice carries meaning that attaches to you as the sender. Letting AI write those sentences undermines the thing the email is meant to establish. Both signals are worth holding in mind as you read the list below — they are what the eleven situations have in common.

The eleven emails you should always write yourself#

1. 1

   Condolences and grief

   A condolence email has value because a specific person who knows and cares about the recipient took time to acknowledge something real. A model-drafted condolence is plausible — it says the right things in the right order — but it is from no one in particular, which is the opposite of why anyone sends one. Write it yourself, briefly, in your own words. AI can review it afterward for a phrase that reads cold or generic; it cannot write the heart of it.

2. 2

   Terminating employment or ending a long client relationship

   A termination message carries enormous emotional weight for the recipient. Letting AI draft it communicates, indirectly, that the relationship was not worth the time to write a human sentence. The message needs to be clear, humane, and direct — qualities that are hard to fake and easy to feel when absent. Write it yourself, then use AI only to check whether the tone reads as dismissive or vague about next steps before you send.

3. 3

   A genuine apology for something you personally did

   An apology for an operational mistake — a billing error, a product bug, a missed SLA — is a task AI handles well. An apology for something you personally did to someone is different. The specificity and the accountability have to come from you, because a model-drafted apology for a personal wrong reads as what it is: words without the person behind them. AI can check that the draft does not blame-shift or bury the apology. It cannot supply the genuine ownership.

4. 4

   Legally operative language

   Formal legal correspondence — demand letters, contract modifications, notices of breach, resignations with legal implications — carries meaning that may be reviewed by lawyers and attaches to you as the sender. Writing here is not primarily about quality of prose; it is about intent, precision, and accountability. Use a lawyer for anything with legal teeth. Do not let a model produce legally operative sentences you have not verified word for word against a primary source.

5. 5

   Sensitive personal disclosures

   Disclosing a health situation, a family crisis, or any circumstance that requires the recipient to know something private about your life — these messages need to be yours. Pasting sensitive personal information into a model also raises a direct privacy question: you are sending your private situation through a third-party system. The fact that you wrote the words makes the message appropriate to the disclosure in a way a model-produced version cannot match.

6. 6

   Asking someone to stake their reputation on you

   A reference request, an ask for a formal endorsement, or a request for an introduction to someone important — these depend entirely on a personal relationship. The person being asked is putting their reputation behind yours. A request they can sense was drafted by AI signals that you did not think the relationship was worth the time to write to them directly. Write it yourself; the personal quality of the ask is part of the ask.

7. 7

   Difficult feedback that may damage or end a relationship

   Delivering difficult feedback — to a direct report who is not going to work out, to a client relationship that is deteriorating, to a colleague who has crossed a line — requires you to own every word. These conversations go wrong when the other person cannot tell whether they are talking to a person or a policy. Writing it yourself forces the clarity that difficult feedback needs: you have to decide, in plain words, exactly what you mean.

8. 8

   Re-establishing contact after conflict or silence

   Reaching out after a falling out, a period of estrangement, or a professional dispute is one of the most human things you can do by email, and one of the most easily invalidated. A model-drafted reconnection sounds like a reconnection from no one in particular. The whole point is that a specific person — you — decided to reach out. Write it yourself, even if it comes out imperfect, and use AI only to check whether the opening reads as defensive or score-keeping.

9. 9

   Farewell and tribute messages

   Leaving a team, marking a colleague's retirement, acknowledging a contribution at a significant moment — these messages are valued because they are personal. A model-drafted farewell from a manager reads as an absence, not a presence. Even a short, imperfect personal note beats a polished one that could have come from anyone. Write the specific memory, the specific quality you want to name. AI can help you trim it if it runs long.

10. 10

    Confidential or privileged information

    If the email contains information that is legally privileged, covered by an NDA, classified within your organization, or otherwise confidential, pasting it into a model is a decision with real consequences. Even services with zero-retention policies are third-party systems processing your data. The privacy risk alone should stop you. Handle confidential content in your own words, in your own email client, with whatever safeguards your organization requires.

11. 11

    Any email where the fact that you wrote it is the point

    Some emails carry value precisely because a specific person — with a specific relationship and a specific history — took the time to write them. When the fact that it came from you is load-bearing, producing it from a model removes the load. A useful test: if you would be uncomfortable telling the recipient that AI wrote this — not out of shame, but because it would change how they receive the message — write it yourself.

When AI can still help in these situations#

None of the eleven situations above mean AI is useless in the moment. They mean AI should not draft the message. A narrower set of prompts remains genuinely useful: not for producing the words, but for reviewing what you wrote yourself.

The table below maps each situation to the specific review question that stays legitimate — and marks clearly where even review is off-limits because the content should not be shared with any third-party system at all.

What to do when your first draft still doesn't land#

You write the email yourself and it still reads wrong. This is common — these situations are hard precisely because the emotional weight makes the words come out awkward, stiff, or over-qualified. Three approaches help without outsourcing the authorship.

Read it aloud before you send it. The sentence that sounds fine in your head often reveals itself the moment you hear it. 'I am so sorry for your loss' said aloud sounds more human than it looks on a screen; 'It is with deep regret that I inform you' sounds as hollow as it is. Reading takes thirty seconds and catches the phrase that will land wrong.

Ask a trusted colleague to read it with one specific question: does this sound like me, or does something feel off? A person who knows you will catch the sentence that is technically accurate but cold — the thing a model cannot catch because it does not know the relationship. This is what human editing does that AI review cannot replace in these situations.

If you use AI at all, use only the narrow review prompts in the table: one specific question about a specific problem, not a request to rewrite. The words stay yours. You are using the tool for what it can genuinely do, which is noticing patterns in language without the emotional charge that makes these emails hard to write in the first place.

A faster way for the other 95% of your inbox#

Everything above covers the emails that require your words. The rest of your inbox — client updates, follow-ups, scheduling, status replies, anything routine to moderately complex — is exactly where AI drafting is most valuable. The manual approach still works; this is what doing it continuously without losing control looks like.

We build AI Emaily, an AI email client with a Copilot mode that drafts replies inside your real inbox — grounded in the actual thread — and queues every draft for your review before anything sends. Drafts come from a user-set Personal Context brain and per-client profiles, not from training on your mail. You approve before send, you can undo, and every action is audited. For the eleven situations above, Copilot mode gives you a plain compose window, exactly the same as any other email client — which is what those messages need.

Start free at app.aiemaily.com/signup. Connect the inbox you already use, and let the AI handle the volume while you keep the judgment on what matters.