AI for logistics and freight at Nidrosoft means sitting in dispatch, the exception board, and the dock note a person still signs. We do not move a truck, change a rate, or tell a shipper the load is on the way if the driver has not called. The audit maps hours. The build, if there is one, stays inside the TMS, the WMS, or the inbox you already pay for.
Written by Cyriac Zeh, founder of Nidrosoft. Also on LinkedIn.
Key takeaways
- We start with exceptions, appointment windows, and the note that never made it back to the customer.
- Method: Embed, Diagnose, Scope, Build, Own. Same as how we work.
- A person still accepts anything that becomes a customer update or a detention claim.
- We decline autonomous dispatch and any write that releases a load without a dispatcher.
- Book a free audit if ops can grant TMS or folder read access.
Contents
- Where the hours sit
- What we sit in
- The audit
- What we identify
- What we will not do
- How Nidrosoft handles this
- Frequently asked questions
- The leftover
Where the hours sit
A small carrier or 3PL still runs on a TMS, a warehouse sheet, and a phone that rings when a door is missed. McLeod, Turvo, MercuryGate, or a cousin. Someone rekeys an appointment. Someone writes “waiting on POD” in Slack. Someone promises a customer update and then takes another load.
Those loops are the week. Dispatch already knows which one. Billing knows a different one. The audit is how those two lists become one ranked page.
What we sit in
We ask for the TMS, the shared customer inbox, and one week of exception codes. Embed means we watch a real dock day. Diagnose means we cost the repeats.
Public work on this site that sits next to acquisition loops includes Nexuvo for dealer inventory outreach. That is automotive, not freight. We will not describe it as a TMS.
The audit
Two weeks. We sit with the dispatcher and the person who files PODs. We write the system of record, the operator, the inheritor, and the human gates. If nobody can approve a detention invoice, the map says so.
The packet ranks hours. Missed appointments. Customer “where is my load” mail. POD chase. The first line might be “draft the delay note from the last ping, send stays on dispatch.” The first line might be “fix the appointment calendar before you buy an agent.”
What we identify
We look for codes you already use: late, OS&D, waiting on POD, appointment moved. Those are forms. Open-ended recovery with a national account is not a form. It is the account manager’s job.
A useful first system drafts the customer update from the exception code. A person still sends it. A useful second system lists PODs that are older than the SLA you already wrote down.
See AI consulting alternatives and AI implementation for San Diego small businesses.
What we will not do
We will not dispatch a driver. We will not change a rate. We will not tell a shipper the trailer is rolling if the driver has not confirmed. We will not connect an ELD to auto-send. If a broker contract blocks vendors, say that to cyriac@nidrosoft.com first.
A lights-out yard with no TMS access gets a no. Seats-only work is training.
How Nidrosoft handles this
Embed on the board. Diagnose the hours. Scope one exception type. Build only if send stays under dispatch. Own means the desk can run the draft after we leave.
Nidrosoft has shipped 125 products and keeps 16 public. None of those 16 is a freight OS. The number that matters is whether this morning’s exceptions have a note before the first appointment.
Frequently asked questions
Do you replace a dispatcher? No. We cut the retyping of a delay. The dispatcher still assigns the truck.
Warehouses or only trucks? If there is a repeating exception queue and a person who can approve a customer note, we can sit there. If the leftover is a new WMS, that is not us.
What do we send to start? A redacted week of exception codes and the name of the person who can send a customer update. Book a free audit.
The leftover
Freight work is a queue with a dock clock. We map the queue. We leave the clock in a human’s hands. Write cyriac@nidrosoft.com or use contact.