navlun.ai reads a forwarder's mailbox, groups it by shipment, and turns it into a status board. Every claim links back to the exact email it came from. It sits beside CargoWise or whatever you already run. Nothing to migrate.
VGM confirmations, SI cutoffs, released payments: every update arrives as an email and stays there. Nobody writes it down twice.
A missed reply can cost real money. Demurrage builds per container, per day, until someone happens to check that thread.
The fastest answers happen on the phone in five minutes, then vanish the moment you hang up. No trace, no handoff.
The same pipeline every time: connect, group, extract, track. Nothing about it depends on you organizing your inbox first.
IMAP app password or a one-click Microsoft sign-in. Either way, navlun.ai only reads your mailbox. It can't send anything on your behalf.
Emails are grouped by MBL/HBL/booking reference and by thread. Grouping is deterministic, not LLM guesswork.
Status, ETD/ETA, deadlines, and next actions are pulled straight from the thread. Click any of them to jump to the source message.
Each shipment is placed on a standard booking-to-delivery stage tracker, so you see not just what's urgent but how far along it actually is.
The Microsoft connection requests exactly one scope: read-only IMAP access. No send permission exists in the product at all.
Every customer runs in their own isolated instance. Your data is never pooled with another customer's, and never used to train shared models.
We're formalizing our information security management system under ISO 27001. Certification is in progress and not yet issued.
No setup, no sales call required. Connect a mailbox or run the offline demo with sample data.