AI Email Prompts: 12 Templates That Actually Work

Your inbox has 47 unread emails and you're staring at a reply you've rewritten three times. It still sounds either passive-aggressive or like you're begging. This is exactly where AI email prompts earn their keep.

Not by writing your emails for you. By getting you out of the rewrite loop faster.

Most people use AI email tools completely wrong. They type "write a professional email" and paste whatever comes out. Then they wonder why it sounds like a terms-of-service agreement wrote back. The fix isn't a better tool. It's a better prompt.

Why most AI email prompts fail

The problem isn't ChatGPT. It's the same problem you'd have if you hired an intern and said "write a good email for me" while walking away. You'd get something technically correct and completely useless.

AI is fast, pattern-matching software. It's genuinely good at language-shaped work: drafts, rewrites, summaries, tone adjustments. What it's not good at is guessing what you actually need when you give it nothing to work with.

The "garbage in, garbage out" rule is brutal here. Feed it a vague request and you get a vague email. Feed it role, context, the specific problem, and what outcome you want, and you get something worth editing.

The goal isn't to eliminate your judgment. It's to give you a decent draft in 30 seconds instead of staring at a blank screen for 20 minutes.

A lot of the anxiety around AI at work comes from misunderstanding what it actually is. It's not a mind reader. It's not a replacement for knowing what you want to say. If you've ever read about what AI can and can't do, you'll know that the gap between "writes fluent sentences" and "knows your situation" is enormous. Prompts are how you close that gap.

The one prompt formula that works for almost everything

Before the 12 copy-paste templates, here's the structure behind all of them. Every good AI email prompt has five parts:

Role: Tell it who's writing and to whom. "I'm a project manager writing to a client."

Context: One sentence on the situation. "They missed a deadline and we need to reschedule."

Task: What you want the email to do. "Write a brief, professional message asking to reset the timeline."

Constraints: Tone, length, anything to avoid. "Keep it under 100 words. Don't sound accusatory."

Format: What you want back. "Give me two options."

You don't always need all five. But the more you include, the less editing you'll do afterward. Think of it like briefing a smart intern who's fast, tireless, and occasionally confident about things they shouldn't be. You still have to supervise the output.

The format instruction is one most people skip. Asking for two versions gives you something to choose between rather than just accept or reject. Asking for bullet points first before the full email helps you check the logic before you check the language. Small adjustments to how you ask change the usefulness of what comes back by a lot.

What makes a bad email prompt vs. a good one

Let's be specific about this because the difference matters.

Bad prompt: "Write a professional email following up on my proposal."

What you get: A generic, lifeless message that could have been written by anyone, for any proposal, to anyone. It'll start with "I hope this email finds you well" and end with "please don't hesitate to reach out."

Good prompt: "I'm a freelance designer. I sent a brand refresh proposal to a mid-size retail client two weeks ago. They haven't responded. Write a short follow-up email that assumes they're busy, not ignoring me, and makes it easy to reply. Under 80 words. No apology for following up."

What you get: Something close to usable on the first try.

The difference is specificity. Context about who you are, who they are, the history, and what you want the email to accomplish. That's what separates useful AI output from the kind you delete and rewrite manually anyway.

It takes an extra 30 seconds to write a better prompt. That 30 seconds saves you five minutes of editing, or worse, five minutes of trying to figure out why the draft feels wrong.

A safety reminder before you paste anything

This matters and you should read it before using any of the prompts below.

Do not paste confidential information into ChatGPT, Claude, or any AI tool unless your company's policy explicitly allows it. That means no customer PII, no HR conversations, no legal or medical details, no private employee information, no financial figures tied to real names. Replace names with "[Client Name]" and strip out specific numbers if you're not sure.

Once the draft comes back, read every word. Verify any facts, dates, links, attachments, or promises the AI included. It will occasionally invent details with complete confidence. Never send AI output without reading it. That's how you end up cc'ing the wrong person on a message that describes them.

If you want the broader thinking on using AI at work without creating problems for yourself, the no-BS starter guide covers it.

12 copy-paste AI email prompts that actually work

These are designed for ChatGPT or Claude. Paste the prompt, fill in the brackets, read the output, then edit. Don't send anything without reading it first.

1. Make a messy draft clear

I've written a draft email but it's unclear and jumbled. Clean it up so it's easy to read, keeps the key points, and uses plain language. Don't change the tone much. Here's the draft: [paste draft]

2. Shorten a too-long email

This email is too long. Cut it to under [100/150/200] words while keeping the main message and the ask. Remove anything that's just filler or context the reader doesn't need. Here's the email: [paste email]

3. Make a message warmer

This email is technically fine but sounds cold. Rewrite it so it sounds like it came from a real person, not a policy document. Keep it professional but human. Same length. Here's the original: [paste email]

4. Make a message firmer

I need to send this email but it sounds like I'm apologizing for asking. Rewrite it so it's direct and confident, not aggressive. The ask should be clear. Here's the draft: [paste draft]

5. De-escalate a tense thread

This email thread has gotten tense. I need to reply in a way that addresses the issue without escalating it. Keep the tone calm and solution-focused. My goal is [state your actual goal]. Here's the thread: [paste relevant parts, with names replaced]

6. Ask for a decision

I need to ask [their role] to make a decision about [topic]. They've been slow to respond. Write a concise email that explains the situation in two sentences, clearly states what I need them to decide, and gives a deadline of [date]. Keep it under 100 words. Respectful but direct.

7. Follow up without sounding needy

I sent an email [X days] ago about [topic] and haven't heard back. Write a short follow-up that's polite, references the original, and makes it easy for them to respond. Don't make me sound desperate. Under 60 words.

8. Summarize a long email thread

Summarize this email thread in 3-5 bullet points. Include: what was decided, what's still open, and any action items with names attached. Here's the thread: [paste thread, names replaced if needed]

9. Write a client recap email

Write a short email recapping what was discussed in our meeting with [client role] on [date]. Include: what we agreed to do, any open questions, and next steps with rough timelines. Tone should be professional and organized. Here are my notes: [paste notes]

10. Turn bullet points into an email

Turn these bullet points into a well-written email. Keep it clear and concise. The recipient is [their role]. The purpose is [state purpose]. Tone should be [professional/friendly/formal]. Here are the bullets: [paste bullets]

11. Rewrite jargon into plain English

This email is full of jargon and buzzwords. Rewrite it in plain English without losing the meaning. The reader is [describe their background, e. g., "not a technical person"]. Keep the same length. Here's the original: [paste email]

12. Check an email before sending

Read this email and tell me: Does it clearly state what I need? Does anything sound rude, confusing, or ambiguous? Is there anything missing (attachments mentioned, questions unanswered, unclear deadlines)? Here's the email: [paste email]

That last one is underused. Running your email through a pre-send check takes 15 seconds and has saved at least a few people from career-limiting moments.

For more templates across different work situations, the 12 prompts for work collection has formats for reports, decisions, and presentations too.

How to adapt these prompts when they don't quite work

The first output isn't always right. That's fine. The prompts above are starting points, not guarantees. Here's what to do when the draft comes back wrong.

If the tone is off, don't rewrite from scratch. Add a sentence to your prompt: "That's close but sounds too formal. Rewrite it to be warmer, like I'm talking to someone I know." Or: "Less formal. I want this to sound more like a message from a person, less like a memo." You can tune the output without starting over.

If it's too long, paste it back and say "Cut this by a third. Keep the ask and the deadline. Cut everything else." It'll do it in seconds.

If it invents details you didn't give it, just delete them. Don't try to fact-check AI hallucinations by asking AI to check itself. Read the output yourself and remove anything you didn't put in.

If you asked for two versions and both are bad, the problem is usually the prompt. Go back, add more context, and try again. The fix is almost always more specificity, not a different tool.

One pattern that works well: ask for the email structure first, then ask for the full draft. "Before you write the email, list the three things it needs to accomplish." If the list is right, tell it to write the email. If the list is wrong, correct it there. You're checking the logic before you check the language, which saves time.

What to do with the output

You asked for a draft. You got one. Now the actual work begins, and it takes about two minutes.

Read every sentence. Does it sound like you? If not, change it. Does it say what you actually mean? If not, fix it. Did it invent a detail, a date, or a promise you didn't make? Delete it.

AI doesn't know your relationship with this person. It doesn't know the history, the politics, the unspoken thing from the last meeting. You do. That's the part that actually matters. The prompts above handle the scaffolding. You handle the judgment.

This is the distinction that matters. AI handles the language work. You handle the thinking. The people who get replaced aren't the ones who use these tools. They're the ones who either refuse to use them at all, or use them without reading the output. Both are equally avoidable.

Dee covers the full thinking behind this in Don't Replace Me, specifically the "smart intern" framing: AI is like a new hire who's fast, has read everything, and occasionally makes things up. You wouldn't send an intern's work to a client without reading it. Same rule applies here.

The emails where you shouldn't use AI prompts at all

This doesn't come up in most articles about AI email tools, but it should.

There are emails where using a template is the wrong move, not because AI can't write them, but because the relationship deserves better. When someone close to you is going through something hard and they've reached out. When you're genuinely apologizing for something serious, not a missed deadline, but something that matters. When you're having a real disagreement with someone you work with every day and the relationship is on the line.

AI can write something that sounds sympathetic. It can't be sympathetic. The difference is small on the screen and huge on the receiving end. People who know you can usually tell when something sounds like you and when it doesn't.

Use AI for the operational stuff. The follow-ups, the recaps, the status updates, the "can you please just decide" emails. Write the human stuff yourself. If you're not sure which category an email falls into, it's probably the second one.

There's also a practical reason: AI-written empathy tends to land wrong. It hits all the keywords but misses the specifics. It says the thing without knowing the thing. You end up with something that reads like a condolence card from a company you don't have a relationship with. Write those ones yourself.

Should you tell anyone you're doing this?

Short version: probably yes, in most situations. The longer answer depends on your company, your role, and what kind of email you're writing.

The full breakdown of whether to disclose AI use to your boss is worth reading if this is on your mind. The 68% of workers who hide their AI use aren't necessarily doing something wrong. But it's worth knowing where your company actually stands before you're in an awkward conversation about it.

What you're doing with these prompts isn't fundamentally different from asking a colleague to read a draft before you send it. You're getting a second pass on your own thinking. The output is yours. You read it, edited it, decided it was right, and sent it. That's how writing has always worked.

One tool is enough

There are about 40 AI email assistants on the market right now with names like "Mailmuse" and "InboxGenie" and similar. Most of them are wrappers around the same models you already have access to for free or at $20/month.

You don't need any of them. ChatGPT or Claude and the prompts above will handle everything in this article. The guide to using ChatGPT specifically at work goes deeper if you want more context on how to get the most out of one tool instead of chasing 10.

Stop collecting tools. Start using the one you have.

Frequently asked questions

What's the best AI prompt for writing a professional email?

Start with role, context, task, constraints, and desired format. Something like: "I'm a [role] writing to [recipient role] about [situation]. Write a [tone] email that [does X]. Keep it under [word count]." The more specific you are, the less editing you'll have to do afterward. Vague prompts produce vague emails.

Is it safe to paste work emails into ChatGPT?

It depends on your company's policy, and you should check it. Don't paste anything with customer PII, HR details, legal content, medical information, or financial data tied to real names. Replace specific names and numbers with placeholders when in doubt. When it comes to confidential or sensitive threads, use your own judgment and write those yourself.

Will people be able to tell my email was written by AI?

If you paste the output without editing, yes, sometimes. AI has patterns: it over-explains, adds phrases like "I hope this finds you well," and can sound weirdly formal. The fix is to read the draft, cut the filler, and make it sound like you. Use AI for the structure, then rewrite the parts that don't sound human.

What's the difference between AI writing my emails and AI helping me write emails?

The difference is your judgment on the output. AI writing your emails means you paste whatever comes out and hit send. AI helping means you use it to get a draft faster, then read it, fix what's wrong, and send something you've actually approved. The second version is what these prompts are designed for.

Do I need a special AI email tool or will ChatGPT work fine?

ChatGPT or Claude works fine. Most dedicated AI email tools are just wrappers around the same underlying models. Save the money, learn to write better prompts, and use one general tool well. That's it.

How do I follow up on an email without sounding desperate?

Keep it short, reference the original, make it easy to respond, and skip the apology. "Following up on my email from Tuesday about [topic]. Happy to answer any questions, or let me know if [decision] isn't the right path." Under 60 words. Direct. Done. The prompt in section four above handles this with one paste.