Zach, the AI agent turning forwarder emails into OneChain data

Your TMS reads your inbox

A shared email address receives your forwarders’ messages. Zach reads attachments, identifies the right shipment, classifies documents, captures useful dates and alerts your teams only when an exception requires action.

Connected inbox

From forwarder email to updated OneChain file

Zach connects where information already arrives: your operational inbox. It reads, matches, classifies and enriches OneChain without forcing partners into a new portal.

A shared address receives emails and attachments from your freight forwarders
Zach identifies the right shipment from file reference, HBL, HAWB, booking or email context
Documents are automatically classified in OneChain
Useful dates, plates, references, amounts and statuses are extracted with no re-entry

Result: less copy-paste, fewer emails to triage, and transport data usable inside OneChain.

What Zach automates

The repetitive tasks that slow down freight operations

Zach does not replace your teams. It absorbs incoming flows and leaves them the decisions that matter.

Documents

Classifies attachments in the right place

POD, CMR, HBL, HAWB, invoices, packing lists: Zach reads attachments and attaches them to the right shipment file.

Exceptions

Only alerts when action is required

Missing document, unidentified shipment, discrepancy above threshold or missing data: Zach surfaces the exception.

Customer proof

8,000 emails avoided per year at Christofle

The Christofle case illustrates Zach’s operational promise: reduce email loops, make transport documents reliable and let teams focus on exceptions.

See customer cases
8,000 emails avoided per year
50 transport users involved
3 years global partnership
Questions & exceptions

Ask Zach about the flows it processes

Every email read becomes usable data. Your teams can ask what was classified, what remains in exception and what requires a decision.

Alert when an email cannot be matched to a shipment
Notification when an expected document is received or remains missing
Escalation for invoice discrepancies, inconsistent dates and critical delays
You

Which forwarder emails are still not matched to a OneChain shipment?

Zach

3 emails need review: 2 missing booking references, 1 unrecognized HAWB. All other attachments were classified.

You

Which PODs updated a delivery date this week?

Zach

18 PODs were read. 15 dates match the ETA, 3 deliveries were flagged as late.

Alerting

Contextual alerts, not another inbox to watch

Zach surfaces exceptions with useful context: source email, document, transport reference, extracted field and expected action.

Email OneChain

Shipment identified

The POD received by email was classified on file BB-HYHN-3 and the delivery date was updated.

Invoice Email + platform

Discrepancy above threshold

Fuel surcharge billed above the rate sheet. The credit note request is ready with justification.

Exception Platform

Reference not found

The email mentions an unrecognized booking. Zach keeps the message as an exception with extracted context.

In short, Zach is:

An agent connected to your emails, without forcing partners into a portal

Documents classified and useful fields captured automatically

Exception alerts to keep teams focused

Evaluate OneChain

Ready to save 50% of your transport management time?

See in 30 minutes how OneChain adapts to your flows, providers and quality standards.

Request a free demo