Driver–Dispatcher Chat

Problem Statement

Dispatchers and drivers currently use fragmented tools like phone calls, SMS, or third-party apps to coordinate delivery tasks. These tools are not integrated with shipment or route data, leading to miscommunication, slower resolution of delivery issues, and a lack of traceable conversation history.

Current Pains & Impact

• Scattered Communication: No centralized, integrated space for driver-dispatcher interactions.

• No Context: Shipment-specific info is not attached to messages, making troubleshooting harder.

• Driver Safety Risks: Drivers receive phone calls or unclear texts while on the road.

• Operational Inefficiency: Dispatchers waste time managing multiple tools and channels.

• Lack of Traceability: No records for what was said and when, limiting accountability.

“I have to constantly call drivers just to clarify small things. It’s chaotic and slow.” — Dispatcher, Capstone Logistics

Current Workarounds

• Dispatchers rely on:

  • Direct calls or SMS

  • WhatsApp or third-party apps

  • Notes and memory for context

• Drivers responding late or missing key details

Opportunity

A built-in, contextual, permission-based chat system inside the Driver and Dispatcher apps will provide persistent, real-time communication that is tied directly to orders and stops—reducing confusion, speeding up resolution, and eliminating tool fragmentation.

Benefits

• Faster issue resolution with real-time, contextual messages

• Reduced call volume and distraction

• Full message history tied to stops and shipments

• Improved dispatcher productivity

• Safer communication experience for drivers

• Flexible thread management with permissions-based access

Target Users

User’s Core JTBD

“When real-time delivery issues come up, help me connect with drivers quickly and contextually so I can resolve problems without slowing down operations or needing to jump between tools.”

Opportunity Hypothesis & Desired Future State

Opportunity Hypothesis:
By enabling a native, permission-based messaging feature between drivers and dispatchers, we can reduce operational lag, improve support quality, and ensure safer, traceable, and more effective communications.

Desired Outcomes:

• For Dispatchers:

  • Contextual chat tied to stops or orders

  • Manage multiple driver conversations efficiently

  • Reduce time spent on phone calls

  • Flexible thread management with permissions

• For Drivers:

  • Fewer calls from dispatch

  • Clear, contextual instructions via app

  • Quick, easy way to report issues

• For Business:

  • Higher on-time delivery rate

  • Better driver compliance and retention

  • Improved dispatcher-to-driver ratio

Core Functionality

1. Permission-Based Access

   • Drivers:

     • Access to chat is permission-based (set in Mobile Option Set by dispatchers)

     • Two levels:

       • Create: Can initiate new threads with dispatcher(s)

       • Respond Only: Can only reply in existing threads they are part of

   • Dispatchers:

     • Access control set in Users section under Maintenance in Operations app

     • Two levels:

       • Create: Can initiate new threads, add/remove participants, archive threads

       • Respond Only: Can only reply in existing threads they are part of

2. Thread Management

   • Thread Creation:

     • Dispatchers/drivers with create permission can start new threads (at least one dispatcher must be in every thread)

     • No drivers-only threads

   • Participant Management:

     • Dispatchers with create permission can add/remove participants

   • Thread Archiving:

     • Dispatchers with create permission can archive threads (no closing or deleting in MVP)

   • Thread Visibility:

     • All users see threads they are part of

     • Threads accessible from chat tabs, order/route detail pages, and profiles

3. Messaging & Notifications

   • Text, images, PDFs, DOC/DOCX attachments (≤3MB per file, ≤5MB per message)

   • Quick replies (“Running late”, “Need help”, “Location not accurate”)

   • Read receipts & typing indicators

   • Push notifications to drivers for replies

   • Dispatcher sound/visual alerts for new messages

   • Quiet mode for drivers

   • Unread indicators for new threads and messages

   • Special notification when a driver is added to a new thread

4. Offline Support

   • All users can send messages offline in existing threads

   • Messages are delivered when connectivity is restored

5. Security & Compliance

   • End-to-end encryption

   • HIPAA compliance?

   • 30-day message retention

User Flows

• Driver Flow:

  • Access chat from any screen via floating icon or chat tab

  • Start new thread (if permitted) or reply in existing thread

  • Attach stop/order context when available

  • Receive notifications and unread indicators

• Dispatcher Flow:

  • View and manage threads from chat tab, order/route detail pages, or the Drivers grid in VDB

  • Start new threads, add/remove participants, archive threads (if permitted)

  • Reply in existing threads

  • Receive notifications and unread indicators

Rollout Plan

Outcomes & Success Metrics

• Objective 1: Improve Communication Efficiency

  • Key Results:

    • CSAT score from dispatchers and drivers: >70%

    • Reduction in phone calls per driver: 30%+

    • Faster average issue resolution: -40%

• Objective 2: Improve Operational KPIs

  • Key Results:

    • Daily chat usage adoption rate: 80% in beta

    • Dispatcher workload per issue: -25%

Dependencies

• Messaging backend (Firebase, Twilio, or equivalent)

• Push notification service

Initial Limitations

• No broadcast (except as defined by thread creation)

• No live translations

• Attachment limit: 5MB

• No deletion/editing of messages