Bookings · Dispatch · Drivers
Transport Operations
Bookings, dispatch and driver assignment for taxi and car hire operators — built around how bookings actually arrive here, on WhatsApp.
Building this now. The demo below is real. First customers help shape it and get founding pricing.
The problem
What this is actually for
Bookings arrive as WhatsApp messages and get copied into a paper diary, or not copied at all.
Two drivers get sent to the same job, or nobody gets sent to the 06:00 airport run.
A customer asks what you quoted them last month and there is no way to check.
A vehicle is held at a roadblock because its COF ran out last week and the date was in somebody’s head.
The operator is the only person who knows what is happening today.
Who it is for
- Taxi firms
- Car hire companies
- Tour operators
- Lodge and hotel shuttles
Built with
- Phonex Taxi
Airport transfers and town work in Blantyre
- R&H Car Rentals
Car hire from a staffed desk at Chileka Airport
Our clients, whose day-to-day work shaped this. They are not customers of the product — it does not exist yet for anyone to be a customer of.
Try it
A day on the board
A realistic Blantyre day: airport runs, town trips, one long haul to the lakeshore. Assign a driver, open a booking, filter by status. Then paste a WhatsApp message in and watch it become a booking.
Still need a driver
Friday · 8 bookings
Unassigned
Drag a booking onto a driver, or use Assign.
Chikondi Banda · Voxy · BT 4471
Thoko Mvula · Hilux Double Cab · BT 8823
Mphatso Zulu · Honda Fit · BT 2019
Yamikani Phiri · RAV4 · BT 6640
Sample data. Nothing is saved — the board resets when you reload.
Fares shown are our estimates, not a published tariff. Malawian taxi fares are agreed per journey.
And where the bookings come from
Nobody fills in a booking form. They send a message. This is the same message, read by the software instead of by whoever is holding the phone.
The message that arrives
Change the message and try again — misspell a place, leave the time out, ask for six people.
What the operator gets
Press the button and this fills in — pickup, destination, time, passengers, and which vehicle to send.
Sample data throughout — the businesses, people and figures are invented. Nothing you do here is saved.
Where it stands
What is built, and what is not
The left column is everything you have just used. The right is everything you have not, because it does not exist yet.
Built
- The dispatch board you can use below — assignment, conflicts, filtering
- Parsing a free-text WhatsApp message into a structured booking
- Vehicle suggestion from passenger count and journey type
- Two live client sites whose real workflows shaped this
Not built yet
- Saved bookings — nothing on this page persists yet
- Driver accounts and a phone view for drivers
- Automatic WhatsApp confirmation back to the customer
- Quote history per customer
- COF, insurance and road tax expiry, chased before they lapse
- Service schedules by mileage, per vehicle
- Fuel and running cost per vehicle, so you know which car earns
- Daily and weekly takings by driver and vehicle
The order these get built in is not fixed. It is one of the things a first customer gets a say in.
Be one of the first to use it
Transport Operations is not finished, and we are not going to pretend otherwise. What early customers get is real influence over what gets built and in what order, founding pricing that we will not raise on you, and us on the end of a phone. What we get is someone telling us where it is wrong.
Not this one? The other two — or tell us what you actually need.