Track vessels and tell shippers about ETA changes

Poll carriers' tracking APIs for your B/Ls and containers and detect ETA changes. AI drafts what the change affects and the shipper notice; staff check it.

  • Freight forwarding & customs
  • Operations & orders
  • Customer support

The problem today

Every day, staff check vessel schedules and container status on dozens of carriers' websites and tell shippers, customs brokers, and truckers when an ETA changes. Carrier sites often restrict automated retrieval through bot protection or terms of use, so RPA lookups keep stopping. When notice comes late, delivery orders, customs clearance, pickup, and delivery bookings all slip.

The workflow in Kitewell

  1. Poll carriers' tracking APIs for events on the B/Ls and containers you handleAutomatic
  2. Extract shipments whose ETA changed since the last checkAutomatic
  3. AI works out what the change affects and drafts the notice to the shipperAI judgment
  4. Staff check the impact and the notice, and approve sendingApproval
  5. Notify the shipper and update the shipment recordAutomatic

What AI does

Works out what an ETA change affects, such as delivery orders, customs clearance, pickup, and delivery bookings, from its size and the shipment's status, and drafts a notice for the shipper.

Where people decide

Staff check the impact and the notice before anything is sent.

Features used

What a PoC checks

  • Access to your main carriers' tracking APIs (such as DCSA Track & Trace) and the fields they provide
  • For carriers without an API, what their terms allow and what stays manual
  • What the shipper notice says and how it is sent

Discuss a PoC for this work

We check whether this workflow runs on your own work and screens.