Use Claude for an email only after you know the purpose, confirmed facts and action you can legitimately request. Tone comes later. A polished message with an invented deadline is still wrong.
Build a send-state card
Suppose a client asks whether a reviewed report can arrive Tuesday. Your facts say QA finishes Wednesday, so the earliest approved delivery is Thursday.
| Field | Confirmed value |
|---|---|
| Recipient | Client project lead |
| Purpose | Correct the requested delivery date |
| Facts | QA completes Wednesday |
| Action | Confirm whether Thursday works |
| Forbidden claim | Do not promise Tuesday or offer an unreviewed draft |
| Attachment | None |
Draft, inspect and correct
Draft a concise reply from the send-state card.
Answer the delivery question in the first sentence.
Preserve the dates exactly. Do not offer an unreviewed version,
invent urgency or imply the client caused the timing.
Return a subject line, body and “Check before sending” list.A sound draft says the reviewed report cannot arrive Tuesday because QA completes Wednesday, offers Thursday, and asks whether that date works. If Claude writes “We will try our best to deliver Tuesday,” correct the unsupported promise directly. Do not ask only for a “more accurate tone.”
Compare the reply against the card
An authored example of an acceptable body is:
The reviewed report will not be ready Tuesday because QA completes Wednesday. We can send the reviewed version Thursday. Does Thursday work for your team?
The first sentence answers the client’s question. The second states only the approved alternative, and the last asks for confirmation without implying consent. Now test a bad draft: “We’ll send a preliminary copy Tuesday and the final report Thursday.” The Tuesday offer is not in the card. Delete it; do not soften it into “we hope to.”
If Thursday is only an estimate rather than an approved commitment, change the card before drafting. The email should then say the delivery date needs confirmation from the project owner. Claude cannot promote a hopeful schedule into a promise.
Use the right surface
A normal Claude chat is enough for one email. A maintained Project can help when repeated messages must follow the same current policy. A Microsoft 365 connector or add-in introduces account permissions and possible write actions, so check administrator controls before using it to send or update anything.
Final send review
Read the draft as the recipient. Check the address, reply-all state, names, dates, amounts, links, attachments and whether the requested action belongs to that person. Resolve every “Check before sending” item in the source record. Deleting the warning is not resolution.
| Send check | Pass condition |
|---|---|
| Recipient and reply-all | Only intended people receive the message |
| Dates and commitments | Tuesday is declined; Thursday has owner approval |
| Attachment and links | None is promised or silently added |
| Tone | Direct, without blaming the client for the schedule |
| Final authorization | A person reads the exact version being sent |
For a sensitive reply, ask someone who knows the account to check the draft against the source record. If you use a connector with send or write actions, separate drafting from sending and inspect the exact recipient, body and attachment list in the approved tool before release.
Questions about Claude for emails
Can Claude send the email for me?
Some connected products may support write actions when an administrator enables them. Draft first, inspect the exact message and keep sending under the approved process.
How do I keep my own tone?
Supply two short approved examples and describe the traits to preserve. Review the result instead of asking Claude to imitate a person from public material.
What should I do with a missing deadline?
Ask the owner for the date or state that it is not set. Do not let the draft turn a guess into a commitment.
Is this method suitable for newsletters?
No. Campaign email needs consent, audience rules, claim review and measurement. Use the marketing workflow for that job.
For reusable versions covering replies, follow-ups and clarification, open the work email prompt pack.