Field management and coordination, per vertical.
14 vertical-specific dispatch surfaces, each tuned to how that industry coordinates work. 24-carrier shipping layer, multi-leg handoff orchestration, and a cross-vertical command board.
14 industries. 50 sub-pages. One dispatch engine.
Each vertical gets its own dispatch UI tuned to how that industry 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.
Dispatch Board, Fleet Map, Status Board, and Metrics aggregate data from every active vertical into unified operational views.
,0,
vertical-specific dispatch surfaces
,0,
dedicated sub-pages across verticals
,0,
shipping carrier connectors
,0,
access areas (personal · staff · manager)
4 capabilities. 14 verticals. One command surface.
DispatchBoardClient renders a unified work-order queue spanning all active verticals. Filter by vertical, team, area, or status without switching contexts.
Every field worker. Every job. One map.
FleetDispatchMapClient plots active jobs and team members across all verticals in a geospatial view. Position data updates in real time.
Operational state of every resource. One grid.
ResourceStatusHubClient provides a bird's-eye view showing which resources are available, in-progress, blocked, or completed across all active verticals.
24 carriers. Multi-leg handoff. Stuck-package detection.
Carrier abstraction layer with handoff chain orchestration, dwell-time monitoring, and automatic actions on leg transitions.
4 leg types. 3 provider types. Stuck-package detection.
The handoff engine manages the complete last-mile lifecycle, from shipment planning through leg-by-leg execution to delivery proof.
Multi-Leg Chain Orchestration
HandoffOrchestrator plans multi-carrier chains. Each chain tracks legs, handoff points, and dwell-time thresholds.
Stuck Package Detection
StuckPackageDetector monitors dwell time at each point. Fires alerts with severity, reason, and remediation actions.
Local Courier Onboarding
CourierOnboardingService manages profiles: coverage areas, capabilities (express, same-day, white-glove, oversized), SLA definitions.
Last-Mile Providers
Three pluggable types: LocalCourierProvider, DeliveryAppProvider, PickupPointProvider. Each implements quote, book, track, cancel.
Event Bridge
EventBridge normalizes raw carrier events into HandoffEvents. Trigger rules fire automatic actions on leg transitions.
Handoff Analytics
Success rate, average transit days, dwell hours, carrier breakdown, top stuck reasons, handoff-point utilization.
24 carriers. 4 regions. One abstraction.
Unified IShippingCarrier interface: createShipment, getRates, trackPackage, validateAddress. Carrier-specific clients with retry logic and rate limiting.
Global
Europe
Latin America
Africa
Forms, action links, and scan triggers, in context.
Data capture and task completion inside the dispatch flow. Cross-product bridges push events to Pulse, Reputation, and Sync.
3 capture tools. 2 target entities. Zero context switches.
Data capture and task completion happen within the dispatch context. No 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.
Forms engineAction Links
Token-based action URLs via /api/dispatch/action-links. Target entities: appointment and reservation. Configurable expiry. Recipients complete actions without authenticating.
Action links engineScan-Complete Trigger
POST /api/dispatch/scan-complete fires when a field worker scans a QR or barcode. The event propagates to the status board and triggers downstream handoffs.
Scan completion API6 metric classes. Per-vertical KPIs. Carrier breakdown.
DispatchMetricsClient renders performance data from /api/dispatch/metrics. HandoffAnalyticsService feeds carrier-level performance and stuck-chain analysis.
- Dedicated metrics dashboard at /dispatch/metrics
- Per-vertical KPIs via /api/dispatch/metrics endpoint
- Handoff analytics: success rate, avg transit days, avg dwell hours
- Top stuck reasons and handoff-point utilization tracking
- Carrier breakdown: on-time, late, failed counts per carrier
- Period aggregation: totalChains, completedChains, activeChains, stuckChains
3 bridges. 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
Completed field-service events push into Calisto Pulse for revenue attribution and service-completion analytics.
Dispatch Task Complete → Pulse Field Services FeedReputation
When a dispatch task finishes, the event fires to trigger review-request flows in the Reputation product.
Task Status → Closed → Reputation Review RequestSync
Delivery-order data surfaces to the Sync product for cross-platform order reconciliation.
Delivery Orders → Sync Reconciliation EngineHigh-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