The "where is my shipment?" answer, from inside Outlook.
CargoCube lives in the inbox your team already uses. Hover any HBL, MBL or job number and the live shipment opens beside the email — pulled straight from your CargoWise One. One click drafts the reply, grounded in the real milestones, containers and dates.
Your ops people are stuck in a "where is X?" loop.
Eighty emails before lunch, each asking the same three things — status, ETA, container journey — each costing five minutes of tab-switching.
Today
Read the email. Open CW1 in another tab. Search the HBL. Wait. Read the milestones. Switch back. Paraphrase. Reformat the container dates. Send. Five minutes, every email.
With CargoCube
Hover the HBL. The shipment opens beside the email — status, milestones, six dates per container. Click CargoCube Reply, edit a sentence, send. Thirty seconds.
The math
A six-person desk answering 80 emails a day saves roughly 22 hours daily — two-and-a-half full-time coordinators, without hiring one.
The HBL becomes a link.
You don't search or paste. 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. A grounded reply.
The AI reads the email, looks up every shipment number mentioned, and writes a professional reply that cites the actual status, dates and containers from your CW1 data. Mediocre AI with real data beats brilliant AI with none.
It matches the language of the incoming email — English, 中文, 日本語, Español, Deutsch, Français, Português — in 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 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
It flags what's about to cost you money.
Every shipment surfaces its money deadlines — detention, storage, export cut-offs (Docs/SI, CTO, CFS, VGM) — overdue in red, approaching in amber. Your admin adds custom rules with no code, tied to ETD/ETA ± N days. One click marks an alert handled.
And one click summarises the whole inbox — every email gets a one-line gist and a single next action, so the morning queue clears itself.
🔴 VGM cut-off overdue by 2d (due 05-25)
🟡 Empty return due in 3d · OOLU1234567
🔴 HBL document not uploaded — due ETD
Inbox triage
joyce.chen — ATD still red on 3 consols
To do: update ATD & reply to shipper
Why this is different.
"AI for freight" exists. None of it is built where the work actually happens — inside the operations executive's inbox, grounded in CargoWise.
vs. workflow automation (Raft, Expedock)
They automate the back office — extracting data from emails into your TMS. They don't help the person actively typing a reply. CargoCube lives in the reply itself.
vs. Outlook Copilot & generic AI
Copilot writes faster sentences but has no idea what an HBL is and will happily hallucinate an ETA. CargoCube only answers from your eAdaptor feed — it can't invent status because it doesn't try.
vs. replacing Outlook (Sedna et al.)
Some platforms ask your team to abandon Outlook for a new inbox — a six-month rollout and a fight with IT. CargoCube is a 3-minute admin upload. Same Outlook, just smarter.
vs. CargoWise on its own
CargoWise has the data — two tab-switches away from the email asking for it. CargoCube doesn't replace CargoWise; it surfaces it where your team is already typing.
One Cube. Many faces.
One agent per role, each living in the tool that role already uses — and every one of them grounded in the same CargoWise backbone. The order is the launch order.
CargoCube · Ops Agent
Live shipment lookup on hover, AI replies grounded in your CW1 data, six journey dates per container, deadline alerts and inbox triage. Seven languages.
CargoCube · Booking Agent
Reads a booking email, extracts the fields against your CW1 reference data, writes the booking into CargoWise via eAdaptor, and drafts the confirmation reply.
CargoCube · Control Tower Agent
Whole-job, cross-office visibility — Information, Physical, Document and Cash on one screen. Per-office P&L, AR/AP, FX and inter-company, scoped to your role.
CargoCube · Quote Agent
Drafts a quote from live CargoWise rates with a confidence light and margin guardrails. Clean, high-confidence quotes can auto-send within minutes of the enquiry.
CargoCube · Service Agent
Resolve tier-1 customer queries autonomously (BL copy, status, ETA) and triage the rest with a one-paragraph summary attached. RAG over your own SOPs.
We install it with your team.
One API key per CargoWise instance, locked to your email domains. We do the eAdaptor and certificate work. Your admin's only job is a 3-minute upload.
30-minute scoping call
We map your CargoWise instance, branches and email domains. No prep needed.
eAdaptor + certificate
We set up the read-only eAdaptor connection and OAuth certificate. You approve one Azure app.
3-minute M365 install
Your admin uploads one manifest on a screen-share. Same Outlook, no per-seat install.
14-day pilot
Your ops team uses it on real mail with full functionality. We watch usage with you.
Start a 14-day pilot.
One scoping call, one M365 admin install on a screen-share, one tenant key for your ops team. Full functionality, no commitment. We handle the CargoWise side.