Skip to main content

I Let an AI Draft My Email Replies for a Month. Here's What It Got Right (and Where I Still Type It Myself)

I used to treat "AI can write your emails now" as a solved problem, the kind of feature you turn on once and never think about again. Then I actually tried leaning on it for a full month — not just the odd smart-reply suggestion, but letting an AI draft actual responses to actual people — and it turned out to be way more uneven than the demos make it look.

This isn't a "these five prompts will change your life" post. It's closer to a field report. Some of what I found will save you real time. Some of it will just annoy you, and I'd rather tell you that upfront than let you find out the hard way in a reply-all thread.

A person typing on a laptop in a bright, modern office setting, showing productivity and technology.

Photo by cottonbro studio on Pexels

What I actually tested

I used the AI drafting features already built into Gmail and Outlook, plus a general-purpose assistant (Claude or ChatGPT, pasted in manually) for anything longer or trickier. No separate email-AI startup, no browser extension — just tools most people already have access to.

The rule I set for myself: if the AI drafted something, I had to at least skim and edit it, never blind-send. That sounds obvious, but it's worth stating because the whole pitch of these tools is speed, and speed is exactly what tempts you to skip the read-through.

Where it genuinely saved time

For a specific category of email, this worked better than I expected: short, low-stakes, format-predictable replies. Things like:

  • Confirming a meeting time someone already proposed
  • Politely declining an invite with a one-line reason
  • Acknowledging receipt of something ("got it, thanks, will review by Friday")
  • Turning three bullet points I typed into a properly formatted paragraph for a client-facing email

Say you get a Tuesday morning inbox with fourteen emails, and eight of them are basically "yes," "no," or "got it, thanks." That's the exact pile where an AI draft-and-edit loop beats typing from scratch. I wasn't saving five minutes per email. I was saving maybe forty-five seconds each, but across eight emails, that adds up to something you actually notice by the end of the week.

The other place it helped was tone-smoothing. I'll draft something quickly in my own blunt style, then ask the AI to make it "warmer but not fake," and it does a decent job stripping out the accidental curtness without turning it into corporate mush. I still edit the output, but starting from a reasonable draft beats starting from a blank box.

Where it fell apart

Anything involving actual judgment calls was where the AI drafts went sideways. A few recurring failure patterns:

It doesn't know what you've already agreed to. If a thread has history — prior commitments, a number you already quoted, a deadline you already pushed back once — the draft will confidently ignore all of it unless you paste in the whole thread every time, which defeats the purpose.

It over-explains. Left alone, AI drafts tend to add a sentence of justification where a human would just say no. "Unfortunately I won't be able to make it" becomes three sentences about scheduling conflicts nobody asked about. I found myself deleting more than I kept in these cases.

It flattens your actual opinion. For emails where I had a real, specific take — pushback on a proposal, a disagreement about scope — the AI draft would smooth it into something so diplomatically vague that the point got lost. That's the one I care about most, honestly. If the whole reason you're writing is to say something, and the tool's instinct is to sand off anything that could sound like disagreement, you've lost the point of the email.

It fabricates confidence. A couple of times it drafted a reply that stated something as fact — a date, a policy, a "yes we can do that" — that I hadn't actually confirmed. I caught it because I read the draft, which is exactly why I don't trust anyone who tells you to auto-send these.

A worked example

Close-up of businessman typing on a laptop in a modern office setting, showcasing remote work.

Photo by Andrea Piacquadio on Pexels

Say you get an email from a vendor asking to bump a deadline by two weeks, and you're only okay with one week. A generic AI draft, given just that prompt, will often produce something like: "Thank you for reaching out. While we understand scheduling can be challenging, we'd like to propose an alternative timeline that better aligns with our current commitments." That's technically fine. It's also mush — it doesn't say one week, doesn't say why, and reads like it was written by nobody in particular.

What worked better was giving it the actual constraint up front: "Say no to two weeks, offer one week instead, keep it under three sentences, don't over-apologize." With that framing, the draft was genuinely close to something I'd send unedited. The lesson wasn't "AI drafting doesn't work" — it was that the tool needs the actual decision from you before it starts, not after.

The habit that made this worth keeping

The thing that made the month worthwhile wasn't a setting or a prompt trick. It was a rule I forced on myself: never let the AI make the call, only let it handle the wording. I decide yes or no, I decide the number, I decide the tone I want. The AI's job is turning that decision into clean sentences faster than I'd type them myself. The moment I let it guess at the decision too, the quality dropped fast.

That's roughly the same lesson I landed on when I [wrote about time blocking](#) a while back — the tool works when it executes a decision you've already made, and it works a lot worse when you ask it to make the decision for you.

FAQ

Is it safe to let AI draft emails that include sensitive information?

Be careful here. If you're pasting client details, financial figures, or anything confidential into a general-purpose AI tool to get a draft, check your company's data policy first. Built-in email provider AI features usually operate within your existing account's privacy terms, but a separate tool you paste text into is a different situation — treat it like you would any third-party service.

Does AI email drafting actually save time, or does editing cancel it out?

For short, predictable replies, the time savings are real, even after editing — you're mostly deleting and rearranging rather than writing from scratch. For long or high-stakes emails, editing often takes about as long as writing would have, so the net savings shrink to close to zero. Match the tool to the email, not the other way around.

What's the single biggest mistake people make with these tools?

Sending without reading. It sounds too obvious to mention, but the entire appeal of AI drafting is speed, and speed is what makes people skip the one step that catches fabricated confidence or flattened opinions. If you only take one thing from this, take that one.

The takeaway

AI email drafting isn't the productivity miracle it's pitched as, but it's not nothing either. It's a decent typist that's bad at judgment. Once I stopped expecting it to decide anything and started using it purely to turn my own decisions into clean sentences, it earned a permanent spot in my inbox workflow — just not an unsupervised one.

Keep reading

Comments

Popular posts from this blog

Every To-Do App Works for the First Two Weeks — Here's What Decides the Rest

Photo by RDNE Stock project on Pexels The Honeymoon Phase Is Not the Test Here's a pattern I've watched play out dozens of times, including in my own phone: someone downloads a new task manager, spends a Saturday afternoon setting it up beautifully, and for about two weeks it's genuinely great. Everything's captured. Everything's organized. Then, sometime around week three, tasks start piling up unchecked, half the projects are stale, and the app quietly turns into another icon you feel guilty about. If this sounds familiar, your instinct is probably to blame the app. Todoist wasn't flexible enough. Things was too rigid. Notion took too much setup. So you switch, rebuild everything, and get another two good weeks. I've seen people cycle through four or five systems in a year this way, and each time they walk away more convinced that the "right" tool is still out there somewhere. It usually isn't the tool. The apps that survive long-...

The 20-Minute Weekly Reset That Keeps a Productivity System From Rotting

Photo by RDNE Stock project on Pexels The system isn't broken. It's just never reviewed. Here's a pattern I've watched play out with almost every productivity app I've tried: week one, it's magic. Everything gets captured, tagged, scheduled. Week three, there are 40 tasks with no due date sitting in an "Inbox" that nobody opens anymore. Week six, you've quietly gone back to a sticky note. I've written before about how every to-do app works great for the first two weeks and then something decides whether it survives past that. What I didn't spell out then is what that "something" usually is. It's rarely the app. It's the absence of a recurring moment where you actually look at everything you've captured and decide what to do with it. That moment has a name in productivity circles: the weekly review. It sounds like homework, and most explanations of it make it sound like a 90-minute audit of your entire l...