Fare Before Booking
A regulated fare estimate shown before the booking is confirmed, calculated from the authority's published tariff.
Passenger App
Your app, or ours
Most authorities already run a passenger app. Ours is optional, and our dispatch API lets the app and website you already own book against the same engine. If you do want an application, this is what it does.
Bring your own app
You may already have an app
Most transport authorities we speak to already run a passenger app. It usually carries the city identity, it was often built under a separate contract, and people already have it installed. We do not ask you to retire it.
Tanzim dispatch is available through a documented API. Your existing app, your website, your call centre software or a third-party booking channel can all book against the same allocation engine. Our Passenger App is there if you want it. It is not a condition of using the platform.
Your appYour website
Third-party channelsCall centre
What the dispatch API exposes
- Regulated fare quotation before the booking is confirmed
- Create, amend and cancel bookings
- Allocation status, assigned vehicle and estimated arrival
- Live vehicle position during approach and journey
- Driver and vehicle identity to display to the passenger
- Accessible vehicle requests under the same priority rules
- Trip completion with the fare breakdown and receipt data
- Complaint submission bound to the trip record
- Webhooks on every status change, so you are not polling
- Sandbox environment and documentation for your own developers
Oversight does not depend on which app was used
A booking made in your own app, in a third-party app or over the phone produces the same trip record as one made in ours. The allocation decision, the regulated fare, the driver and vehicle identity and the route are all written to the same place.
That is the point of putting dispatch under the authority rather than under each booking channel. You keep one view of the licensed fleet no matter how many front doors the public uses to reach it.
Public confidence is the product
Passengers do not distinguish between an unlicensed vehicle and a licensed one until something goes wrong. An official booking channel is how an authority makes the licensed option the easy one.
- Unlicensed vehicles competing on convenience rather than compliance
- Fares disputed after the trip because no estimate was given before it
- Accessible vehicles difficult to request and slow to arrive
- Passengers without bank cards excluded from app-based booking
- Complaints with no trip record attached to investigate
What a passenger gets
The functions people expect from a modern booking app, with the parts a regulator cares about built in rather than added later.
Verified Vehicle and Driver
Licence number, vehicle registration, photograph and licence class shown on arrival, so the passenger can confirm the vehicle is the one dispatched.
Accessible Vehicle Requests
Wheelchair accessible vehicles requested directly, allocated under priority rules, with the response target the authority has set.
Cash, Card and Wallet
Card, digital wallet and cash all supported. Passengers without a bank account are not shut out of the official channel.
Live Tracking and Sharing
Vehicle location during approach and journey, with the option to share the trip with a chosen contact.
Receipts and History
Every completed trip stored with its route, fare breakdown and vehicle details, available to the passenger and attachable to a complaint.
Scheduled and Return Trips
Advance bookings, return journeys and recurring trips for commuters, medical appointments and school runs.
Complaint Route
A complaint raised from the trip itself, arriving at the operator and, where the rules require it, at the authority, with the record already attached.
Designed for everyone the city serves
A public-facing service cannot be usable only by people with recent phones and good eyesight. The application is built to WCAG 2.2 AA, supports screen readers and large type, and runs in both left-to-right and right-to-left languages including Arabic.
WCAG 2.2 AAScreen reader supportArabic and RTLLow-end device support
Reach
Nobody is left without a way to book
App-only booking excludes people. The authority's channel has to cover the whole population it is responsible for, not the part that is easiest to serve.
- Telephone booking handled by the same dispatch engine
- Street and rank hailing recorded in the same trip record
- Cash accepted without penalty or restricted service
- Runs on older Android devices and modest connections
- Web booking for passengers who will not install an application
- Arabic and right-to-left layout supported throughout
- Carries the city or authority brand, not a vendor brand
- Trip record available to the passenger after the journey
Works with
The rest of the platform
The official way to book a licensed trip
We can show the application running under your own branding, tariff and licensing conditions.