The problem with AI-written email is not that it's bad. The problem is that it sounds like everyone else's AI-written email. The corporate warmth, the "I hope this message finds you well," the three-paragraph structure that builds to a politely stated request. Recipients are pattern-matching this now. The emails that get responses are the ones that feel like a specific person wrote them.

The prompts below are designed to fix this. Each one is structured to produce a draft that you can edit into something that sounds like you, rather than something that sounds like a professional email generator. The key additions that make the difference: specifics about the person you're writing to, your actual tone, and a constraint on length.

Difficult Conversations

These are the emails most people spend 20 minutes staring at before writing. The prompts help you get a draft quickly so you can spend your time on the judgment calls, not the blank page.

Prompt 1: Pushing back on a decision you disagree with

"Draft an email pushing back on [decision] made by [person/team]. I disagree because [your specific reason]. I want to express my concern clearly without being dismissive of the reasoning behind the decision. I'm willing to be persuaded but I want to be heard. Keep it direct, under 200 words, professional but not deferential. Don't start with 'I hope this finds you well.'"

What makes it work: the instruction "professional but not deferential" signals that you want actual pushback language, not softened disagreement that reads like agreement. Always edit the specific argument for your situation; the AI won't have your context.

Prompt 2: Addressing a conflict with a colleague

"Draft a professional email to a colleague addressing a tension between us. The situation: [brief factual description, 2-3 sentences]. My goal is to name what happened without assigning blame, express what I need going forward, and keep the working relationship intact. Warm but direct. Under 150 words. Don't use passive-aggressive language or over-apologize."

The "don't over-apologize" instruction prevents the common AI tendency to smooth over everything until the email communicates nothing.

Prompt 3: Setting a boundary with a client who keeps scope-creeping

"Draft an email to a client who has repeatedly added requests outside our agreed scope. The original scope was [describe]. The additions have been [describe]. I need to acknowledge the requests, explain that they fall outside scope, and offer a path forward (either an amendment to the contract or a separate project). Firm but not hostile. Under 200 words. Don't apologize for holding the boundary."

Cold Outreach

Cold email fails for one consistent reason: it's about the sender. Effective cold email is about the recipient.

Prompt 4: Cold email to a potential client

"Write a cold outreach email to [person] at [company]. They are a [role] at a company that [brief description]. My specific reason for reaching out: [one specific relevant thing about them or their company]. What I offer that's relevant to them: [specific, not generic]. One clear ask at the end (15-minute call, reply to a question, etc.). Under 120 words. No filler opening. First sentence should be about them, not me."

The "first sentence about them, not me" instruction is the most important. AI defaults to leading with the sender's introduction. Most cold emails that work lead with something the recipient finds interesting about themselves or their work.

Prompt 5: Cold email for a job you want badly

"Write a cold email to [person] at [company] about a role I'm interested in. I'm not sure if it's open. The role I'm hoping for: [describe]. The most relevant thing I've done: [one specific example, 1-2 sentences]. Why this company specifically: [actual reason, not 'I admire your mission']. End with one question that starts a conversation rather than a request to review my resume. Under 150 words."

Prompt 6: Re-engaging a lapsed contact

"Write an email re-engaging someone I know professionally but haven't spoken to in [timeframe]. We last interacted around [context]. I'm reaching out because [honest reason]. I don't want to be transactional about it, but I do have an ask eventually. Start with something genuine. Brief, under 100 words. Don't fake enthusiasm for things I don't actually know about them."

Follow-Ups

Follow-up emails are where persistence and awkwardness blur. Good ones are confident and short. Bad ones are apologetic and long.

Prompt 7: Following up after no response

"Write a follow-up email to [person] who hasn't responded to my previous email about [topic]. It's been [timeframe]. I want to follow up without being passive-aggressive or overly apologetic. Reference what I asked in the original email. One clear question or call to action. Under 80 words. Don't start with 'Just following up.'"

"Don't start with 'Just following up'" is crucial. That opener signals low confidence and is one of the most common phrases recipients tune out.

Prompt 8: Post-meeting follow-up

"Write a follow-up email after a meeting with [person] about [topic]. The meeting happened [when]. Key things discussed: [2-3 bullets]. What I'm doing next: [your action]. What I need from them: [specific ask or confirmation]. Under 150 words. Structured and specific. Not effusive."

Prompt 9: Following up on a proposal or quote

"Write a follow-up email on a proposal I sent [timeframe] ago to [person] at [company]. I haven't heard back. I want to ask if they have questions, without being needy. I also want to add one piece of value or new information since I sent the proposal: [add something specific if you have it, or ask the AI to flag this gap]. Under 100 words. Confident, not desperate."

Feedback

Feedback emails are hard because the recipient needs to receive the message clearly without feeling attacked. AI is useful here for calibrating tone once you've decided what you actually want to say.

Prompt 10: Giving critical feedback professionally

"Draft a professional email giving feedback on [deliverable/behavior/situation] to [person]. Specific feedback: [your actual observation, as concretely as possible]. I want to be direct without being unkind. The relationship is [describe: peer, report, client]. My goal is behavior change, not to make them feel bad. Under 200 words. Lead with the specific observation, not a compliment sandwich."

"Not a compliment sandwich" is intentional. The compliment-criticism-compliment structure is so overused that people have learned to hear only the compliments and dismiss the middle. Direct feedback delivered respectfully lands better.

Prompt 11: Asking for feedback on your own work

"Write an email asking [person] for specific feedback on [your work/proposal/project]. The work: [brief description]. What I specifically want to know: [2-3 specific questions, not 'any thoughts?']. I want them to feel like their time is worth spending here. Under 100 words. Specific questions, not open-ended."

Bad News

Bad news emails are best when they're direct, explain the situation clearly, and don't over-explain or over-apologize.

Prompt 12: Declining a request or invitation

"Write an email declining [request/invitation] from [person]. I'm declining because [real reason, even if I soften it in the email]. I want to be honest without being blunt. I want to preserve the relationship. Optional: offer an alternative if there's a natural one. Under 100 words. Don't over-explain the decision."

Prompt 13: Delivering a missed deadline or disappointing update

"Write an email telling [person] that [deliverable] will be late by [timeframe], or that [project] hit a problem. The situation: [factual description]. I want to: take responsibility without over-apologizing, explain what happened briefly, give a revised timeline or next step, and end with confidence, not groveling. Under 150 words."

Prompt 14: Ending a professional relationship

"Write an email ending a [client relationship / working arrangement] with [person]. I need to stop working with them because [general reason, can be tactful]. I want to: be clear that it's ending, give reasonable notice if appropriate, thank them for the work if genuine, and leave no ambiguity about the decision. Under 150 words. Professional and final."

Prompt 15: Delivering news you don't want to deliver

"I need to tell [person] that [news: budget cut, project cancellation, rejection, organizational change]. They will be disappointed. Write an email that: delivers the news in the first two sentences (no burying the lede), explains the context briefly, acknowledges the impact if genuine, and if there are next steps offers them. Under 180 words. Direct, not cold. Don't soften the news so much that it's unclear."

Making These Sound Like You

Every prompt above will produce a serviceable draft. None of them will produce an email that sounds exactly like you on the first try. The things to edit after generating:

The goal isn't to publish the AI output. It's to spend five minutes editing a strong draft instead of 20 minutes staring at a blank email compose window.