Skip to main content
IronKernel Platform

Pilot: Driver Messaging

Delivers secure, real-time-oriented in-app communication with unread tracking, grouping, and send restrictions.

Problem

Delivers secure, real-time-oriented in-app communication with unread tracking, grouping, and send restrictions.

Capability

Delivers secure, real-time-oriented in-app communication with unread tracking, grouping, and send restrictions.

How it works

  1. 1 Driver-dispatch chat with inbound/outbound visual differentiation.
  2. 2 Date-grouped message chronology.
  3. 3 Unread indicators and auto-scroll to latest messages.
  4. 4 Continuous refresh behavior for near-real-time messaging.

Operational outcomes

  • Driver-dispatch chat with inbound/outbound visual differentiation.
  • Date-grouped message chronology.
  • Unread indicators and auto-scroll to latest messages.

Integration boundaries

  • TMS
  • CMMS
  • Crew

Proof model

Feature-level proof

  • Driver Messaging scope is defined in product module catalog.

    verified

    docs/products/pilot/product.md · Module Catalog > Driver Messaging

  • Pilot trip workflows and stop progression are implemented in mobile load and stop views.

    verified

    docs/products/pilot/product.md · Module Catalog > Trip and Stop Management

    Code: frontend/apps/mobile/src/pages/Loads.tsx

    Contract: proto/tms/loads/v1

  • Pilot trip and stop workflows are implemented in mobile and load components.

    verified

    docs/products/pilot/product.md · Module Catalog > Trip and Stop Management

    Code: frontend/apps/mobile/src/components/load

    Contract: proto/tms/loads/v1

Continuity routes for this capability

Route-level continuity checks where this feature appears in product-pair workflows.