← AI 101

Intermediate training

Claude with Outlook and Teams

Email is where most of GMFS sales work flows — and where bad AI output is most embarrassing. Triage an inbox, draft replies in your voice, and turn long threads into decisions with owners. The module that compounds the value of everything above it.

18 minutes Builds on Module 3.4 Includes thread summarizer

Start here

What you'll be able to do after this lesson

Triage a full inbox in one sitting

Use Claude to sort the unread folder into reply-today, reply-this-week, archive, and delegate — with the actual reasoning, not a confident guess.

Draft replies in your voice

Produce short, specific replies that sound like you wrote them — not like the bot opened the message and produced a polite paragraph.

Threads into decisions

Compress a long back-and-forth into the three things that matter: what was decided, what's still open, what someone has to do next.

Three email moves

Triage, draft, summarize

Triage

What needs a reply today, what can wait, what should be archived or delegated. Inbox sorting is the highest-frequency Claude move for anyone whose work flows through email.

Draft

In your voice, on the right hook, addressing the specific person you're writing to. The brief is the relationship, the outcome, and a sample of how you talk — not just "reply to this."

Summarize

Threads turn into structured decisions: what was decided, what's still open, who owes what. The summary should also flag what the thread didn't answer — gaps are part of a useful summary.

Trainer note: Email is where AI productivity gains are most visible — and where bad AI output is most embarrassing. A wrong name in a forwarded reply travels fast. The patterns in this module exist because the cost of getting them wrong is real.

Where the work happens

Three surfaces, the same moves

Chat for one-off drafts

Paste the thread or a long message, ask for the reply or the summary, ship it. Fast for single-touch requests where you'd rather not open Cowork.

One-touch

Cowork for thread files

When a long thread comes as an attachment, an .eml export, or a connector pull, Cowork is the right surface. Same patterns — different way of getting the source in.

Real files

Teams as a secondary surface

The same patterns work for Teams threads: triage, draft, summarize. Shorter messages, faster cadence — but the same "supply the thread, name the relationship" rule applies.

Same rules

Email work

Five rules for replies that don't embarrass you

Always supply the original thread

The whole thread, not a paraphrase. Replying to "the gist" loses the thing the recipient was actually asking. Pasting takes two seconds; rewriting after a wrong reply takes twenty minutes.

Name the relationship and the outcome you want

"This is my processor Sarah. I want her to extend the lock and prep for the renegotiation conversation." The brief is half relational, half operational — both halves matter.

Draft short by default

The default reply is short — three sentences, one clear ask, one specific date or window. Lengthen only when the situation actually warrants it. Long replies trigger long replies.

Run a tone pass against your own writing

Paste a recent reply you wrote, ask Claude to match it. Without the voice sample, Claude defaults to a faintly-AI-flavored business polish that doesn't match how you actually write.

Never send a sensitive reply without reading it yourself

Borrower-facing, compliance-adjacent, customer-impacting, manager-facing — read every word before you hit send. The cost of catching one wrong specific is much smaller than the cost of sending it.

Prompt upgrade

Weak prompt

Reply to this email.

Email-ready prompt

Work-ready prompt

(In Cowork.) Thread attached — Patel appraisal gap, six messages between me, Sarah (my processor), and the AMC. Relationship: Sarah is my processor and a regular collaborator. Borrowers Anil and Priya Patel are first-time buyers, payment-sensitive. Outcome: I need to give Sarah my final call by EOD Monday — renegotiate, ask for more down, or kill the deal. Match my-voice-sample.docx in this folder. Under 100 words.

Best patterns

Four email workflows that earn the time

Inbox triage

Sort the unread folder into reply-today, reply-this-week, archive, and delegate. Get back time on the front end of the day instead of losing it to inbox-tax.

Single-reply draft in your voice

One thread, one reply, one specific ask. The highest-volume use case for most employees — and where a voice sample makes the biggest difference.

Long-thread summary with action items

Decisions, action items with owners and dates, open questions. The fastest way to catch up on a thread you've been away from for three days.

Pre-meeting prep from email history

"From the last 30 days of email with this account, what's open, what's decided, and what should I bring to today's call?" Five minutes of prep replaces twenty minutes of awkward.

Email checks

Five things to verify before you send

Names and titles correct — every spelling, every honorific, every cc No client-confidential information leaked to the wrong audience — especially in forwards and replies-all Tone matches the relationship — a peer doesn't get a formal close, a partner doesn't get a casual one The ask is unambiguous — one specific next step with a specific date or window The reply doesn't promise something you can't deliver — Claude doesn't know your calendar

Employee rule: Sensitive emails are read by people who know exactly how you write. A wrong cadence, a wrong word, or a wrong name reads as "they didn't write this." Take the extra minute before you hit send — every time.

Tame the inbox

Six exercises to build email fluency

The compounding gains come from saved prompts, voice samples that work, and a triage habit. Run these once and you'll keep running them.

Open the thread summarizer in this lesson. Click each summary item to see which thread messages it came from — and note the one item that has no source (the implicit gap).
Triage your unread folder with Claude. Compare its sort to your own sort the next morning. Note where it called things right and where it didn't.
Draft three replies in your voice using a voice sample. Trade them with a teammate and have them rate which feels most like you.
Summarize a long thread into decisions, action items, and open questions. Forward the summary to a colleague who wasn't on the thread and see if they can catch up from it alone.
Prep for one upcoming meeting using the last 30 days of email history. Note what surfaces that you'd otherwise have missed.
Build a saved prompt for your most common reply type — referral request, follow-up after closing, condition explanation — and save it where you can grab it in three seconds.

Completion standard

You've finished this module when you have a triage habit, a working voice sample, three saved reply prompts, and a summary pass you actually trust enough to forward.