Right, let’s be clear about something before we start: I’m not going to show you how to get an AI to send emails on your behalf without you looking at them first. That’s not what this guide is. If you want an assistant that fires off replies while you sleep, this isn’t it, and honestly, I’d be wary of anyone promising that anyway.
What I am going to show you is how to get AI to do the boring bit, the drafting, the staring at a blank message wondering how to phrase something, while you stay completely in charge of what actually leaves your outbox. AI drafts. You send. That’s the whole deal.
What you’ll be able to do
By the end of this you’ll have a proper workflow for getting emails drafted quickly, whether that’s a follow-up to a client, a group update, or one of those tricky messages where you need to say no without sounding like a jerk. The AI does the heavy lifting on wording. You do the reading, the checking, and the clicking send.
You’ll also end up with drafts that sound more like you than like a generic assistant, which matters more than people think. A lot of AI-written emails have a certain flatness to them, you know the type, overly polished, slightly robotic, everyone’s inbox is full of them now. Getting past that is part of what we’re covering.
Before you start
You’ll need an AI assistant account already, something like ChatGPT, Claude, Gemini, or Copilot. If you’re using Gmail, Gemini’s writing tools are built right into the compose window. If you’re on Outlook, Copilot does something similar. Nothing fancy required, just an account and an email client you already use.
The one rule that overrides everything else in this guide: AI drafts, you send. Every workflow below assumes a human, that’s you, reads the draft before it goes anywhere. Don’t wire this up to auto-send. Don’t give an assistant your email password and tell it to “handle things.” That’s not a productivity hack, that’s a mistake waiting to happen, and honestly there isn’t a mainstream tool built for that anyway, at least not one I’d trust.
Get set up
There are a few different routes here depending on what you’re trying to do, so I’ll go through them in the order I’d actually use them.
If you care about the emails sounding like you specifically, not like a helpful robot, I’d start with ScriptGrain. It’s ours, so take that as you will, but the reason I recommend it here is specific: it measures your actual writing rather than just being told “sound like me” and hoping for the best. Email is one of its content types. The free tier gives you one profile and one draft, enough to test whether it actually captures your voice before you commit to anything. There’s also an MCP server, which means if you’re using Claude, it can draft directly using your measured voice profile rather than a vague instruction typed into a chat window.
Compare that with just telling ChatGPT “write this in my voice” or “sound like me.” It’ll do its best, but there’s no measurement behind it, nothing it’s actually learned from your past writing. Ask it three times across three sessions and you’ll get three slightly different versions of “you.” It drifts. That’s not a criticism of ChatGPT, it’s just not built to hold a consistent voice profile the way a dedicated tool is.
If you’re already living in Gmail, the built-in “Help me write” feature (powered by Gemini) sits right in the compose box. You type a rough instruction, it generates a draft, you edit it in place before sending. No extra tool needed, no leaving your inbox.
Outlook users get something similar with Copilot, drafting assistance built into the compose experience, generating text you can then edit and refine before it goes anywhere.
And then there’s the plain workflow: open ChatGPT or Claude in a separate tab, throw in some bullet points about what you need to say, get back a draft, then copy it across into your email client and tidy it up. Simple, works everywhere, no integration required. It’s basically what I use for anything that doesn’t need my specific voice, quick internal notes, a message to someone I don’t know well, that sort of thing.
For anything you send repeatedly, think onboarding emails, recurring check-ins, the same template with different names dropped in, a proper template plus mail-merge setup will save you more time than asking AI to write it fresh each time. Draft the template once (with AI, if you like), then merge the details in. No point regenerating the same email fifty times with minor variations.
Try it yourself
Here are three prompts to get you started. Copy them, adjust the brackets, and see what comes back.
A professional follow-up, the kind you send after a meeting that’s gone quiet:
Write a short follow-up email to [name] about [topic we discussed].
It's been [X days] since we spoke and I haven't heard back.
Keep it friendly but brief, no more than 4 sentences, and end with
a clear next step I want them to take: [what you want them to do].
A brief update to a group, where you need to sound clear but not stiff:
Write a short update email to my team about [project/topic].
Cover these three points: [point 1], [point 2], [point 3].
Keep it under 100 words, no corporate jargon, and make it sound
like a normal person wrote it, not a press release.
A tricky message where tone matters more than usual, say, pushing back on a request:
I need to write an email declining [request], but I don't want to
sound harsh or dismissive. Here's the context: [brief explanation].
Draft something that's warm but firm, keeps the door open for future
collaboration, and doesn't over-apologise.
If you’re using ScriptGrain for voice-matched drafts, the process is a bit different, you’re not writing a prompt from scratch each time, you’re feeding it the topic and letting the measured profile do the tone work. Worth trying once you’ve got a profile set up, just to compare against the raw prompt approach above.
Check the result
Don’t just read a draft and hit send because it looks fine at a glance. Run it through a few actual checks first.
Does it sound like you? Read it out loud, genuinely, out loud. If it sounds like something a stranger would write, that’s your cue to edit it, not send it as-is.
Are the facts right? AI doesn’t know your actual meeting time, your actual client’s actual preferences, or what was actually agreed last Tuesday. It’s guessing based on what you told it, and it’ll happily guess wrong if your bullet points were vague.
Names and dates: check every single one. This is the single most common place these drafts go wrong, a name spelled slightly off, a date that’s drifted a day because of a vague instruction. Takes ten seconds to check, saves an awkward follow-up email apologising for the first one.
Attachments: if the draft references something being attached, actually attach it before you send. Obvious, but it’s exactly the kind of thing that slips through when you’re moving fast.
And finally: is anything missing that only you’d know? AI can’t read your inbox history unless you’ve explicitly given it that context. If there’s a detail from a previous conversation that matters, add it yourself.
If it doesn’t work
The biggest thing to get right here isn’t technical, it’s about what you’re willing to hand over.
Don’t paste other people’s personal data into a public AI assistant. Someone’s home address, a client’s financial details, medical information, anything sensitive about a third party, keep it out of the prompt entirely. Public assistants aren’t confidential by default in the way your own inbox is, and once you’ve pasted something in, you’ve lost control of where it’s gone.
If a draft comes back sounding wrong, generic, over-formal, weirdly cheerful when the topic is serious, don’t just accept it and edit around the edges. Sometimes it’s quicker to write the email yourself from scratch, especially for anything emotionally sensitive: a complaint, a resignation, a difficult personal message. AI is good at structure and phrasing. It’s not good at knowing exactly how upset you are, or exactly how much you want to soften something.
Check what permissions you’ve given any tool that connects to your actual inbox. If you’ve linked Gmail or Outlook to a third-party assistant, know what it can see and what it can do, and make sure “send” isn’t one of the things it’s allowed to do without you.
Questions people ask
Can AI send emails for me automatically?
No. The rule that overrides everything else is: AI drafts, you send. Don't wire this up to auto-send, and don't give an assistant your email password and tell it to "handle things" — there isn't a mainstream tool built for that anyway.
Which AI tool should I use to draft emails?
You'll need an AI assistant account such as ChatGPT, Claude, Gemini or Copilot. In Gmail, the built-in "Help me write" feature sits in the compose box; Outlook users get similar drafting assistance from Copilot. Or just open ChatGPT or Claude in a separate tab and copy the draft across.
Is there a free way to get AI to draft emails in my voice?
ScriptGrain's free tier gives you one profile and one draft, enough to test whether it actually captures your voice before you commit to anything. It measures your actual writing rather than just being told "sound like me".
What should I not paste into an AI when drafting an email?
Don't paste other people's personal data into a public AI assistant — someone's home address, a client's financial details, medical information, anything sensitive about a third party. Public assistants aren't confidential by default, and once pasted, you've lost control of where it's gone.
How do I check an AI email draft before sending?
Read it out loud to see if it sounds like you, check the facts, and check every name and date — that's the most common place drafts go wrong. Attach anything the draft references, and add any detail from previous conversations that only you would know.
Keep exploring
If you want the fuller picture on managing your inbox with AI rather than just drafting individual emails, have a look at “How to get AI to handle my emails”. And if the voice-matching side of things interests you, specifically getting AI to actually sound like you rather than like an assistant, “How to get AI to sound like me” goes into that in more depth.
Sources and review notes
- Gmail Help — Help me write with Gemini: https://support.google.com/mail/answer/13955415
- Microsoft Support — Draft an email with Copilot in Outlook: https://support.microsoft.com/en-us/office/draft-an-email-message-with-copilot-in-outlook-3eb1d053-89b8-491c-8a6e-746015238d9b
- ScriptGrain (email is one of its content types; MCP server): https://scriptgrain.com/
- Model Context Protocol: https://modelcontextprotocol.io/
Review date: 15 September 2026 — every source above was opened and checked against the text on that date.
Disclosure: ScriptGrain is one of our products — this site is made by the same studio, Adapt Progress Evolve. We have tried to compare fairly, and the alternatives named are real and worth a look.