SQRlane’s agents work on the bookings in your TMS, not beside them. Follow one booking through a port strike: every agent’s work lands as a change on that record, the everyday desk picks up what the change implies, and all of it waits for your approval.
This page where the agents’ work lands — one booking, field by field
A strike is called at the Port of Hamburg. Three agents take their turn on a booking bound for it, and each one’s work is a change on the record — not a message beside it. The fourth turn is yours.
HoverTap any agent’s line to see why.
From one recorded run of the demo’s Hamburg scenario, with the model switched off so the page stays the same run to run — the lines above are the rules engine’s own. On the live demo the Routing and Comms Workers write the same fields in the model’s words. The booking is synthetic; the TMS behind it is a demo connector, and nothing is ever written.
A reroute is not finished when it is decided. The booking has to be amended, a new port can move the customs entry, and whatever the customer is told has to meet their standing instructions. The Routing Worker hands each of those to the everyday desk — as messages, on the same booking.
Live reasons on every run. Scripted replays authored data, and says so. Demo is the connector: real on this side, no TMS on the far end. What each one does on an ordinary day is on Use cases.
Built to run on the systems the desk already has
It is a demo connector today.
The far end is the work; the near end is already built.