Every milestone, every customer, in real time.
The Tracking Agent polls 3,000+ carrier APIs continuously, classifies exceptions properly, sends proactive updates in your customer's language, and confirms delivery with proof. The “where is my shipment?” WhatsApp pings stop arriving.
Six capabilities. All of them concrete.
Real-time visibility isn't a dashboard — it's the absence of “where is my shipment?” messages. Here's how the Tracking Agent makes that happen.
Polls 3,000+ carriers in real time
DHL · FedEx · Aramex · Emirates SkyCargo · MSC · Maersk · CMA-CGM · plus regional and niche carriers. APIs polled continuously, customer-driven onboarding for anything new.
Proactive customer updates at every milestone
Pickup confirmed. In transit. Arrived at hub. Customs cleared. Out for delivery. Delivered. The customer hears from you before they ask — on the channel they started on.
Classifies exceptions — never a generic 'errors' pile
Customs Hold · On Hold · Delivery Attempted · Address Issue · Weather Hold · Damage. Categorised, prioritised, routed to the right human — not dumped into one inbox.
Multi-language status updates
Arabic for GCC customers. Hindi for Indian SMEs. English for everyone else. The agent picks the customer's preferred language from the original RFQ thread.
Predicts ETA changes before the customer asks
Carrier API says “delay 6h at Dubai hub” → the agent drafts the proactive update with new ETA before the customer has even noticed.
Confirms delivery with proof — auto-generates POD
Delivery photo, signature, timestamp. POD generated and archived on the JO. Customer notified. Loop closed.
Four steps. Continuous loop.
Booking hands off; the agent runs the relationship until delivery. Routine milestones can auto-send. Exceptions always come to a human.
JO goes live
Booking Agent hands off. The Tracking Agent picks up the shipment relationship.
Continuous carrier polling
API checks against the carrier — every status change captured and timestamped on the JO activity log.
Routine update or exception?
Routine milestones can auto-send (per your Autonomy setting). Exceptions always come to a human gate.
Customer informed proactively
Status update on the customer's existing thread. No portal. No login. They never had to ask.
Routine milestone updates can run Auto. Exceptions (Customs Hold, On Hold, Delivery Attempted) are locked to Supervised — a human always sees the bad-news messages before they go out.
Every status change, timestamped on the JO.
Pickup → in transit → arrived at hub → customs cleared → out for delivery → delivered. Each event auto-stamped with the carrier API source. Full audit trail.
- →Every milestone, timestamped
- →Carrier API source on each event
- →Customer notification status per milestone
- →ETA prediction with delta from original
Every event labelled “tracked via carrier API at HH:MM” — never “system says.” Clean audit trail for compliance, disputes, customer asks.
Three states. Always drillable.
Whatever the JO's stage, the customer-facing view is the same — context, status, next action. No vendor portal logins required.
Live carrier status with ETA, milestone timeline, and notification log.
POD attached, delivery timestamp, signature/photo, loop closed.
Classified by type — Customs Hold · On Hold · Delivery Attempted — prioritised by SLA.
Bad news, surfaced fast and clean.
When something goes wrong — and it will — the customer should hear it from you first, with the next-step plan attached. Not after they've already noticed.
Each exception tagged by type — so the right human handles it, not the first one available.
- Exception type — customs · delivery · address · damage
- Severity — based on lane, customer tier, deadline
- Suggested next step — escalate · wait · contact broker
- Customer comms draft — explanation + ETA + action
The Tracking Agent listens, across every system.
Carrier APIs in. Customer channels out. TMS sync sideways. Customs broker escalations downstream.
3,000+ carriers globally — air, sea, road, express. Customer-driven onboarding for any carrier not already wired.
Email · WhatsApp · the customer's existing thread. No vendor portal. No new login.
Hold escalations routed to your customs broker contact, with the exception classification attached.
Status updates flow back to Logi-Sys · Kale · Shipsy · Magaya — your TMS stays the system of record.
The boring magic: customers stopped asking.
Infinity Logistics · 12 months in production · 100+ active B2B accounts. The 'where is my shipment?' WhatsApp queue dried up.
“Used to spend an hour every morning answering ‘where is my shipment?’ messages. Now the customers know before I do.”
— Megha · Operations Manager · Infinity Logistics, Ajman
After delivery, the carrier invoices arrive — and the Invoice Reconciliation Agent catches the variance.
Planned cost vs actual cost — flagged green or red, per shipment, customer, lane, carrier. In real time, not three months later.
Stop being the "where is my shipment?" service.
The Tracking Agent makes you the source of truth — proactively, in the customer's language, before they ask. Pilot scope: tracking + one other process.