- Route planCurrent
- Duty 08Scheduled
- Change reviewOpen
The TOOSA product
Six products. One passenger job.
- Vehicle 12Assigned
- CapacityChecked
- Next duty09:30
- Driver briefReady
- AcknowledgementPending
- ActualsOpen
- Owned optionAvailable
- Partner optionAwaiting reply
- TermsReview
- PlannedRecorded
- ActualsPending
- VarianceReview
- EvidenceObserved
- ChecksPassed
- ApprovalRequired
TOOSA Dispatch, Fleet, Crew, Network, Billing, and Automate are products within one system.
Review each responsibility against the workflow, then confirm availability and launch readiness during evaluation.
Give every operating handoff a clear owner.
Each product owns a clear part of the operating record while the workflow stays connected.
TOOSA Dispatch
- Route planCurrent
- Duty 08Scheduled
- Change reviewOpen
Turn the plan into executable trips.
TOOSA Fleet
- Vehicle 12Assigned
- CapacityChecked
- Next duty09:30
Keep vehicle context attached to the job.
TOOSA Crew
- Driver briefReady
- AcknowledgementPending
- ActualsOpen
Coordinate the people doing the work.
TOOSA Network
- Owned optionAvailable
- Partner optionAwaiting reply
- TermsReview
Coordinate owned and partner capacity.
TOOSA Billing
- PlannedRecorded
- ActualsPending
- VarianceReview
Carry the completed job into financial review.
TOOSA Automate
- EvidenceObserved
- ChecksPassed
- ApprovalRequired
Assist within explicit operating authority.
Know what is ready now and what comes next.
Evaluation starts with one real workflow and separates visible product surfaces from future configuration and verified production behavior.
Ready to explore
Explore route, duty, driver, tracking, history, import, user, and configuration surfaces in a guided walkthrough.
Configured for your operation
Map systems of record, roles, permissions, imports, rules, and acceptance criteria to one operating workflow.
Validated before launch
Confirm production connections, populated reconciliation, billing execution, and authorized Automate actions before launch.
Evaluate the product
Bring the workflow that crosses the most responsibilities.
Describe the pattern without sending passenger, driver, payment, credential, or route-record data.