Operator workflows
Explore customer, dispatch, container and billing workflows with seeded records. Connected deployment requires operator acceptance.
Explore Operator workflows →Product availability
Commercial inclusion and production readiness are different decisions. The demo shows workflows; your launch requires configured services, tested data and signed acceptance.
Explore customer, dispatch, container and billing workflows with seeded records. Connected deployment requires operator acceptance.
Explore Operator workflows →Provider configuration, credentials and payment/accounting acceptance must be completed for each deployment.
Explore Payments and accounting →Camera-assisted container observation; measurement accuracy and field reliability remain subject to pilot validation.
Explore TossGauge →Oyster3 (containers) and G70 BLE (trucks) are candidate devices under evaluation; neither has been validated against real hardware yet. Hardware and carrier connectivity are separately scoped.
Explore TossTrack →Truck entry and exit records and movement-based text notifications, subject to hardware and integration validation.
Explore TossTower →Separate consumer app for qualified operator capacity. Local coverage and production activation are required.
Explore TossIt →