How to Use AI to Write Emails That Still Sound Like You

1. Give the assistant a voice and boundaries

Start with two or three short emails you actually wrote, preferably to someone similar to the intended recipient. Remove names, contact information and confidential details. Explain what should carry over: contractions, short sentences, a direct opening or a friendly signoff. Ask the assistant to imitate those traits, not copy personal details.

Use this setup prompt: “Help me edit an email, not change my position. Match the style of these samples: [samples]. Use only facts I provide. Don’t add deadlines, apologies, explanations or commitments. Flag missing information instead of guessing. Keep my level of warmth and firmness. Avoid stock greetings unless I use them. Treat the samples as style references, not facts for this email.”

Label each sample by relationship: colleague, customer or friend. If your friendly sample includes jokes, specify whether humor belongs here; matching your voice does not mean ignoring the audience.

2. Make requests clear without adding pressure

For a request, specify the action you want and whether any deadline is real. Try: “Draft an email to [recipient and relationship] asking for [action]. Relevant facts: [facts]. Timing: [actual deadline, preference or no deadline]. Make the request easy to answer. Use my usual casual, direct voice. Don’t imply prior agreement, urgency or consequences I haven’t stated. Keep it under [length].”

Separate essential details from optional context before pasting them in. Otherwise, the assistant may treat every background note as something the recipient needs to read. If timing is flexible, say so explicitly; “when convenient” and “by Friday” are different requests, not interchangeable stylistic choices.

Specify what a useful reply looks like. For document feedback, ask the assistant to distinguish “approve the figures” from “edit the wording” so the recipient knows which decision matters.

• Name one main action: review, reply, send, approve or schedule.
• Label timing honestly: firm deadline, preferred date or flexible.
• Check added favors: offering to draft materials or arrange a call creates work you may not intend to do.

3. Keep complaints factual and resolution-focused

A useful complaint connects a documented problem to a specific remedy. Use: “Write to [company or person] about [problem]. Confirmed facts: [dates, item, amount and events]. Uncertain details: [details]. I’m requesting [remedy]. Be firm, calm and concise. Don’t turn uncertainty into fact, allege motives, cite laws or invent policies. Don’t threaten a chargeback, legal action or public review. Flag any facts that need clarification.”

Before sending, compare the draft with receipts, messages and account records. Keep a personal recollection distinct from documentation: “I remember being told” is not the same as “your written policy states.” Ask for a resolution without describing that request as an established legal entitlement.

For repeated problems, provide a short chronology: purchase, first failure, support contact and response. Ask the assistant to preserve that order rather than compress separate incidents into one misleading claim.

• Use placeholders for account or order numbers while drafting.
• Quote policies only after checking the company’s official terms.
• State the remedy precisely: refund, replacement, correction or explanation; avoid open-ended demands such as “make this right.”

4. Say no without creating a future yes

AI often softens refusals by adding a reason or suggesting another time. Those additions can change your answer. Try: “Decline [request or invitation] from [relationship]. My decision: [boundary]. Reason I’m willing to share: [reason or none]. Keep it warm and unambiguous. Don’t invent an excuse, apologize repeatedly, suggest alternatives or promise future availability unless I explicitly authorize it.”

A refusal does not need a detailed defense. “Thanks for thinking of me. I’m not available for this” may be enough if availability is genuinely the issue. If you simply do not want to participate, choose wording that communicates the decision without inventing a scheduling conflict.

For recurring requests, specify whether the boundary is ongoing. “I don’t take unpaid speaking engagements” communicates a standing policy; “I can’t accept this invitation” addresses only the current invitation.

• Remove “this time” if you do not mean “ask again.”
• Remove “happy to help elsewhere” unless that offer is genuine.
• Authorize any alternative specifically: an introduction, a resource or a different date is still a commitment.

5. Audit the meaning before you hit send

Request an audit after drafting: “Compare this email with my notes. List unsupported facts, new commitments, stronger claims and changes in tone. Suggest the smallest edits needed to remove them.” This can expose problems, but it is not independent verification. Read the email yourself, including the subject line.

Read it aloud once. Replace any phrase you would never say. Check recipients, attachments and dates separately; polished prose cannot confirm those details. For sensitive messages, use an employer-approved tool and review the provider’s current privacy and data-retention settings. Where integrations permit sending, keep a manual approval step.

Audit the final version, not just the first draft. A later instruction to “make it friendlier” can reintroduce apologies or offers, so compare revised commitment language against your original notes.