A dispatcher’s daily workflow

Inbox → review/accept AI proposal → order → price → dispatch or subcontract → documents → tracking/ETA → POD → billing

1. Overview: tiles for orders today, in transit, delayed, open AI proposals, revenue and margin for the month; below them the latest orders and open AI proposals. Clicking the delayed tile takes you to the control tower.
2. AI inbox: the mail agent has already classified new emails (e.g. order request, status request, proof of delivery, invoice). Open an order request – on the right you will find the “create order” card with a confidence bar.
3. Review the proposal: read the reasoning and risks, check stops, shipments and price. If everything fits, accept it. If something is missing, use edit & accept. If it is wrong, reject it with a comment. The order is created as a draft; a “review” badge marks AI-extracted orders that should be double-checked.
4. Order: open the order, check the AI extraction notice in the overview tab and move it to confirmed. Confirming automatically starts the dispatch agent.
5. Price: the sales price comes from the customer rate (live price while editing, then apply it). Alternatively run the pricing agent from the AI tab, or click the prices in the order header to edit them. For a quote, ask the Copilot to create one or generate a quote document in the documents tab.

1. Dispatch: the dispatch action opens the dispatch board with the order highlighted – drag it onto a tour – or use the AI proposal button on the order card. Own fleet: set the tour to transmitted so the driver sees it in the app. Subcontractor: subcontract → carrier, purchase price → request; once the carrier agrees, confirm it under assignments.
2. Documents: documents tab → generate: CMR consignment note, transport order, delivery note, pallet note or quote in the language of your choice. Incoming PDFs (CMR, POD, invoice) are classified and attached automatically by the document agent (L3, can be rolled back).
3. Tracking/ETA: once the tour is started, the order is in transit. The ETA agent recalculates the ETA every 15 minutes. If it is more than 30 minutes after the delivery window, a proposal to inform the customer about the delay is created (L2). To set it manually: “…” menu → set ETA.
4. POD: the driver reports arrival, photo/signature and departure in the app; the order becomes delivered and the proof is stored in the documents tab (green = signed). POD by email: in the inbox, the “proof of delivery” topic leads to a proposal to link the document.
5. Billing: when an order is delivered and has a POD, the billing agent proposes creating an invoice (L2). Then: billing → open the invoice → issue → send. Carrier invoices are checked under incoming invoices; at month-end run the accounting export.