Same-day parcel and document · San Francisco

Same-day courier dispatch software in San Francisco — multi-stop, PoD, B2B invoicing.

Taxi dispatch system calibrated for courier work in San Francisco. TLC, BACP, DFHV, LADOT and SFMTA ready. Multi-stop routing, proof-of-delivery photo + signature, B2B invoicing.

Courier dispatch within a taxi fleet uses the same physical fleet for parcel and document work alongside passenger trips. It needs multi-stop route optimisation, proof-of-delivery capture (photo + signature), client account invoicing on a separate billing cadence to passenger work, and the ability to slot courier trips against passenger demand without starving either.

San Francisco courier dispatch — the operating reality

Courier work that runs on the same fleet as passenger trips needs explicit slotting. The Aurora console treats courier jobs as a distinct trip class with their own pricing, billing, and PoD requirements; the dispatcher sees both layers and the auto-dispatch logic respects the constraint that a vehicle on a multi-stop courier route shouldn't be offered a passenger pickup mid-route.

San Francisco courier dispatch — how TaxiCloud handles it

Proof-of-delivery (photo + signature on the driver app) is captured against every drop; the data is attached to the trip record and exposed to the client account via API or self-serve portal.

San Francisco courier dispatch — migration + go-live

B2B account invoicing runs on a monthly statement cadence distinct from passenger work. Per-client pricing tiers, surcharge rules, and credit limits are tracked at the account record.

FAQ

Courier taxi dispatch San Francisco — questions answered.

Can passenger and courier work share a fleet?: Yes. Each trip class is dispatched discretely; vehicles on multi-stop courier routes aren't offered passenger pickups mid-route.
Is proof-of-delivery captured?: Yes. Photo + signature against every drop, exposed to the client via API or portal.
How does B2B courier billing work?: Monthly statement cadence per client, with per-account pricing, surcharges, and credit limits.
Where is rider data stored for SF operators?: AWS US-West (Oregon) by default. SF operators with municipal contracts can request US-West-1 (Northern California) residency on the Pro Ultra plan.
How does SFO staging work?: Drivers enter the Aviation Operations holding lot and check in via the driver app. The Aurora console shows queue position per terminal; dispatch respects FIFO.

More San Francisco dispatch services

Ready when you are

Dispatch on autopilot.

14-day free trial. No card. Cancel anytime.

47 fleets joined this month · Talk to sales