How to Use AI to Draft and Triage Work Email
On this page
TL;DR: Email is where most people first feel AI paying for itself, and where most people first embarrass themselves with it. The fix is to split the work: use AI for triage (what needs my attention, in what order) and for drafting (turn my five bullet points into a clean message), and keep two things human, the decision about what to say, and the final read before send. This page gives you the setup, a drafting prompt worth saving, and the failure modes to avoid.
Two different jobs, two different setups
“AI for email” is really two use cases with different risk profiles:
- Triage is read-only. The model summarizes threads, flags what needs a reply, and drafts nothing. Worst case, it misranks something. Low risk, immediate payoff.
- Drafting is write-adjacent. The model produces text that will go out under your name. Worst case, it commits you to something you never said. The review step is non-negotiable.
Treat them separately and you can adopt triage on day one while building better habits around drafting.
Setup
- Pick your surface. An assistant built into your mail client (Copilot in Outlook, Gemini in Gmail) can read threads directly, which makes triage nearly free. A standalone assistant (ChatGPT, Claude) requires pasting, but gives you full control over the prompt, better for drafting. Most people end up using both.
- Check the data rules first. Before pasting anything: does your plan exclude inputs from training? Does your company AI policy allow customer names, deal terms, personnel matters in prompts? If nobody has written that policy, the practical floor is: no customer personal data, no credentials, no legal or HR content.
- Save a triage prompt. Something you can paste a batch of emails (or point an integrated assistant at your inbox) with: classify each message as reply-needed / FYI / delegate / ignore, one line on why, and surface anything with a deadline. Run it once or twice a day, not continuously.
- Save a drafting prompt with your voice rules in it. This is the highest-leverage ten minutes in this whole setup, see the template below. Basic prompt engineering applies: the model needs your intent, the context, and the constraints, in that order.
- Set your personal review rule. Every AI draft gets a full read before send. For anything with money, dates, or commitments in it, read it twice, once for tone, once checking every factual claim against what you actually know.
Example prompt
The drafting prompt worth saving as a snippet:
“Draft an email from me. Context: [paste the thread, or describe the situation in 2-3 sentences]. What I want to say: [your points, as rough bullets, don’t polish them]. Recipient: [role and relationship, ‘my VP, skip-level, formal-ish’ or ‘vendor contact, friendly’]. Rules: Keep it under 150 words unless the content demands more. Match my register: direct, plain sentences, no exclamation marks, no ‘I hope this email finds you well.’ Do not add any facts, numbers, dates, or commitments I didn’t give you. If my bullets are ambiguous or missing something the reply needs, ask me instead of guessing. Give me a subject line and one alternative.”
Two parts of that do the heavy lifting. “Do not add facts I didn’t give you” targets the failure mode where a large language model helpfully invents a delivery date or agrees to a meeting time you never offered, hallucination is more dangerous in email than almost anywhere else because the output gets sent. And “ask me instead of guessing” turns the model from an autocomplete into a competent assistant who checks.
For triage, a simpler saved prompt does it: “Classify each of these emails: reply-needed / FYI / delegate / ignore. One line each on why. List anything with an explicit deadline first.”
Where this pays off most
The gains concentrate in high-volume, structured correspondence: sales follow-ups and prospecting sequences, recruiter outreach and scheduling in HR, vendor and invoice chasing in finance. The common thread: the shape of the message repeats, only the specifics change, exactly what a saved prompt plus bullets handles well. One-off, politically delicate messages are the opposite case: draft those yourself and maybe ask AI to critique them.
Pitfalls
- Sending without reading. The one rule. Every horror story in this category, the invented discount, the wrong name, the meeting accepted twice, is a skipped review.
- The AI accent. Default model output is longer, warmer, and more symmetrical than human email. If you don’t give tone rules, you get “I hope this finds you well” energy, and regular correspondents will clock it. Your prompt’s voice rules are the fix.
- Prompting with nothing. “Reply to this email” gives the model nothing but the thread, so it produces generic agreement-shaped filler. The quality of the draft is set by the quality of your bullets. Five rough bullets in, good email out.
- Using drafts to avoid decisions. AI writes the message; it can’t decide whether to say yes. If you’re asking the model what your position should be, the email isn’t the hard part.
- Pasting sensitive threads into a consumer plan. Triage and drafting both involve real business content. Sort out which tool, which plan, and which data categories before the habit forms, not after.
Checklist: before you hit send on an AI draft
- Every fact, number, date, and name came from you or the thread, not the model
- No commitments you didn’t intend to make
- Right recipient(s); reply vs. reply-all checked
- Reads like you, shorter and plainer than the model’s first attempt
- Nothing in it you’d mind being forwarded
FAQ
Is it safe to paste work emails into an AI assistant? Check two things: whether your plan excludes inputs from model training (business/enterprise tiers usually do), and what your company’s AI policy allows. Customer personal data, credentials, and legal/HR content stay out regardless.
Will people notice my emails are AI-drafted? Only if you send defaults. Feed the model your actual points and tone rules, then edit, the result is your email, faster. Raw output from a one-line prompt is recognizable and reads as low effort.
Can AI reply to emails automatically? It can; don’t let it for anything that matters. Auto-draft, human-send preserves the review step that catches invented commitments. Full auto-send is only defensible for genuinely mechanical messages.
Which AI tool is best for email? Integrated assistants (Copilot, Gemini) win on triage because they read the thread in place. A general assistant with a saved prompt wins on drafting control. Using both is normal.
Get one practical AI implementation brief per week, join the free newsletter.
Frequently asked questions
Is it safe to paste work emails into an AI assistant?
Depends on your plan and your data. Business and enterprise plans of the major assistants typically exclude your inputs from model training; consumer plans may not. Never paste customer personal data, credentials, or legal/HR matters without checking your company's AI policy first.
Will people notice my emails are AI-drafted?
They notice defaults: over-long, over-formal, oddly enthusiastic messages with bullet-point symmetry. If you feed the model your intent in your own words and edit the output, the result reads like you on a good day. If you send raw output from a one-line prompt, yes, they notice.
Can AI reply to emails automatically?
Technically yes, via agents and inbox rules, practically, don't for anything that matters. Auto-send removes the review step, which is the only thing standing between you and a confidently wrong commitment sent under your name. Auto-draft, human-send is the working pattern.
Which AI tool is best for email?
The one wired into your mail client (Copilot for Outlook, Gemini for Gmail) is fastest for triage and quick replies because it can read the thread. A general assistant (ChatGPT, Claude) with a saved prompt gives better control over tone and structure for messages that matter.