BVL surveyed over 200 specialists and executives in logistics in February 2026. Two thirds want to introduce or expand AI, and missing expertise tops the list of obstacles. The obvious answer is an AI course for the team. We have seen that at customers, and it changed nothing.
The knowledge a dispatch team needs when an agent joins is not knowledge about AI. It is three skills you learn in the first weeks on the service itself.
The service books what is unambiguous. Everything else it hands to a person: the order with an unknown article number, the portal order with a quantity change above tolerance, the arrival notice without a dock address. Per case the reason, the original and the service's proposal.
What the dispatcher learns: read the reason first, then the original, then decide. Do not take the proposal unchecked, but do not work every case from scratch either. At the wholesaler from the order capture case study, that is about 20 percent of orders after three months, and the clerk needs under an hour a day for them.
Time to learn: one morning next to the service, in the parallel week.
Every run writes an entry: input, result, review cases, errors. The dispatcher does not have to read it every day; the watchdog does that. But he has to be able to read it. What does 300 in and zero booked mean? What does the same error text four times mean?
What the dispatcher learns: "running" is not proof. A service that ends without a result is an outage, even if the icon is green. And: the first look at an outage goes to the error text, not to the phone.
Time: one hour, with a real outage from the parallel run as the example. There almost always is one.
The service does not get better on its own. It gets better when the rules are right and the master is clean. A new customer needs a reading rule. A customer with three spellings in the master produces three review cases a day until someone cleans the master. A price matrix with contradicting rules delivers contradicting invoices.
What the dispatcher learns: a recurring review case is not work, it is a hint. Three times "unknown article number" from the same customer means: fix the master or call the customer, not book by hand three times.
Time: that is not training, it is routine. We plan two hours a week for one person in the first three months.
Prompting. No dispatcher has to learn to talk to the language model. The model sits inside the service, reads mails and messages and proposes. The rules it follows are maintained with the customer, not by the dispatcher in a chat window.
Nor the technology behind it. Which browser automation, which database: that goes into the handover for IT, not into the dispatcher's head.
At the wholesaler, the clerk now does purchasing and complaints, and an hour a day of review cases. At the forwarder with 40 trucks, dispatch puts the 45 minutes a day that used to be phone calls into tour planning. That is the training that counts: not knowledge about the model, but time for the work dispatchers were hired for.
A caveat: this applies to teams that use the service. For the person who operates and changes it, at our place or in the customer's IT, other requirements apply, and those sit in the handover, not in this piece.
Which of the three skills is your team missing after the last project? Tell me the number and the process. I will show you what our review list and protocol look like, with a real outage in them. Ask for a process check: 30 minutes, no sales pitch.
