Field management and coordination, per vertical.
14 vertical-specific dispatch surfaces, each tuned to how that industry coordinates work. Cross-vertical dispatch board, real-time fleet map, operational status grid, and a 24-carrier shipping layer with multi-leg handoff orchestration.
One dispatch engine. Fourteen operational shapes.
Each vertical gets its own dispatch UI tuned to how that industry actually coordinates field work. Not a generic board with different labels.
Endurance
5 dedicated surfaces
- Aid Stations
- Assignment
- Course Ops
- Medical
- Race Control
Cross-vertical surfaces that span all 14 verticals.
The Dispatch Board, Fleet Map, Status Board, and Metrics dashboard aggregate data from every active vertical into unified operational views. Registry-driven navigation scopes each user to their area and assigned verticals.
,0,
vertical-specific dispatch surfaces
,0,
dedicated sub-pages across verticals
,0,
shipping carrier connectors
,0,
access areas (personal · staff · manager)
The cross-vertical command surface.
DispatchBoardClient renders a unified work-order queue spanning all active verticals. Registry-driven sidebar narrows scope to current area and assigned verticals.
Cross-Vertical Command Surface
A single board that aggregates work orders from all 14 verticals. Filter by vertical, team, area, or status without switching contexts.
Work-Order Assignment
Assign tasks to technicians, drivers, or crew via /api/dispatch/dispatch/assign. Roles resolve through the registry: personal, staff, and manager areas each see their scope.
Team Feed
Real-time team roster pulled from /api/dispatch/dispatch/team. See who is on shift, their current assignment, and availability across verticals.
Task CRUD + Assignments
Full task lifecycle via /api/dispatch/tasks/dispatch. Create, read, update dispatch tasks and manage assignment chains per task ID.
Every field worker. Every job. One map.
FleetDispatchMapClient plots active jobs and team members across all verticals in a geospatial view. Jobs array and team array pipe in from the dispatch board. The map reads position data in real time.
- Real-time geospatial view of all active jobs and team positions
- FleetDispatchMapClient renders job markers and team-member markers on a single canvas
- Cross-vertical jobs feed: cleaning crews, delivery drivers, local pros, guides on one map
- Graceful empty-state rendering when no active jobs or team members are in the field
Operational state of every resource. One grid.
ResourceStatusHubClient provides a bird's-eye operational status view, showing which resources are available, in-progress, blocked, or completed, across all active verticals.
Resource Status Grid
ResourceStatusHubClient renders an operational grid showing the current state of every dispatchable resource, including rooms, vehicles, zones, stations.
Cross-Vertical Visibility
A single status board view that spans cleaning status, rental fleet availability, restaurant table states, and gym equipment readiness.
Real-Time State Transitions
Resources move between states (dirty → cleaning → ready, available → dispatched → returning) as field workers complete tasks.
24 carriers. Multi-leg handoff. Stuck-package detection.
The shipping connector layer provides the carrier abstraction. The handoff engine orchestrates multi-leg chains, monitors dwell time, onboards local couriers, and fires automatic actions on leg transitions.
Multi-carrier chain orchestration. Stuck-package detection.
The handoff engine manages the complete last-mile handoff lifecycle. From shipment planning through leg-by-leg execution to delivery proof. HandoffDashboardClient renders the operational view.
Multi-Leg Chain Orchestration
HandoffOrchestrator plans and executes multi-carrier shipment chains. Each chain tracks legs (international → domestic_trunk → last_mile → pickup_point), handoff points, and dwell-time thresholds.
Stuck Package Detection
StuckPackageDetector monitors dwell time at each handoff point. When maxDwellTime is exceeded, the system fires a StuckPackageAlert with severity (warning/critical), reason, and suggested remediation actions.
Local Courier Onboarding
CourierOnboardingService manages courier profiles: coverage areas (country/city/postal/radius), capabilities (standard, express, same-day, white-glove, temperature-controlled, oversized), SLA definitions, and performance scoring.
Last-Mile Providers
Three pluggable provider types: LocalCourierProvider (private fleets), DeliveryAppProvider (delivery app connectors), and PickupPointProvider (locker/pickup networks). Each implements quote → book → track → cancel.
Event Bridge & Trigger Rules
EventBridge normalizes raw carrier events into HandoffEvents. HandoffTriggerRules fire automatic actions (book_next_leg, assign_courier, notify_receiver, escalate, reroute) when conditions match on a leg transition.
Handoff Analytics
HandoffAnalyticsService aggregates success rate, average transit days, average handoff dwell hours, carrier performance breakdown, top stuck reasons, and handoff-point utilization metrics.
24 carriers. Three continents. One abstraction.
The shipping connector layer provides a unified IShippingCarrier interface (createShipment, getRates, trackPackage, validateAddress), backed by carrier-specific clients with retry logic, rate limiting, and authentication handling.
Global
Europe
Latin America
Africa
Forms, action links, and scan triggers, in context.
Data capture and task completion happen inside the dispatch flow. Cross-product bridges push events to Pulse, Reputation, and Sync.
Forms, action links, and scan triggers, inside the dispatch flow.
Data capture and task completion happen within the dispatch context. No context-switching to separate apps.
Forms Core
AppForm component (appName: "dispatch") embeds structured data-capture forms directly in dispatch flows. Service feedback, inspection checklists, and completion reports render inline without leaving the dispatch context.
Forms engine → /dispatch/formsAction Links
Token-based action URLs generated via /api/dispatch/action-links. Target entities: appointment and reservation. Each link type has a configurable expiry (defaultExpiryMinutes). Recipients complete actions (confirm, reschedule, rate) without authenticating.
Action links engine → /api/dispatch/action-linksScan-Complete Trigger
POST /api/dispatch/scan-complete fires when a field worker scans a QR or barcode to mark a task done. The scan event propagates to the status board and triggers downstream handoffs.
/api/dispatch/scan-completeOperational KPIs from field to dashboard.
DispatchMetricsClient renders performance data pulled from /api/dispatch/metrics. HandoffAnalyticsService feeds carrier-level performance, stuck-chain analysis, and handoff-point throughput.
- DispatchMetricsClient: dedicated metrics dashboard at /dispatch/metrics
- Per-vertical KPIs via /api/dispatch/metrics endpoint
- Handoff analytics: success rate, avg transit days, avg dwell hours, carrier performance
- Top stuck reasons and handoff-point utilization tracking
- Carrier breakdown: on-time, late, failed counts and average delivery days per carrier
- Period-based aggregation: totalChains, completedChains, activeChains, stuckChains
Dispatch events flow into Pulse, Reputation, and Sync.
Dispatch is not isolated. Completed tasks, field-service events, and delivery orders propagate to sibling products through dedicated API bridges.
Pulse → Field Services
POST /api/dispatch/pulse/field-services pushes completed field-service events into Calisto Pulse for revenue attribution and service-completion analytics.
/api/dispatch/pulse/field-servicesReputation → Service Complete
POST /api/dispatch/reputation/service-complete fires when a dispatch task finishes. Reputation product picks up the event to trigger review-request flows.
/api/dispatch/reputation/service-completeSync → Delivery Orders
GET /api/dispatch/sync/delivery/orders surfaces delivery-order data to the Sync product for cross-platform order reconciliation.
/api/dispatch/sync/delivery/ordersHigh-Performance Ops. Zero Monthly Overhead.
Get all 15 Core modules at no monthly cost. You only pay 2% of processed revenue.
Dispatch
Field coordination, fleet tracking, and multi-carrier shipping.
Part of Ops Suite
Wallet-debit
Add to Pro Shop