Carrier email → shipment exception

Context

A messy 'where's my truck' email from dispatch is parsed into a structured shipment-exception event that a TMS can act on — delay type, new ETA, reefer temp, and whether the dock appointment needs rescheduling.

The decision

Reliability lives at the systems-of-record boundary: the value is a clean, typed event the TMS can consume, not a paraphrase a human still has to re-key.

What most miss

The hard part isn't understanding the email — it's producing the exact typed event the downstream system expects, every time, so no human re-keys it.

Stakes

A mis-parsed exception that doesn't reach the TMS is a missed dock slot and a detention charge.