Skip to main content
Using Claude

Writing Emails and Work Messages with Claude

Tell Claude the recipient, purpose, tone, and key points, and a work-email draft comes quickly. Plus tone tuning and pre-send checks.

ByUpdated
🌐 This article was machine-translated and may contain inaccuracies. Read the Korean original if in doubt.

When you write work emails or messages, Claude can produce a fast first draft. The key is to avoid a vague request like "just write an email" and instead give the recipient, purpose, tone, and the points it must include. The more context you provide, the fewer edits the draft needs.

🟢 Model references match the current lineup · model notice · Fable subscription
🟢 Model references match the current lineup · Claude Opus 5.5 / Claude Sonnet 5.5 / Claude Haiku 5.5 (higher tier: Claude Fable 5.1). This notice changes only when Anthropic ships a new model.

Fable 5 and 5.1 subscription (updated November 1, 2026): Claude Fable 5.1, released September 1, 2026, is the current Fable model and Fable 5 is now legacy. Plan terms are the same for both — Max, Ultra, and Team Premium plans include Fable at up to 50% of the weekly usage limit; Pro and Team Standard use usage credits ($10/M input, $50/M output tokens). The one-time $100 credit applied only to the Fable 5 transition and is not offered for 5.1. Some coding and debugging requests may be answered by an Opus model due to a security classifier (both models). See the Fable 5.1 guide and the Fable 5 availability guide for details.

Context speeds up your draft What to give · Recipient (client) · Purpose (scheduling) · Tone (polite) · Key facts (next Tue/Wed) → Claude Drafting → Email draft Hello, ... I'm writing to arrange a meeting time ... → Review, then send

What to tell Claude

A good draft starts with good input. Give Claude these four things and it will write an email that fits the situation.

  • Recipient: a manager, colleague, client, or customer — the relationship changes the wording and formality. Adding a line like "a client contact I'm reaching out to for the first time" makes it more accurate.
  • Purpose: be clear about whether it is a request, notice, apology, refusal, or thank-you. A clear purpose keeps the writing free of filler.
  • Tone: specify the mood you want — polite, formal, casual, or firm.
  • Key content: list the facts, dates, conditions, or amounts that must appear. State anything that cannot be missing up front.

Vague request vs. request with context

The same task produces very different quality depending on the input. Compare the two requests below.

Vague request vs. request with context Vague request "Write a client an email" Result · Generic, fits anyone · Key details missing · You explain again With context "To client Mr. Kim: arrange a meeting next Tue/Wed, polite tone, 3 paragraphs" Result · Greeting fits the relationship · Clear schedule and purpose · Polish and send

On the left, a vague request yields generic wording that fits anywhere, so you end up explaining again. On the right, giving the relationship, purpose, schedule, and tone at once produces a draft you can polish and send right away.

Adjusting the tone

The same content leaves a different impression depending on the tone you ask for. Name the mood in a single phrase — "politely", "concisely", "firm but not rude" — and Claude matches it.

Name the tone in a word Polite Formal wording Concise Just the essentials Firm Clear yet polite Warm A friendly tone

If the result is too stiff, ask for "a bit softer"; if it is too long, "in three sentences"; to make it more deferential, "raise the formality" — one more request and it is tuned.

Tips by situation

  • Request: be clear about what you want and by when, and add one sentence that eases the other person's burden.
  • Apology: lead with acknowledging the facts and the next steps rather than excuses.
  • Refusal: decline politely but offer an alternative where possible to preserve the relationship.
  • Thanks: name specifically what you are grateful for so it does not sound formulaic.

The draft is only a start

Rather than sending the first result as is, point out what feels off or missing and refine it. Specific requests like "make this part softer" or "add a line confirming the schedule at the end" let you match your own voice in one or two passes.

Check before you send

Even when you like the draft, check the following yourself before sending.

  • Confirm that facts such as names, dates, amounts, and schedules are correct.
  • It is safer not to put sensitive personal data or company secrets into your input.
  • Make sure the recipient and CC are right and no attachment is missing.

We recommend that a draft made by Claude is reviewed by a person before it goes out.

If you often write customer support replies, see answering customer inquiries with Claude.

To summarize an incoming email or a long document first and then write your reply, see summarizing documents with Claude.

Note: general principles for writing prompts are available in Anthropic's official docs (platform.claude.com/docs).

Was this helpful?

Keep reading

Claude's Skills Explore Tab Explained — What 60 Plugins Do, How to Use Them, and Whether They Run Automatically (Sept 2026)

What each plugin listed under Settings → Skills → Explore does, how you call it, and whether it can run with nobody around — based on the SKILL.md files of 60 installed plugins and Anthropic's official docs.

103

Can Claude Really 'One-Click' Write a Web Novel? What's Realistic

There's a hope that feeding Claude a premise is enough to get a finished serialized novel, but the tasks Claude is actually good at and what still needs a human writer are different things. Here's a realistic workflow using real features like Projects and Styles.

58

When Your Claude Character Drifts Mid-Conversation: Keeping Persona Context Stable with Projects

Long conversations can wear down a carefully built character setup. Here's how Claude's project instructions and knowledge features keep a persona consistent over time.

54

How to Save Claude Usage: A Practical Guide for Research and Experimentation

A few small changes to how you chat can meaningfully cut your Claude usage. Here's how project caching, turning off extended thinking, Claude Code commands, and the September 14 weekly limit change all fit together.

117