Know the condition.Not only the location.
Dispatch turns route, temperature, light, motion, battery, signal, and freshness telemetry into customer-safe operational state, exceptions, and practical next actions.
Dispatch is not generic parcel tracking. It is an applied proof surface for shipments where condition, confidence, and exception handling matter.
Shipment / masked-218c
Cold-chain sample route · customer-safe view
Origin
Hub
Hold
Delivery
Shipment state
In transit
Route active, next stop in review window
Freshness
8 min
Latest event received within expected cadence
Condition
Watch
Temperature trending toward threshold
Next action
Review hold time
Check dwell time before next handoff
Condition boundary
Temperature is trending toward threshold. Review dwell time; do not infer damage or responsibility.
Product walkthrough
See the operatingsurface in motion.
The recorded demonstration moves through the Dispatch operations experience: resources, planning context, and shipment state used to understand what is happening and what requires attention.
Recorded product demo
Dispatch / v2
Operator experience
From signal noiseto the next safe action.
Operators see route, freshness, condition, confidence, device health, and exception state together—without interpreting raw tracker protocols.
Event timeline
Honest state ordered by event time
01
Route and position
Last-known position, stop state, route segment, and arrival context without exposing raw tracker identifiers.
02
Condition telemetry
Temperature, light exposure, motion, and possible opening indicators become reviewable operational states.
03
Freshness model
Fresh, delayed, stale, unavailable, duplicate-merged, and late-ordered updates remain visible.
04
Exception review
Condition alerts create next-action review items, not automatic claims about damage or responsibility.
05
Device health
Battery and signal health show whether silence is expected, suspicious, or under review.
06
Customer-safe output
Support and logistics teams receive operational answers rather than raw payloads, topics, and protocol noise.
Telemetry and trust
Preserve the signal.Bound the conclusion.
Dispatch preserves source value, event time, freshness, and interpretation while preventing a condition signal from silently becoming a damage, liability, or live-tracking claim.
Source → governed output
| Source | Value | Normalized | Customer state |
|---|---|---|---|
| tracker.temp_c | 7.8 | temperatureCelsius | Watch |
| tracker.light_lux | 182 | lightExposureLux | Under review |
| tracker.motion_g | 0.42 | motionEvent | No impact claim |
| device.battery_pct | 64 | deviceHealth.batteryPercent | Healthy |
Customer-safe event
{
"shipmentRef": "masked-shipment-218c",
"routeState": "in_transit",
"eventTime": "2026-07-20T09:54:00-07:00",
"freshnessState": "fresh",
"conditionState": "under_review",
"signals": { "temperatureCelsius": 7.8, "lightExposureLux": 182 },
"claimBoundary": "not_damage_proof",
"nextAction": "check_handoff_notes"
}08:42–09:18
Temperature drift
Trending toward threshold
Review hold time before handoff
09:48–09:54
Light exposure
Possible opening or staging exposure
Check notes; do not infer damage
10:03–10:11
Late ordered packet
Event time preserved
Merge by event time; show delay
Product boundaries
No guaranteed live tracking when telemetry is delayed, stale, or unavailable.
No automatic proof of damage from condition alerts.
No raw tracker payloads, topics, identifiers, or protocol internals in customer-facing views.
No claim that Dispatch is a universal logistics platform for every carrier and mode.
Evaluation
Start with one lane.Prove one operational answer.
A serious Dispatch evaluation begins with a bounded condition problem, representative telemetry, clear escalation rules, and an operator who can validate the result.
01
Best-fit shipments
Cold-chain, laboratory, healthcare, high-value, or exception-sensitive shipments where condition matters as much as location.
02
Buyer problem
Tracking exists, but freshness, condition, confidence, exception, and next-action state still require manual interpretation.
03
Pilot inputs
One shipment lane, tracker path, expected condition signals, escalation rules, and examples of manual follow-up to reduce.
04
Pilot output
A customer-safe view of route state, condition review, tracker health, event ordering, and bounded exception language.
Qualified review artifacts