Leo tracks the containers and raises the alert

“Where is my cargo?” burns more time than any other question at a forwarder: open each carrier's site, find the container, copy the date, write to the customer. Leo does that round and speaks up when something actually changes.

Book a demo The whole team

What it does

Tracks by container, booking or BL and alerts whoever set the tracking up when something changes.

01
Checks with the carriers
Tracks by container, booking or BL on the main carriers' sites and keeps what they publish.
02
Spots the change
Compares against what he last saw: a date moved, a new transhipment, an arrival confirmed.
03
Alerts whoever set the tracking up
Writes to whoever asked to follow that shipment: when something changes, the summary, and the end of the voyage. Not every time the carrier refreshes its page.
04
Keeps the history
Every event keeps its date and its source, so the discussion is about what the carrier published, not about what someone remembers.

Tracking and alerts

What its work looks like

Tracking · timeline

Event	Place	Status
Loaded on board	Shanghai · CNSHA	Actual
Vessel departure	Shanghai · CNSHA	Actual
Arrival	Manzanillo · MXZLO	Estimated

The alert goes to whoever set the tracking up, not to the end customer.

Illustrative screens and data from the Flettia portal.

What it does not do

Does not guess dates: he shows what the carrier publishes, and estimates look like estimates.
Does not cover every carrier in the world. When one does not publish a field, it is reported as not published.
Does not write to the end customer: the alert goes to whoever set the tracking up, and your team decides what the customer is told.