Fair questions, answered before you ask twice.

Those platforms sell visibility to shippers — dashboards their supply-chain teams watch. Logitrack AI is built for the forwarder's side of the relationship: it doesn't just show you events, it turns them into customer communication — classifying the exception, drafting the update in the customer's language, and sending it on their channel after your approval. Visibility is the input; the conversation is the product.

A tracking API gives your developers standardized container events — someone still has to interpret them, decide who needs to know, and write the message. The desk consumes the events and does the interpreting, deciding and writing. If you have a dev team building your own stack, an API is a fine ingredient; the desk is the finished meal.

Rollover, blank sailing, transshipment delay, customs hold, port congestion, late gate-out, missed empty return — each detected from event patterns and classified with its reason, so the customer note says what actually happened and what happens next, not just “delayed”.

No. Milestones that matter to the customer (departed, arrived, out for delivery, exception, POD) become updates; internal noise doesn't. Cadence and channel are configured per customer — some want every move on WhatsApp; some want a weekly digest by email.

Updates go out in your customers' languages — the desk drafts multi-language natively. Every draft is yours to review until you dial specific update types to auto.

As deliveries complete, the desk collects the proof of delivery and attaches it to the shipment — so the document your customer's accounts team needs (and your invoice may be gated on) exists the day of delivery, not weeks later.

Yes — alongside CargoWise, Logi-Sys, Kale, Shipsy, Magaya, or no TMS at all. Events and documents post into what you already run.

Anything that commits you: delay explanations to angry customers, claims conversations, and any update type you haven't dialled to auto yet. The desk drafts with the full event history attached; your team decides what leaves the building.