Territory · Substrate signal

02SmartHub modernization.

SmartHub exists; no public AI / agent layer named in the public roadmap. Enmovil's customer-facing chat surface + proactive narrative + document Q&A maps directly to the modernization mandate the Chief Information Officer was hired for.

The portal evolution

From track + book → conversational + proactive.

Today

SmartHub track / quote / book (passive)

Conversational

chat across the shipment graph in plain English

Document Q&A

ask any question across BoL / invoice / customs docs

Proactive

narrative-style exception alerts before customers ask

What we read

Today's portal · tomorrow's mandate.

SmartHub today

JAS's customer portal at smarthub.jas.com. Track + quote + book + document access. No public mention of conversational, document Q&A, or proactive narrative.

JAS company profile

Vishal Bedi · Chief Information Officer

Hired March 2023 from DHL Global Forwarding Americas (where he was CIO + Head of BPO). Brought in to drive digital transformation. Customer portal is in scope.

Intelligent CIO

Customer-centric mandate

Loadstar reported the leadership reshuffle as a move toward a "customer-centric future." Executive air-cover for visibility-portal investment.

The Loadstar

What Enmovil delivers here

Three moves · one SmartHub evolution.

Conversational shipment graph

Customer types in plain English; Caddie reads across CargoWise + customs + carrier data, returns the answer.

Document Q&A

Ask any question across the BoL / invoice / customs documents — Caddie surfaces the line, the page, the answer.

Proactive narrative alerts

When an exception is detected, Caddie generates the customer-facing narrative (what happened, what we are doing, when it resolves).

Proof anchor

Where we have shipped this shape.

40%

Fewer client inquiries on disruptions · global lead-logistics provider, 50+ countries

24/7

Visibility across the carrier mix vs business hours · same deployment

30%

Faster exception resolution · same deployment

For the conversation

Questions, fence, timeline.

What's the gap between what enterprise customers ask for in SmartHub and what it ships today?
What's on Vishal Bedi's 12-month digital agenda — and where does customer-portal modernization sit on it?
Where would a 90-day SmartHub-overlay pilot land first — one customer cohort, one industry vertical, or one route corridor?

We would touch

Conversational shipment graph layered on SmartHub.
Document Q&A across BoL / invoice / customs.
Proactive narrative alerts before customer asks.
Audit trail per generated answer.

We would not

SmartHub replacement (extension only).
CargoWise back-office workflows.
Customs broker workflow.
Carrier-side portals.

8-10 weeks · one customer cohort

First lane: one named customer cohort gets the conversational + document-Q&A layer overlaid on SmartHub, with WISMO call-volume + portal-engagement metrics measured at week 8.