Blog

83 / 88

Article·Cross-vertical···2 min

EverydayA story, same factsTechnicalThe deeper cut

Catch up fast

Catch up on a long email thread with AI before you reply

Paste the thread with private details taken out, ask who wants what by when and what's still open, then have it draft a reply you check against the thread.

The short answer

Copy the whole email thread, take out anything private, and paste it into a chat tool like ChatGPT, Claude, or Grok. Then ask: "Who wants what from me, by when? What's already decided? What's still open?" Ask it to quote the line each answer comes from. Then ask it to draft your reply, and check that draft against the thread before you send anything. You make the call. The AI just does the reading.

Why "summarize this" isn't enough

A plain summary tells you what the thread is about. You probably know that already. What you need is the part addressed to you: the question someone asked three emails ago, the date that changed, the decision everyone assumed you agreed to. Asking specific questions gets you those.

Floor vote

When you're cc'd on a long thread, what do you usually do?

One vote per device. Change it any time.

Loading votes…

Step 1: Copy the thread and take out private details

Open the newest email and copy the whole thing, including the older messages quoted below it. Paste it somewhere plain first, like a notes app. Swap names for roles, and remove phone numbers, addresses, account numbers, and anything about a customer you wouldn't put on a postcard. Here's how to remove private details before you paste into ChatGPT.

If it's a work thread, check your company's rules about AI tools first. Some workplaces allow only certain tools, or none.

Step 2: Ask the questions that matter

Paste the cleaned thread and send:

This is an email thread, newest message at the top. I am
[YOUR ROLE]. Tell me:
1. Who is asking me for something, what, and by when.
2. What has already been decided.
3. What is still open or disputed.
4. Anything that changed during the thread (dates, prices,
   names).
For each point, quote the line it comes from.

Telling it which message is newest matters. Threads read backward, and dates that changed midway trip people up.

Vague ask | Useful ask

Vague ask

Summarize this thread.

Tells you what it's about.

Useful ask

Who wants what from me, by when? What's decided? What's still open? Quote the line for each.

Tells you what to answer.

Same thread, two ways to ask.

Step 3: Check the quotes

Skim the quoted lines. If a quote isn't really in the thread, or says something different, don't trust that point. AI tools sometimes fill gaps with something that sounds right. Here's a five-minute way to fact-check an AI answer.

Step 4: Draft the reply, then make it yours

Now ask:

Draft a short reply that answers only the questions
addressed to me. Use plain language. Don't agree to
anything I haven't confirmed. Mark anything you're unsure
about with [CHECK].

Read it against the thread. Fix every [CHECK]. Change any line that commits you to a date or a price you haven't agreed to. Then send it yourself.

Built-in summary buttons

Some email apps now include their own summarize button, depending on your plan and whether your workplace turns it on. It's fine for a quick sense of a thread. For anything you need to answer, the four questions above still do the real work.

Field check

Field check

Three questions. Honest answers. No score sent anywhere but this page.

01 / 03

Did you take private details out before pasting?

Short close

Copy the thread, take out private details, ask who wants what by when, and make it quote its sources. Then draft the reply, check it, and press send yourself.

Keep these

The working rules

Long threads hide the one thing you need to answer. Then: Take out private details; Ask the four questions; Ask it to quote the lines; Check the draft before you send.

Mark

Saved on this device. No account.

Pass along

Comments

Comments

A short note on the job in this piece. Name optional. Saved on this page, not a profile.

Loading comments…