How I answer 100 emails a week with AI (without sounding like a robot)

I run WriterPi solo. Between customer support, potential-customer emails, invoices, contract questions, and personal stuff, I get about 100 emails a week that need a real reply. Not one-liners — actual thought-out responses.

Two years ago this would've been a full afternoon a day. Now it's about 40 minutes. Here's exactly how, without any of the AI-fluff you usually get in workflow posts.

The three rules I never break

Before any tool talk — the philosophy.

1. AI drafts. I send. Every email that leaves my inbox has been touched by me. Not just skimmed — actually edited. This is the difference between using AI well and getting complaints.
2. AI never handles feelings. A grief email from a customer whose company shut down. A friend going through a divorce. An angry customer who deserves a real apology. These get zero AI. Wrong tool for the job.
3. Specifics are always mine. Names, dates, prices, promises, decisions — I type these myself. AI is good at structure and phrasing, not memory or judgment.

Those three rules alone explain why my customers keep telling me they can't tell my replies are AI-assisted. They're not, in the ways that matter.

The workflow, step by step

Step 1: Batch, don't drip

I don't reply to email as it arrives. Twice a day — 11am and 4pm — I open Gmail and clear the inbox. This alone saves an hour because there's no context-switching penalty.

Step 2: Triage in 30 seconds

Each thread gets one of four tags in my head:

• Reply now (30 sec) — one-liners. Just type it.
• Reply now (AI-drafted) — needs a real response but the shape is obvious.
• Reply later (needs thought) — the ones that need a walk before I answer.
• Delete / archive — most of them.

Step 3: The AI-drafted ones

For the AI-drafted category (~60% of my emails), the workflow inside Gmail is:

1. Open the thread.
2. Open the WriterPi sidebar. Turn on Page toggle.
3. Type a specific ask (below).
4. Read the draft. Delete anything generic. Add specifics.
5. Paste into Gmail's reply box. Send.

Total time per email: 60-90 seconds. Without AI, closer to 4-5 minutes each.

The prompts I actually use

These are copy-paste from my most-used list. No fancy prompt engineering — just plain requests with specifics.

Accepting

Reply saying yes to the meeting on [day]. Confirm the time.
Mention I'll come with the doc pre-read. Under 3 sentences.

Declining politely

Politely decline this pitch. Don't burn the bridge.
Suggest they reach back out in Q1 next year if the offer changes.

Chasing an unpaid invoice

Follow up on the invoice they haven't paid. This is the
second reminder. Firm but not aggressive. Under 4 sentences.

Asking for clarification

Reply asking them to clarify what deliverable they mean
by "the deck". List 3 specific questions I still need answered
before I can start.

Answering a technical question about the product

Draft a reply explaining how [feature] works. Keep it
concise, non-technical language. Mention that if they want
more detail, they can email me back.

Delivering bad news

Draft a reply telling them we can't hit the deadline they
asked for. Offer a realistic alternative date. Take responsibility
without over-apologising. Under 4 sentences.

The editing pass — 30 seconds that matters most

The AI draft always needs three passes:

1. Cut anything generic. "Thank you for reaching out" — delete. "I hope this email finds you well" — delete. AI loves fluff. I delete every filler sentence.
2. Add one specific detail. Their name, a project reference, an inside joke from last week, the specific number we discussed. This is what makes it feel human.
3. Read it out loud. Actually mouth the words. If it sounds like something a stranger wrote, rewrite one sentence in my own voice. Usually the first sentence.

These three passes take about 30 seconds. They're the difference between AI-slop and a real reply.

Where the whole thing breaks down

Honest failures:

• Really long email chains. When a thread has 8+ back-and-forth messages, AI misses subtle context. I read manually and reply manually.
• Emails from people I care about. Friends, family, my closest customers. Fully manual. The saved time isn't worth risking the relationship.
• Complaints. The customer wants to feel heard, and they can tell if you AI-drafted their complaint response. I write these myself, even the short ones.
• First contact with a new person. Setting the tone of a relationship matters. AI works better once we have a few emails of context between us.

The metrics that matter

People love asking "how much time does AI save?". The honest answer for me:

• Email time went from ~9 hours/week to ~4 hours/week
• Reply quality (measured by customer NPS on support emails) went UP, not down
• Response time went from 24-48 hours to 4-8 hours
• My cognitive load at end of day is dramatically lower

The last one is the real win. Email used to leave me drained. Now it's just a task I do twice a day and forget about.

— sane. If you have your own AI email workflow that works, I'd love to hear it. hello@writerpi.com.