Driver messaging and carriage status updates, on the record they belong to.

The Inbox is a single feed of every conversation in your company. Cargo, Orders, Carriages, Fleet, Companies, Contacts, Locations, Drivers and Network are the same feed filtered by what a thread is anchored to — so a dispatcher reads the trips, an accountant reads the partner companies, and nobody searches a group chat for a photo.

Start a thread from any record’s Messages tab and it is already in the Inbox. A card that still needs an answer is framed until somebody gives it one.

• Nine filtered views over one feed, plus the network feed for partner threads.
• A Statuses reading shows the status changes alone, and a People tab holds chats between colleagues.
• Unread is a state you control: mark a thread read or unread, or the whole feed at once.

Arrived, loaded, unloaded, late, a problem at the dock: each is a tap on the stop sheet in the driver app and a card in the carriage’s thread. The colour says what kind of moment it is before you read a word. Amber is a natural stage. Orange is an escalation. Red is a problem. Green is done. Grey is the system recording what happened. Blue is information. Purple is the network — and nothing else.

Every status card is explained on the status changes reference page, with what it means and what it asks of the office.

A card opens into its facts — planned quantities against loaded, delivery window against ETA, who reported what with which photos — and closes with the action. Acting turns the button into a receipt with a time on it and writes a line for everyone else on the thread, and the driver reads the outcome. What the driver reported stays exactly as reported.

• Accept a quantity discrepancy, or ask the driver, without leaving the thread.
• Notify the consignee by email or straight into the thread — one confirm, one receipt.
• Resolve a delivery problem from a fixed set of outcomes, or record your own.
• Reassign a trip after a declined dispatch; ring the driver from the card.

Outcomes suggested by Logis AISoon

Everyone on a trip reads the same thread. A note marked Internal stays in the same chronology but never reaches a driver’s phone — the database refuses it, not just the screen. Say what a message is about — a stop, a cargo line, an order — and read the thread by subject.

• Two audiences on one thread: To the trip, or Internal with the lock.
• Every message can name the stop, cargo or order it is about.
• The driver writes and reads in the app’s eight languages.

The photos and the CMR a driver attaches to a report arrive in the thread and on the carriage’s Documents tab at once, each with a chip for where it lives. A proof of delivery shared with a network partner says so in purple. Everything opens in a new tab; nothing has to be forwarded by email.

Nobody types a status. The driver app writes it, the thread shows it, the office decides on it, and the record keeps it.

Most carriers run dispatch on a messaging app and a mailbox. The table shows what changes when the messages live on the carriage instead.

One thread, four readers, each seeing what their job needs.