Dispatch software for United States fleets

Yes. Black car and livery work is pre-booked and account-billed rather than street-hailed, so the parts that matter are corporate accounts with cost centres and consolidated invoicing, vehicle-class rules that genuinely change the price, quoted fares that do not silently recalculate, and flight tracking that moves the pickup. Those are covered. Hourly as-directed charters are not a first-class booking type today — if that is a significant share of your work, raise it on the demo call.

It handles the operational side: recurring and standing bookings, arrival windows, will-call returns, per-passenger requirements and an exportable trip record for billing and review. It does not ship pre-built connections to specific Medicaid brokerages or state billing portals. If your contract requires submitting to a particular broker's system, ask about it before you evaluate anything else, because that integration work is the deciding factor rather than the dispatch itself.

Licensing in the United States is set locally rather than nationally — a TLC licence in New York City, airport permits per airport, and separate state or city rules elsewhere — so the requirements differ by where you operate. What the software does is track driver and vehicle documents against whatever set you configure and suspend a driver from dispatch automatically the moment a credential expires. Confirm which permissions and records apply to you with your own city or state authority.

Per active driver per month, in USD: about $14 for fleets up to 20 drivers, $11 from 21 to 100, and from $9 above 100, with a one-time setup quoted to your fleet. There is no per-booking fee, which matters if you expect volume to grow. The full breakdown, including the monthly minimum, is on the pricing page.

Stripe is the default, including Stripe Connect for driver settlements, and Apple Pay and Google Pay are supported for passenger payment. Corporate account work does not need a gateway at the point of travel at all — it is billed on the account and invoiced on the client's cycle.

The migration protocol targets a 14-day go-live and is published in full so you can judge the steps before committing. It covers drivers, vehicles, customer accounts and historical bookings, with a parallel-running period so your dispatchers move across when they are ready rather than on a fixed date. What takes the time is almost always extracting usable history from the outgoing system, so ask your current vendor what your export contains early.

The passenger app and the web booker carry your name, colours and identity, and the booking widget sits on your own domain. The driver app is always TaxiDex-branded — we do not white-label it. It is worth pressing any vendor who says their driver app is "yours" on what that means in the app stores.