Skip to content

Proof of concept

Shipment exception triage from supplier email

A freight desk receives hundreds of carrier updates, customs queries and delay notices a day, all as free text email. Most need no action. The few that do are buried among the ones that do not, and they are usually found once the delay has already cost something.

An AI agent node reading a task, choosing a tool and writing a result back

What we built

  • Classification of incoming carrier and supplier mail by shipment, event type and urgency
  • Extraction of the reference numbers, dates and locations from the message body and its attachments
  • Automatic matching back to the shipment record, with the update written against it
  • An exception queue holding only what needs a decision, ordered by how much time is left to act
  • A daily digest of what moved, what slipped and what is still unanswered

What it showed

In the proof of concept routine status mail was filed against the right shipment without anyone reading it, and delay and customs exceptions appeared in the queue within minutes of arriving.

What a live engagement needs

A live setup needs mailbox access, the shipment reference formats actually in use, and the desk's own definition of what counts as urgent.

Services behind it

Related proof of concept work

See the whole library