Procedures and document knowledge
The import procedure for this route, what document fields mean, storage terms and playbooks for holds and missed slots. With source and version.
AI at work/ Interactive workflow example
A phone call starts the work. Agents check each release separately, compare the documents, ask the forwarder for a correction and plan a new truck slot once customs releases. Company Brain supplies procedures and document knowledge; the Laava Platform coordinates the work and the connections.
Fictional terminal, carrier, forwarder, haulier and documents. The call is a written script without audio. Statuses, messages and the slot are simulated.
A driver calls from the gate
Five releases, documents, a correction and a new slot
A handover with timestamps, or a hold with an owner
01 / The example
Play it or choose an exception. Click any item to open its document, including how the driver or the forwarder sees it.
Interactive workflow exampleFictional
CRVU 418207 3Shipment
Case timeThu 15 Oct · 10:12+0 m · Time compressed
01 / 08CallStep 1 of 13
Bram calls from his cab: the container will not come out. This call starts work; it is not a question for an FAQ.
Click any item to open its document.
Document · Step 1
I am at the Brakmond gate. My container is not being released.
Case time is compressed: four hours in about a minute.
02 / Step by step
The standard path, from the phone call to the handover.
01Call
Bram calls from his cab: the container will not come out. This call starts work; it is not a question for an FAQ.
Number, plate and PIN are read back and compared with the haulier's pre-notification. Only then does the agent share shipment details.
02Context
Company Brain supplies the import procedure for this route, what the document fields mean and the customs hold playbook. Those rules decide which checks apply.
03Checks
Terminal, carrier, pickup authority and slot are fine. Customs is holding the container. Each status has its own source and time; one green light does not turn another green.
The B/L says 18,420 kg, the packing list and the declaration 16,240 kg. The difference is shown verbatim, with the source line of each document.
04Act
Rijnpoort gets a correction request quoting the exact lines, Mila at the gate gets an alert, and slot and storage are assessed: the 10:00 slot is at risk, storage is free until Friday.
Bram hears what is going on, who is fixing it and what happens next. The call ends; the case stays open.
05Wait and resume
Rijnpoort sends a new packing list and amends the declaration. The message is matched to the same shipment; only the weight check runs again. Paperwork in order is not a release.
A new status from the customs connection clears the hold. The agent never grants a customs release itself; it reads the status from the source.
06Confirm
The gate operator rechecks terminal, carrier and pickup authority and confirms. Only now can a new slot be booked.
The 10:00 slot has expired. There is room at 14:00; Inge at Kooistra confirms and Bram gets a message.
07Pickup
Customs, carrier, terminal, pickup authority and slot are all right at the same moment. Only then does the terminal record the gate-out.
08Handover
What blocked, who solved it, the new slot and the gate-out are in one handover. Storage stayed within the free period.
03 / Who does what
The import procedure for this route, what document fields mean, storage terms and playbooks for holds and missed slots. With source and version.
The call, statuses from terminal, carrier and customs connections, the correction request, the slot and the handover. Messages land on the right shipment.
Only customs releases, the gate operator confirms the rest and the dispatcher confirms the slot. The agent reads statuses and prepares work, but never grants a release.
The next step
Together we look at one process: where it starts, where it waits and who decides. Then it is clear what a first application can do.
Discuss this workflow for your organisationMore about Company Brain