AI for Logistics · Last mile · Fleet and drivers · Freight and documents
Every exception, called and cleared.
- Saudi Arabic, day and night
- Drivers and consignees, both
- Updated in your TMS
- Cash on delivery, verified
04 · WHERE THE WORK LANDS
Last mile
→ Window agreed
written to the TMS
Failed stops
→ Return cancelled
rescued on the call
Drivers
→ Re-briefed by voice
no typing at a wheel
Customer service
→ Live position given
not yesterday’s status
Freight
→ Document gap found
before demurrage
Claims
→ Pack assembled
POD and photos attached
03 · HARNESS
VOHO LOGISTICS AI HARNESS
WATCH · CALL · RESOLVE · EVIDENCE
VOICE
Listen · speak · barge-in
TOOLS
TMS · telematics · docs
MODELS
Arabic speech · LLM · ETA
AGENTS
One per desk
VERIFICATION
Before an address changes
CASH LIMITS
Amounts come from the order
EVALUATIONS
Scored on real exceptions
MODEL ROUTING · CONTEXT · RAG · GUARDRAILS · PII REDACTION · HUMAN APPROVALS · AUDIT TRAIL
02 · SYSTEMS OF RECORD
01 · WHERE THE SHIPMENTS ARE
Swipe the drawing sideways.
One AI layer. Every shipment, every driver and every system behind them.
The Voho Logistics AI Harness
The shipment that goes right never needed the AI.
Margin is lost on the exception: the second failed attempt, the address nobody can find, the certificate missing while a container accrues demurrage. Each one is solvable by a phone call somebody does not have time to make, and each one has to end inside the TMS to count.
A model on its own
- Reads a status that was true this morning
- Cannot see where the van actually is
- Agrees a window the route cannot keep
- Takes the customer’s word for the cash amount
- Leaves the depot to find out tomorrow
The same model, in the harness
- Reads position, sequence and the promised window together
- Calls before the van reaches a locked door
- Books a window the route plan has accepted
- Reads the cash amount from the order, never the call
- Writes the new window and the recording into the TMS
Logistics systems
What you already run
- TMS
- WMS
- ERP
- Telematics / GPS
- Route optimisation
- Proof of delivery
- Customs platforms
- Carrier APIs
- CRM
- Telephony
- SMS gateway
Voho Logistics AI Harness
The runtime between your systems and the models
- Tool calling
- Model routing
- Logistics connectors
- Consignee verification
- Memory
- Context
- RAG
- Workflow orchestration
- Permissions
- Cash limits
- Human approvals
- Evaluations
- Guardrails
- Audit trails
- Observability
Model layer
Routed per task, never one model for everything
- Saudi Arabic speech
- Speech synthesis
- Foundation models / LLMs
- ETA and delay models
- Document and label models
- Address resolution
Agent layer
Scoped to one desk each
- Delivery Agent
- Driver Agent
- Exception Agent
- Customs Agent
- Customer Service Agent
- Freight Agent
Where the work lands
Finished in the system that owns it
- Windows confirmed
- Deliveries rescheduled
- Drivers briefed
- Delays explained
- Documents cleared
- Claims evidenced
01
Watch.
Every shipment against its promised window, using telematics, the TMS and the carrier feeds you already pay for.
02
Call.
The consignee before the van arrives at a locked door, and the driver when the route no longer matches reality. In Arabic, at the hours deliveries actually happen.
03
Resolve.
A new window agreed, an address corrected, a neighbour authorised, a cash amount confirmed, written straight into the TMS as the trip is running.
04
Evidence.
Proof of delivery, photographs, the recording and the agreement behind every exception, so a claim or a customs query has an answer attached.
01 · Last mile
The second attempt, rescued on the phone.
Nobody was in this morning, the parcel is cash on delivery and it is one failed attempt away from riding back to the depot. Listen to where the address gets fixed the way people here actually give directions.
Transcript
Verification
Shipment details are not discussed until the recipient is confirmed.
Tool calls
waiting…
Policy
- Rescheduling a stop, correcting directions and confirming the order’s own cash amount complete on the call.
- Changing the recipient, the city or the amount is held for a supervisor, because that is how parcels get stolen.
Illustrative call · new window, directions and recording written to the shipment
02 · The exception desk
Find them while they can still be saved.
A board of promises with times attached, scored on position, remaining stops and what usually happens at that address at that hour. The resolutions underneath are the calls a depot never gets round to making.
Riyadh · Al Malqa
Riyadh · Al Olaya
Riyadh · Al Narjis
Van is 40 minutes behind, two stops to go
Riyadh · Qurtubah
Riyadh · Al Yasmin
Nobody home, second attempt, cash on delivery
Jeddah port · import
Certificate of origin missing from the pack
Scored on position, remaining stops, the promised window, the history of that address and whether anyone is usually in at that hour.
Exception Agent
Consignee called about the failed stop
Voice · TMSSH-88255: reached on the second ring, new window agreed for tomorrow 18:00–20:00, cash amount confirmed unchanged at SAR 740.
At-risk window renegotiated before it broke
Voice · route planSH-88230: customer offered 13:00–15:00 and accepted, so the stop moves down the sequence instead of failing.
Driver re-briefed on the new sequence
Voice · telematicsTold by voice on his own phone, with the two changed stops read back to him, no typing at a wheel.
Customs gap chased with the broker
Documents · emailFR-40118: missing certificate of origin identified from the document pack and requested from the shipper, before demurrage starts.
Everything written back
TMSStatuses, new windows, the recordings and the agreements attached to each shipment in the TMS.
03 · The rest of the floor
Not one use case. The work a depot runs on.
Driver calls, delivery windows, shipment status and the paperwork behind them. Same harness, different desk. Play any of them.
1 of 5 · swipe for the rest
Press play to hear how this call goes.
Status
—
Reason
—
Repeat call
—
Want this running in logistics?
We build the first one with you, on your own systems, and it is usually working within a month.
Across the network
One harness. Every depot and every desk.
The telephony, the connectors, the verification rules and the evaluation set are built once. The next depot is configuration.
Last mile and customers
The exceptions that cost the margin
- Delivery windows confirmed the evening before, in the customer’s own language
- Failed deliveries rescheduled on the call rather than returned to the depot
- Addresses clarified against landmarks the way people actually give them here
- Cash on delivery amounts confirmed before the driver arrives
- Where-is-my-order calls answered from the live position, not from yesterday’s status
Fleet and drivers
The people on the road
- Drivers briefed and re-briefed by voice while the route changes
- Delays and breakdowns captured by phone and reflected in the plan
- Proof of delivery chased and checked for the missing photograph or signature
- Safety and compliance checks logged without paperwork at the end of a shift
- Shift handovers and depot notes written from what the driver says
Freight and documents
Where shipments wait
- Bills of lading, invoices and packing lists read and cross-checked
- Customs paperwork gaps found before the shipment sits at the border
- Demurrage and detention exposure surfaced while it can still be avoided
- Rate and tariff questions answered against the actual contract
- Claims packs assembled with the photographs, the POD and the timeline
Connectors
One AI layer. Every system behind the shipment.
Read access first, write access for the statuses and windows you allow, and nothing that lets a promise outrun the plan.
TMS
Trips, stops, statuses, exceptions
WMS
Stock, picks, dispatch readiness
Telematics
Position, speed, arrival prediction
Route planning
Windows, sequences, re-planning
Proof of delivery
Signatures, photographs, exceptions
Customs platforms
Declarations, status, requirements
Carrier APIs
Sub-contracted legs and trackers
Telephony and SMS
Your numbers, drivers and consignees
Built for an operator
What operations and finance ask, answered in the product.
The limits below are the ones that protect the margin: cash amounts, redirects and promises the route cannot keep.
Cash limits that cannot be talked around
Cash on delivery amounts are read from the order, never from the conversation. Changes, discounts and waivers are drafted for a supervisor, and every attempt is logged.
Verification before an address changes
Redirecting a parcel is how fraud happens in this industry, so address and recipient changes take the verification you configure and can be held for a person.
It plans with your planner, not around it
New windows are written back through your TMS and route rules, so the promise the customer hears is one the plan can actually keep.
Inside your own network
On your servers or in a Saudi region. Recordings, transcripts, customer addresses and driver data stay where your policy says.
Drivers are spoken to, not surveilled
Voice is used to brief and to capture what happened, on the phone the driver already carries. What is recorded and how long it is kept is your configuration.
Evaluated on your own exceptions
Scored against last quarter’s failed deliveries and delays before go-live: what it would have called, what it would have rescheduled, and what it should have escalated.
From the library
What this would look like at companies you know.
Demonstrations, not customer work. We built five agents for each of these organisations from public knowledge of how they run; none of them asked, and none of them run this today. Open one to see this page’s argument applied to a operator you recognise.
Bahri (National Shipping Company)
Logistics
One of the world’s largest owners of VLCCs, a business where a day of delay is priced to the hour before the ship sails.
Run the demos →Saudi Post SPL
Logistics
The national postal and logistics operator, where a failed delivery is usually an address that describes a place rather than locating it.
Run the demos →Saudi Arabia Railways
Logistics
Passenger and freight rail across long distances, where a single track section failure holds every train behind it.
Run the demos →SMSA Express
Logistics
Express parcels and e-commerce fulfilment, where a delivery promise made at checkout has to survive a network the merchant cannot see.
Run the demos →How a project runs
Start with one exception type. Keep the harness.
The first project proves itself on numbers you already report: failed attempts, returns to depot, cost per delivery and calls answered.
01
Take one exception type
Failed deliveries, or window confirmations the evening before. The one your depot managers complain about, with a number attached.
02
Connect inside your network
TMS and telematics read access, write access for the statuses you allow, your telephony and SMS, reviewed by your IT and operations teams.
03
Replay last quarter
The agents are scored against real exceptions that already happened: what they would have saved, and where they would have made it worse.
04
Go live on one depot, then widen
One depot, one shift pattern, handover always available. The next depot reuses the same harness.
What operations, finance and depot managers ask first.
If your question is not here, bring it to a technical session with our engineers.
01Does it actually change the plan, or just call people?
It writes the agreed window, the corrected address and the new status into your TMS as the trip is running, within the rules your planner enforces. A promise the plan cannot keep is not made.
02How does it handle Saudi addresses?
The way callers actually give them: landmarks, neighbourhood names, "behind the mosque, second gate". It resolves those against your address data and the national address where you use it, and confirms back what the driver will see.
03What about cash on delivery?
The amount comes from the order, not the conversation. It is confirmed to the customer before arrival, and any change, discount or waiver is drafted for a supervisor rather than agreed on the call.
04Can someone redirect a parcel by calling in?
Only if they pass the verification you configure, and you can require a hold for a person on any redirect. This is the most common fraud in last mile, so the bar is yours to set and every attempt is on the audit trail.
05Do drivers have to install anything?
No. It calls the phone they already carry, in Arabic, Urdu or English as you configure, and what they say becomes status and notes in your systems without them typing at the end of a shift.
06Does it work across sub-contracted carriers?
Yes, through the carrier APIs and trackers you already integrate. Where a leg is opaque, it says so rather than inventing an estimate.
07Can it read the freight documents too?
Bills of lading, invoices, packing lists and customs paperwork are read and cross-checked, so a missing certificate is found before the container is sitting at a border rather than after.