Stop answering
"where is my shipment?"
from scratch.
CargoCube lives inside Outlook. Hover any HBL, MBL, MAWB or job number and the shipment opens beside the email — pulled live from your CargoWise One via eAdaptor Next. One click drafts the reply, grounded in the actual milestones, containers and dates.
Your ops people are stuck
in a "where is X?" loop.
80 emails before lunch. Each one wants the same three things: status, ETA, container journey. Each one takes five minutes of tab-switching.
Today
Read the email. Open CW1 in another tab. Search the HBL. Wait. Read milestones. Switch back. Paraphrase into the reply. Reformat the container dates. Hit send. 5 minutes per email.
With CargoCube
Hover the HBL. The shipment opens beside the email — status, milestones, six dates per container. Click CargoCube Reply. Edit one sentence. Hit send. 30 seconds per email.
The math
A 6-person ops team answering 80 emails a day each saves about 22 hours per day. That's two-and-a-half full-time-equivalent shipment coordinators — without hiring a single one.
Why this is different
from the rest of the market.
"AI for freight" already exists. None of it is built where the work actually happens — inside the operations executive's inbox.
vs. workflow automation platforms
Tools like Raft, Reform and Expedock automate the back office — they extract data from emails and feed it to your TMS. They don't help the ops executive who's actively typing a reply. CargoCube does the opposite: it lives in the reply itself.
vs. Outlook Copilot & generic AI
Copilot writes faster sentences. It has no idea what an HBL is, no connection to your CargoWise data, and will happily hallucinate an ETA. CargoCube only answers from your eAdaptor feed — it cannot invent shipment status because it doesn't try.
vs. replacing Outlook (Sedna et al.)
Some platforms ask your team to abandon Outlook for a new shipping inbox. That's a six-month rollout and a fight with IT. CargoCube is a 3-minute M365 admin upload. Same Outlook, just smarter.
vs. CargoWise on its own
CargoWise has the data. The problem is the data is two tab-switches away from the email asking for it. CargoCube doesn't replace CargoWise — it surfaces it where your team is already typing.
The HBL becomes a link.
You don't search. You don't paste. You hover any shipment reference in any email and the full shipment — status, milestones, containers, vessel, ETA — opens beside the message in under a second.
Six dates per container (empty pickup, gate-in, loaded, discharged, gate-out, empty return) — the journey your customer is actually asking about, in one row.
Shanghai → Sydney · ETA 2026-06-04
Containers (2)
OOLU1234567 · 40HC · loaded 05-19 · discharged —
OOLU1234890 · 40HC · loaded 05-19 · discharged —
Milestones
✓ Cargo received 05-15 · ✓ Loaded 05-19
◯ Arrived 06-04 · ◯ Delivered —
One click. Grounded reply.
The AI reads the email, looks up every shipment number mentioned, and writes a professional reply that references the actual status, dates and containers from your CW1 data. Mediocre AI with real data beats brilliant AI with no data.
The reply matches the language of the incoming email — English, 中文, 日本語, Español, Deutsch, Français, Português — and the tone of a working forwarder, not a press release.
Thanks for the note on 731-98957574.
The shipment loaded onto OOCL Hong Kong v.024W on 19 May and is currently in transit. ETA Sydney is 4 June 2026. Both containers (OOLU1234567 and OOLU1234890, 40HC) are on board.
I'll send the discharge confirmation as soon as the vessel berths.
Best,
Michael
Start a 14-day pilot with your team.
One conversation, one M365 admin install on a screen-share call, one tenant key for your ops team. We do the eAdaptor and CargoWise work. Full functionality during the pilot, no commitment.
Talk to us →