AI Email Assistant: From Rough Notes to a Reviewed Draft

An AI email assistant turns scattered notes into a clear message. Provide the facts, explain what the recipient needs to do, generate a draft, and review it before sending it yourself.

The main challenge is not grammar. It is preserving meaning. A fluent draft can quietly turn an estimate into a promise, imply that work is complete, or add a reason you never gave.

The freelance client email below is illustrative. Its notes, drafts, and revisions are original examples, not tested outputs.

Give the assistant the facts and the desired outcome

Suppose your notes for a client update say:

Client: Rowan
Website design draft
Page headings finished
Still resizing mobile images
Need approved logo file from Rowan
Ask for it by Wednesday noon
If logo arrives then, expect to send draft Thursday afternoon
If later, need to reassess timing
Friendly, direct, no big apology

There are three kinds of information here:

• Established facts: the headings are finished; image work remains.
• A requested action: Rowan should send the approved logo by Wednesday noon.
• A conditional expectation: Thursday afternoon is the expected draft delivery if the logo arrives on time.

Keep those distinctions visible in the prompt. An assistant that compresses everything into “The website is almost ready and will arrive Thursday” has changed the message.

Replace identifying details with placeholders when possible. Include only necessary context, following your confidentiality obligations.

Use a prompt that protects the meaning

Here is a reusable email writing prompt:

Draft an email using only the facts below.

Recipient and relationship: [Name; client, colleague, friend, etc.]
Purpose: [What the recipient should understand.]
Requested action: [One specific action and any relevant deadline.]
Facts: [Verified details.]
Estimates or conditions: [Separate these from confirmed commitments.]
Tone: [For example, warm and direct.]
Length: [For example, around 100 words.]

Include a subject line. Do not invent progress, reasons, attachments,
prior conversations, or promises. Preserve all conditions attached to
timing. If a missing detail materially changes the message, ask me
instead of filling it in.

Put any questions or assumptions outside the draft.

Here, the purpose is a progress update; the requested action is “send the approved logo by Wednesday noon.”

Look at what a useful draft actually does

An appropriate illustrative draft would read:

Subject: Website draft update and approved logo

Hi Rowan,

The page headings are finished, and I'm still resizing the mobile images.

Could you send the approved logo file by Wednesday at noon? If I receive it by then, I expect to send the design draft on Thursday afternoon. If it arrives later, I'll need to reassess the timing.

Thanks, [Your name]

The email leads with progress, asks for one thing, and preserves the delivery condition without inventing completed work, attachments, or apologies.

Before sending, add dates and a time zone if needed to avoid confusion. Supply those details yourself.

Revise the draft without changing its commitments

“Make it better” leaves too much open. Specify the defect you want to fix:

Make this slightly warmer and easier to scan. Keep the same facts,
requested action, deadline, and conditional delivery estimate.
Do not add an apology or imply that Thursday delivery is guaranteed.

A revised middle section might be:

Could you send over the approved logo by Wednesday at noon? That would help me keep the draft moving toward Thursday afternoon. If the logo arrives later, I'll need to reassess the timing.

That sounds warmer, but it also makes the delivery expectation less explicit. Depending on the client, the original “I expect to send” wording may be clearer. More conversational writing is not automatically better writing.

For a final revision, ask: “Keep the friendly opening, but restore the explicit conditional delivery estimate.” Judge each version against the purpose of the message.

Review the parts most likely to cause trouble

Read the draft against your notes, not just for tone.

You can ask AI to compare a draft against your source notes, but that is an additional check. You still need to inspect the actual email, recipients, links, and attachments in your email application.

Use different prompts for different situations

For a follow-up, provide the date and substance of the previous request. Ask for one clear next action. Avoid “as we agreed” when there was no agreement.

For a difficult message, write down your boundary before drafting. For example: “I can provide one more revision within the existing scope.” Ask for calm language that preserves that boundary without adding accusations or concessions.

For a long thread, identify confirmed facts and unanswered questions. Request answers in order. Remove unrelated thread content before sharing it.

Draft in Elysona, then send the reviewed message yourself

Elysona offers a personal workspace with Sona for writing help, plans, and notes. Bring a short factual brief, refine the wording, and copy the reviewed draft into your email application to send yourself.

For choosing the right tool, see the personal AI assistant checklist. If writing keeps slipping down your task list, our AI weekly planning example shows how to reserve time for it.

Common questions about AI email drafting

How do I make the draft sound like me?

Describe specific preferences: short paragraphs, plain language, no exclamation marks, or a familiar sign-off. A brief, nonsensitive example of your writing can clarify the tone.

Can I ask the assistant to send the email?

This workflow ends with a reviewed draft. Copy it into your email application, verify the recipients and attachments, and send it yourself.

Open Elysona and start with the email you have been putting off: who it is for, what is true, and what you need to happen next.