Claude Prompts for Writing Long Emails Fast

The short version: Claude writes long emails fast when you give it a point of view, the actual facts, and a structure to follow, not just a topic and a "please write an email." Feed it bullet points of what you want to say, tell it who it's writing to and why, and ask for a specific length and tone. The output still needs editing, but it goes from blank page to 80% done in under two minutes.

Why most people get slow, mushy emails out of Claude

I've watched people type "write me an email about our new pricing" into Claude and then complain the result sounds like a corporate newsletter. That's not Claude's fault. It's a prompting problem. A vague request gets you a vague, over-long, over-polite email full of phrases like "I hope this email finds you well" and "we are excited to announce."

The fix isn't a magic prompt. It's giving Claude the same brief you'd give a junior copywriter: who is this for, what do they already know, what do you want them to do after reading it, and what facts or numbers must be in there. Skip that and you're just rolling dice.

The structure that speeds things up

Every long email prompt that works well has five parts. Miss two of them and you'll be rewriting half the draft yourself.

• Who it's from and who it's to, role, relationship, how formal or familiar.
• The goal, one sentence on what you want the reader to do or feel.
• The raw facts, bullet points, not prose. Dates, numbers, names, decisions.
• The shape, how many paragraphs, whether you want subheadings, whether it needs a sign-off with your name.
• The tone word, one or two words max. "Direct and warm." "Formal but not stiff." "Blunt, no fluff."

Put those five things in a single prompt and Claude has almost nothing left to guess at, which is exactly why the draft comes back usable instead of generic.

A worked example: the dreaded project delay email

Say you run a small web design agency and a client's site launch is slipping by three weeks because a third-party integration broke. You need to tell the client, explain why, and keep the relationship warm enough that they don't start calling other agencies.

A lazy prompt: "Write an email telling my client the project is delayed."

That gets you 150 words of apology soup. Instead, try this:

• "You're me, the founder of a web design agency, writing to a client called Priya at a mid-size retail brand. We've worked together for 8 months and the relationship is friendly but professional. The goal of this email: tell her the launch is moving from 15 February to 8 March, explain the integration issue without throwing our dev partner under the bus, and offer two ways we'll make it up to her (a free month of maintenance, and a priority slot on the next project). Facts to include: the delay is caused by a Shopify API change that broke our checkout integration, we found it during QA not after launch, we've already got a fix in testing. Structure: 4 short paragraphs, no bullet points, sign off as me with my first name. Tone: direct, accountable, warm, not grovelling."

That single prompt, roughly 120 words of input, produces a usable 250 to 300 word email in one go. The difference between that and the lazy version is night and day, and it took maybe 90 seconds longer to type.

Prompts you can copy and adapt

For a long client update email

"Write a client update email, roughly 300 words, four sections with short subheadings: progress this month, any blockers, what's happening next, and what we need from them. Client is [name], context is [one sentence]. Facts: [bullet list]. Tone: confident, specific, no corporate filler, no 'I hope this finds you well.'"

For a long sales follow-up

"Write a follow-up email to a prospect who went quiet after a demo three weeks ago. Reference the demo without being needy about it. Include one new piece of information they haven't seen: [fact, e.g. a new case study or price change]. End with a low-pressure, specific next step, not 'let me know if you have any questions.' Keep it under 180 words even though it's a long email topic, because long doesn't mean padded."

For a long internal team email

"Write an email to my team of 6 explaining a change to our process. Context: [bullets]. I want three sections: what's changing, why we're changing it, what they need to do differently starting Monday. Tone: direct, no apology for the change, treat them like adults."

For a tricky, long explanatory email

"Write an email explaining a complicated situation to someone non-technical. Facts: [bullets]. Assume they know nothing about [topic]. Use plain English, short sentences, no jargon. Length: whatever it needs to be to be clear, but cut anything that doesn't serve the explanation."

The uncomfortable bit nobody tells you

Here's what most "Claude prompt" listicles skip over: the reason these emails are slow to write by hand usually isn't the writing itself, it's that you haven't decided what you want to say. People sit staring at a blank screen not because typing is hard but because they're avoiding a decision, like how much to apologise, whether to admit fault, what the real ask is.

A prompt can't fix that for you. If you feed Claude a vague brief because you yourself haven't worked out the message, you'll get a vague email back, just faster. The speed only shows up once you've done the thinking. So the real productivity gain from these prompts is that they force you to write the bullet points first, which is the actual hard part, and then Claude does the sentence-level labour you were dreading. That's the honest trade: you still have to think, Claude just takes the typing off your plate.

Length controls that work

Claude will happily write 600 words when you wanted 200, especially on emotional topics like apologies or bad news, because it tends to over-explain to soften the blow. Three things fix this reliably:

• Give a word count range, not a vague "keep it short." "250 to 300 words" works better than "concise."
• Ban specific habits: "no restating what I just told you," "no summary paragraph at the end," "one ask only."
• Ask for a second, shorter version. "Now give me a 100 word version of the same email" takes ten seconds and often produces the better draft.

Which Claude model to use for this

For most long emails you don't need the most expensive model running. If you're choosing between Anthropic's current models for everyday writing, something like Haiku is fine for a first draft of a routine update, while Sonnet is worth it when the email is sensitive, like the delay example above, where tone matters more than speed. I've written a longer breakdown of Claude Sonnet vs Haiku if you want to work out which one suits your day to day email volume. And if you're on the free plan and wondering how many long email drafts you can generate before hitting a limit, it's worth checking what the free Claude plan includes before you assume you need to pay.

Save your best prompts so you're not rebuilding them every time

If you send the same type of long email repeatedly, like client updates, delay notices, or proposal follow-ups, don't retype the brief every time. Save your five-part structure as a template in a notes app, or if you're using Claude through a business setup, put your standard tone, formatting rules and common facts (your company name, your usual sign-off, how you refer to your team) into a project-level file so every new email prompt inherits them automatically. I've covered how that works in more detail in my piece on the CLAUDE.md file, which is the closest thing to setting a default voice for all your prompts at once.

When "fast" stops being the goal

Not every long email should be fast. A redundancy letter, a complaint response, a pricing increase to your biggest client, these deserve you sitting with the draft Claude gives you rather than copy-pasting and hitting send. Use Claude to get past the blank page and handle the sentence-level grind, then read it out loud before it goes anywhere near someone's inbox. If a line makes you wince when you say it aloud, it'll make the reader wince too.

If you're building prompting habits across your whole team rather than just for yourself, it's worth reading up on how Anthropic itself recommends structuring business prompts; I've pulled the key points together in my guide to Claude prompt engineering, which goes further into system prompts and context windows than this post needs to. And if your team is reaching the point where email drafting is just one small part of a bigger workflow problem, that's usually the sign you need real help setting it up rather than another prompt list, which is where working with an AI implementation coach tends to pay for itself.

Frequently asked questions

What's the single best Claude prompt for writing long emails fast?

There isn't one universal prompt, but the best format gives Claude five things: who it's to and from, the goal of the email, the raw facts as bullet points, the shape (paragraphs, length, subheadings), and a one or two word tone. That structure consistently beats any "magic" one-liner you'll find online.

Why does Claude write emails that are too long or too apologetic?

Claude tends to over-explain on emotional or sensitive topics because it's trying to soften bad news, which adds length without adding value. Fix it by giving a specific word count, banning summary paragraphs explicitly, and asking for a second, shorter version to compare.

Should I use Claude for sensitive emails like layoffs or complaints?

Use it to get past the blank page and handle the sentence-level work, but read the final version aloud before sending anything sensitive. These are the emails where "fast" shouldn't be the priority, and a human read-through catches tone problems Claude can't.

Do I need the paid version of Claude to write long emails?

No, the free plan handles occasional long emails fine, but if you're drafting several a day across a team, check the usage limits on the free plan before assuming you're covered, since heavy daily use is where people tend to hit the ceiling.