Skip to main content
Logistics

Regional logistics operator · GCC

Fleet and dispatch operations platform

Representative product engineering programs delivered by Zestlan. Client names withheld where confidentiality agreements require. Metrics reflect documented outcomes from production deployments.

Context

Dispatchers coordinated drivers via phone and messaging apps. Customer ETA updates were manual; exception handling was reactive.

Fleet telematics existed but was not connected to dispatch decisions or customer communication.

Challenge

Dispatchers lacked real-time visibility into fleet status, route exceptions, and customer delivery commitments.

Solution

A logistics operations platform integrating fleet tracking, dispatch workflows, customer notifications, and performance dashboards.

Constraints

  • Real-time location ingestion from heterogeneous telematics devices
  • Dispatcher UX optimized for high-throughput shift operations
  • Customer notifications without exposing driver personal contact details

Architecture

Operations control plane — telematics ingestion, dispatch board, exception workflows, and customer notification API.

Telematics ingestion

Normalized GPS events from multiple device vendors into a unified fleet state model.

Dispatch board

Real-time assignment, route exception flags, and shift-level workload view.

Customer notification API

Automated ETA and delivery status messages triggered by fleet events.

Performance analytics

On-time delivery, exception rates, and dispatcher efficiency by route and shift.

Technology stack

Go ingestion servicesPostgreSQL + TimescaleDBReact dispatch UIWebSocketsAWS ECS + SNS

Delivery approach

Telematics integration

Connected phase-one fleet; validated event accuracy and latency.

Dispatch MVP

Live board replacing phone-based coordination for pilot routes.

Customer comms

Automated notifications tied to delivery milestones.

Full fleet rollout

Expanded device coverage and analytics for operations leadership.

Measured outcomes

  • 28% improvement in on-time delivery across monitored routes
  • Dispatcher coordination time reduced by 4 hours per shift on average
  • Real-time status available for 100% of active fleet assets in phase one

Engineering lessons

  • Dispatcher UX density mattered — keyboard shortcuts outperformed feature-rich but slow interfaces.
  • Normalizing telematics vendors early prevented duplicate integrations later.
  • Customer notifications had to be event-driven from fleet state — manual ETA updates did not scale.

Discuss your product program

Every engagement is scoped to your business model, users, and constraints — detailed reference material available under NDA for qualified evaluations.