Driver messaging
Every route or job assignment has its own message thread between the dispatcher and the driver — one place to clarify a delivery, report a delay, or send a photo from the field. A message can go either way and carry attachments; both sides can see whether the other has read it yet.
Who uses it
The dispatcher and fleet manager write to drivers and see every assignment's thread across the organization. The driver replies only on their own active assignment's thread — they have no visibility into other drivers' threads. The mobile inbox is covered in Driver workflows.
The message thread
Messages in a thread are ordered chronologically and visible to both sides of the assignment. The dispatcher writes first — the message lands in the driver's app immediately, with a push notification. The driver replies on the same thread; the reply lands back in the dispatch console as an in-app notification, never back to the driver who sent it. Every message carries a read marker from the other side — the dispatcher sees how many driver replies are still waiting for acknowledgement and can mark them read in bulk.
Attachments
A message can carry up to five files — photos (JPEG, PNG, WebP, HEIC/HEIF) or PDFs, each up to 10 MB. A file is uploaded to the document store through a signed upload link first, and only a confirmed upload can be attached to a message — the raw bytes never pass through the messaging API itself. The recipient downloads an attachment through a separate, short-lived signed download link minted on demand for that specific document.
In the background
A new dispatcher message immediately fires an in-app and push notification to the assigned driver; a driver's reply immediately fires an in-app notification to the dispatcher, fleet manager and organization administrator — neither notification is throttled or batched, every message lands on its own.