Define the service obligation
Tie each departure or request to its current pickup window and instructions.
Airport & Hospitality Shuttles
Passenger transportation operations software for hotel shuttle teams carrying recurring and arrival-linked service from reservation to payment.
Route sequence: Hotel, 06:00; Terminal, 06:25; Hotel, 06:55.
Recurring departures, arrival-linked requests, pickup instructions, capacity, no-shows, guest updates, and actuals must stay aligned.
Tie each departure or request to its current pickup window and instructions.
View vehicles, drivers, waiting groups, no-shows, and later departures together.
Carry the approved pickup point, assignment, escalation, and acknowledgement.
Operating workflow
Dispatch must revise service without assuming an arrival feed or splitting hotel and driver instructions.
Separate guest groups become ready while the planned shuttle is still completing another departure.
Identify current requests, windows, instructions, capacity, and later obligations.
Compare available assignments without treating unconfirmed capacity as committed.
Commit one assignment and the named hotel and driver updates.
Expose stale instructions and keep actuals with the exception.
The six products share one operating record. Network covers approved partners and capacity; TOOSA Billing does not imply funds movement.
Plan. Connect service windows, assignments, and capacity pressure.
Coordinate. Carry driver instructions and approved external options.
Close. Prepare exceptions, actuals, and approved follow-up.
Readiness path
Ready to explore
Review routes, imports, duties, the driver workspace, tracking and history, statistics, administration, and configuration.
Configured for your operation
Define request authority, windows, pickup points, capacity rules, roles, acknowledgements, exceptions, and permitted writes.
Validated before launch
Confirm travel sources, hotel communications, automated action, security, reliability, billing availability, and service reporting.