[NTTP]

Thread Summariser

Paste a long email or chat thread. Get the gist, the key points, and what you need to do.

Paste the full email or chat thread.

Free to try, no sign-up needed

Your text isn't stored. It's sent to Anthropic to generate your result, then discarded. Privacy

Prefer to write it yourself? Use the free prompt.

What it produces

Real output from this tool, not a mock-up.

What went in

The thread
A seven-message thread between Marcus (client), Nadia and Tom about whether a stock sync integration can go live on the 15th, covering a dry run against the full 11,000 SKU catalogue, who is producing the export and when, and an unanswered question about on-call cover.

The gist

Harrow Retail's stock sync integration is planned to go live on the 15th, but Nadia flagged that it's only been tested against a 400 SKU test catalogue versus the real 11,000 SKU live catalogue, so a full dry run is needed first. Marcus is chasing a faster export of the live catalogue (via Sam directly) so the dry run can happen Thursday/Friday with results reviewed Monday, leaving a week's buffer before the 15th. Nadia has been clear that a bad result on Monday means the 15th date is at risk.

Key points

  • Go-live for the stock sync is targeted for the 15th; Marcus says this date can't move because of incoming seasonal stock.
  • Nadia wants a dry run against the full 11,000 SKU live catalogue before committing, since testing so far only covered a 400 SKU test set.
  • Tom says the dry run needs about half a day of setup plus an overnight run, but requires a usable export of the live catalogue, which took about a week last time.
  • Marcus is going directly to Sam (bypassing the portal) to get the live catalogue export faster, targeting Thursday delivery.
  • Agreed plan: catalogue delivered Thursday, dry run Friday night, results reviewed Monday, leaving a week before the 15th.
  • Nadia explicitly warned that a bad result on Monday will trigger a serious conversation about pushing the date.
  • Marcus asked who will be on call on the 15th, since his ops team wants a named contact. This is still unanswered.

What you need to do

  • Confirm with Marcus/team who will be on call on the 15th and provide that name to Harrow's ops team.
  • Be ready to review dry run results on Monday and flag any issues that could affect the go-live date.

When to use it

Use this on the forty-message thread you were added to on message thirty-eight. It gives you the state of play, the points that matter, and specifically what you are on the hook for, which is the part people miss when they skim a thread backwards.

Common questions

What counts as a thread?
Anything with back and forth: a forwarded email chain, a Slack channel you have copied out, a comment thread on a document. Paste it in whatever order it came out, including the quoted text underneath each reply, since that is usually where the earlier context lives.
How does it know what I need to do?
From what is directed at you or left open in the thread. It also flags questions nobody answered, which is the most common thing to fall through: in the example above it catches that the on-call question was asked and never picked up.
Will it tell me who said what?
Where the thread makes it clear, yes, and positions are attributed rather than blended into a consensus that never existed. A summary that flattens a disagreement into one view is worse than no summary.
Is it free?
You can run it three times a day with no account. Signing in gives you renewing monthly credits, and this tool costs one credit per run with the one-click refinements included.

Similar tools

All Work & Meetings