What problem does it solve?
Field operations often rely on fragmented dispatch, tracking, scheduling and evidence tools.
Part of HalNora One · Independent product
In developmentMulti-vertical dispatch & field operations
One dispatch foundation. Multiple operating models.
HalNora Dispatch is being developed as a configurable work-execution platform for courier and delivery, taxi and on-demand transportation, non-emergency medical transport (NEMT), and field-service or contractor operations. Each vertical keeps its own workflow while reusing the same reliable dispatch foundation.
Designed around
- Courier & multi-stop delivery
- Taxi & on-demand transportation
- Non-emergency medical transport
- Field service & contractor work
- Drivers, technicians, vehicles & resources
- Evidence, tracking, scheduling & settlement
Current status
V22 remains the separate HalNora One commercial Dispatch foundation. Multi-vertical Work, tracking, evidence, pricing, scheduling, fleet/resource and customer-tracking foundations are established in development; device, provider, security and field-acceptance gates remain open.
Live development statusActive development
Current focusCourier/delivery, taxi, NEMT and field-service execution models; native Driver/Communications integration; Booking/Marketplace contracts; device, integration and release validation.
Last updatedOctober 12, 2026
The live status feed is temporarily unavailable. Showing the last published snapshot.
Investor view
Problem, capability, connection and current stage.
HalNora separates demonstrated development progress from future product direction so scope can be understood without treating roadmap items as commitments.
What is it being built to do?
A configurable execution foundation for courier/delivery, taxi, NEMT and field-service or contractor workflows.
How does it connect?
Connects with Marketplace and Booking for work intake, Communications for field coordination, Payments for authorized payment workflows, and Accounting/CRM through controlled events.
Where is it today?
Active V22 development and validation. Dispatch Entry, V21 and Phase 3C/MS1 are separate tracks; V22 commercial release remains subject to device, provider, security and field acceptance.
Dispatch portfolio
Four independent tracks with different purposes.
HalNora does not merge the current Dispatch efforts into one version chain. Each track has its own scope, audience and acceptance path.
Dispatch Entry · V20-first
A standalone entry product preserving proven V20 courier/merchant workflows while selected modern controls and V21-derived capabilities are added behind familiar screens.
Explore Dispatch Entry →V21
A separate field-used/legacy operational reference. It contributes proven lessons but is not the Entry product, Phase 3C or V22.
Phase 3C / MS1
An independent guarded staging/acceptance track. It is not grouped into V21 and is not part of V22.
V22
The separate HalNora One multi-vertical commercial foundation for courier/delivery, taxi, NEMT and field-service execution.
Dispatch verticals
Different industries. Different workflows. One execution foundation.
HalNora Dispatch is not being designed as courier-only software. The shared Work model, routing, tracking, resources, evidence and communications are configured around the operating model of each vertical.
Courier & delivery
Multi-stop pickups and deliveries, route planning, scanning/load management, POD, COD/settlement, recurring routes, customer tracking and merchant workflows.
Taxi & on-demand transportation
Passenger pickup/drop-off, driver availability, live assignment, ETA/tracking, shift state, communications and payment-capable field workflows.
Non-emergency medical transport
Scheduled and recurring trips, return journeys, arrive-by timing, wait-and-return, mobility/resource requirements and privacy-aware transport coordination. HalNora is not positioning this as 911 emergency dispatch.
Field service & contractors
Technician jobs, skills/equipment requirements, service areas, recurring maintenance, configurable forms, evidence, customer updates and handoffs from Marketplace or Booking.
Current direction
What this product is being built to do.
Public descriptions reflect current development direction and do not imply general availability or production certification.
Work & multi-stop orders
Create and manage pickups, deliveries, extra stops, requirements, charges and auditable lifecycle history.
Driver/worker & resource assignment
Match work to people, vehicles, skills and equipment while preserving accountable ownership.
GPS, presence & Auto Arrival
Separate location freshness, online presence and shift state, with configurable arrival logic for pickup and destination.
Proof of delivery & evidence
Capture photos, signatures, recipient details, age checks, OTP, safe-drop and other configurable evidence where appropriate.
Route planning & auto-dispatch
Build toward single/multi-route planning and generalized auto-dispatch using resource requirements and operational constraints.
Settlement & invoicing
Keep driver settlement and customer invoicing distinct, auditable and based on authoritative completion state.
Customer tracking & alerts
Use operational state to power dynamic ETA, tracking and meaningful customer notifications.
Offline-aware field execution
Show pending/not-received device actions clearly and reconcile safely against server-authoritative state.
Fleet & inspections
Support vehicle assignment, maintenance/registration reminders, expenses and configurable inspection/checklist workflows.
Connected field apps
Dispatcher, driver/worker and merchant/customer-facing surfaces are designed around the same authoritative Work model rather than duplicated business logic.
Product boundary
Dispatch owns field execution.
Dispatch owns Work, drivers/workers, routing, execution state, POD/evidence and operational settlement. Marketplace owns commerce and Marketplace pricing; Booking owns appointments; POS owns sales; Accounting owns the books.
HALNORA ONE ARCHITECTURE
Connected, not coupled.
Cross-product workflows use explicit contracts, authenticated events and clear authority so one product does not silently take over another product’s records.
How the HalNora platform works →What comes next
Development priorities.
HalNora prioritizes reliability, security, recoverability and real-world validation over feature count alone.
Search themes: courier dispatch software, delivery management software, taxi dispatch software, NEMT scheduling software, non-emergency medical transportation dispatch, field service dispatch, contractor dispatch, driver tracking, route optimization and proof of delivery.
Product inquiry
Interested in Dispatch?
Talk with HalNora about product direction, commercial use cases, partnerships or investment.