Proposed workflowCustomer service · Operations

Summarize a shipment email thread

Turn a messy thread into confirmed facts, conflicting updates, and questions to resolve.

Added 2026-10-14 · Reviewed 2026-10-14

Untested idea · The sample is fictional and does not document an actual deployment or model test.

The task

The latest shipment facts are scattered across an email thread. Older ETAs can survive in a summary unless timestamps and corrections stay visible.

How to get started

Try the fictional thread below first. Keep messages in their original order and number them.
Copy the instructions and paste the thread after them.
Compare every fact to its cited message. Resolve contradictions against the source system.

Expected result

A short brief with confirmed facts, conflicting statements, unresolved questions and suggested follow-ups.

Instructions to copy

Use only the numbered shipment messages below. Produce: (1) confirmed facts with message references, (2) conflicting or superseded statements, (3) unresolved questions, (4) suggested follow-ups. Keep timestamps and timezones exactly as written. Separate a delivery appointment from a driver ETA. Do not invent a location, ETA, shipment status, commitment or completed action. Explicit corrections can supersede an earlier claim; a later timestamp alone does not prove correctness. If a fact is absent or unclear, write Unknown or Needs verification. Draft only; do not contact anyone.

Shipment messages:

Try the fictional sample

Download input ↓

Illustrative input and output. These are not recorded model results.

Sample input

[S1] Oct 14, 2026 09:10 CDT — Dispatch: FF-1042 left Dallas at 08:40 CDT. Delivery appointment: Oct 15 at 10:00 CDT in Chicago.
[S2] Oct 14, 2026 10:00 CDT — Customer: Can you confirm the driver ETA? We still have Oct 15 at 09:00 CDT on our sheet.
[S3] Oct 14, 2026 10:15 CDT — Dispatch: The appointment is Oct 15 at 10:00 CDT, correcting the old 09:00 entry. Driver ETA has not been confirmed.

Illustrative output

Confirmed: FF-1042 departed Dallas at 08:40 CDT [S1]. Delivery appointment: Oct 15 at 10:00 CDT [S1, S3].
Superseded: Customer sheet lists 09:00 CDT; dispatch explicitly corrects it to 10:00 CDT [S2, S3].
Unknown: Driver ETA and current location.
Follow-up: Verify the appointment in the TMS and request a confirmed driver ETA.

Human review required

Confirm the shipment reference and explicit corrections; do not assume the newest message is always correct.
Check every date, timezone, location and appointment against the original message or TMS.
Approve any external communication yourself.

Evidence & limitations

Proposed workflow: the prompt has not been independently evaluated or tested with real shipment data.
The example below is illustrative synthetic content, not a recorded model execution.
The model has no live tracking access and may omit or misread facts. Use only company-approved data and tools.