Airport & Hospitality Shuttles

Keep departures and arrivals on one service plan.

Passenger transportation operations software for hotel shuttle teams carrying recurring and arrival-linked service from reservation to payment.

TOOSAShuttle service workflow
Recurring serviceMorning shuttle loop
Capacity review

Route sequence: Hotel, 06:00; Terminal, 06:25; Hotel, 06:55.

Recurring service brief

The schedule is only one source of demand.

Recurring departures, arrival-linked requests, pickup instructions, capacity, no-shows, guest updates, and actuals must stay aligned.

Promise

Define the service obligation

Tie each departure or request to its current pickup window and instructions.

Balance

See capacity pressure

View vehicles, drivers, waiting groups, no-shows, and later departures together.

Brief

Keep instructions current

Carry the approved pickup point, assignment, escalation, and acknowledgement.

Operating workflow

Three delayed arrivals compress into one pickup window.

Dispatch must revise service without assuming an arrival feed or splitting hotel and driver instructions.

Trigger

Separate guest groups become ready while the planned shuttle is still completing another departure.

  1. 01
    Link affected service

    Identify current requests, windows, instructions, capacity, and later obligations.

  2. 02
    Compare service choices

    Compare available assignments without treating unconfirmed capacity as committed.

  3. 03
    Approve the service plan

    Commit one assignment and the named hotel and driver updates.

  4. 04
    Confirm the service

    Expose stale instructions and keep actuals with the exception.

Validate before launchConfirm arrival-data access, guest communication, capacity ownership, and service-result measures before launch.

What to evaluateCheck that pickup instructions and operating authority stay current through a demand change.

Product path

Six products follow the same operating job.

The six products share one operating record. Network covers approved partners and capacity; TOOSA Billing does not imply funds movement.

01

TOOSA Dispatch + TOOSA Fleet

Plan. Connect service windows, assignments, and capacity pressure.

02

TOOSA Crew + TOOSA Network

Coordinate. Carry driver instructions and approved external options.

03

TOOSA Billing + TOOSA Automate

Close. Prepare exceptions, actuals, and approved follow-up.

Readiness path

Move from exploration to launch validation.

Ready to explore

Explore scheduled-work tools.

Review routes, imports, duties, the driver workspace, tracking and history, statistics, administration, and configuration.

Configured for your operation

Fit the shuttle service.

Define request authority, windows, pickup points, capacity rules, roles, acknowledgements, exceptions, and permitted writes.

Validated before launch

Validate production connections.

Confirm travel sources, hotel communications, automated action, security, reliability, billing availability, and service reporting.