Overview
Booking Status
Booking Source
Flight Tracking
Revenue Over Time
God's Eye
Upcoming Bookings
Next bookings by pickup date/time| Reference | Customer | Trip | Pickup | Vehicle | Flight | Flight Status |
|---|
Bookings
| Reference | Status | Customer | Trip | Pickup | Driver | Fare |
|---|
Partners
Load your current driver partners here now — their profiles will already exist once the Driver App ships, so they'll claim an existing profile instead of signing up from scratch.
| Name | Mobile | License | License Expiry | Vehicle | Ownership | Rating | Status |
|---|
Vehicles
Each driver partner brings their own vehicle — track it here with its documents (registration, roadworthy certificate, insurance) since it isn't a company-owned asset. Link a vehicle to a driver from the driver's own form.
| Make & Model | Year | Registration | Type | Ownership | Driver | Status |
|---|
Suppliers
Third-party companies you source Bodyguards and Armoured/Non-Armoured vehicles from as needed. Drivers are independent partners with their own vehicles, so they're managed separately under the Drivers tab.
| Company | Contact Person | Mobile | Supplies | Status |
|---|
Fare Rates
The current base, per-kilometer, per-minute, minimum fare, and extended airport-waiting fee for each vehicle category, matching the options in Quick Book's own Vehicle Type field exactly. Edit a row and click Save to update it — every fare quoted across Quick Book, the customer app, and the public widget reads live from these same rates. Waiting Fee applies once a flight's landed and the free 60 minutes (or 90, if a driver-requested grace period is granted) have passed, billed per hour of extra wait beyond that.
| Vehicle Type | Base Fare (R) | Per KM (R) | Per Minute (R) | Minimum Fare (R) | Waiting Fee (R/hr) |
|---|
Optional Extras
Fixed fees for optional extras, applied on top of the metered fare for any booking that requests them. Currently R300 per baby seat, per booking.
Armoured Bodyguard Fees
The fixed bodyguard fees used for Armoured bookings — separate from the Armoured SUV vehicle rate above, since a bodyguard is booked and charged on its own schedule. See the Armoured & Bodyguard Fees notes on a booking's own detail view for how these apply.
Explore Picks
Bars, restaurants, and events shown in the customer app's own Explore tab. Each one needs a name and description at minimum - an image is optional, and should be a real photo you host yourself, not a placeholder.
| Category | Name | Neighborhood | Description | Featured |
|---|
Explore Ad Banners
Advertising images shown in a rotating banner beneath Curated For You on the customer app's own Explore tab. Add and remove these whenever you like - the customer app always shows whatever's currently in this list.
| Image | Link | Clicks | Order |
|---|
Clients
Individual clients. Link one to a corporate account so their bookings draw from that company's shared prepaid balance instead of being billed to them directly.
| Name | Mobile | Passport/ID | Corporate Account | Status |
|---|
Corporate Accounts
A company loads funds onto its account in advance, then any client linked to it can book against that balance until it's depleted. Every top-up and every booking charge is logged — click a row to see the full transaction history.
| Company | Contact Person | Mobile | Balance | Status |
|---|
Invite Codes
The customer app is invite-only — signup requires one of these codes. Each code works exactly once; the moment it's used to create an account, it can never be used again.
| Code | Status | Used By | Created | Used |
|---|
Panic Alerts
Triggered by a driver's 2-second press-and-hold panic button in the Driver App. This only records the alert and notifies staff here — there is no live third-party emergency dispatch (e.g. Aura) connected yet, so treat every alert as something that needs a real phone call, not an automated response.
| Driver | Trip | Location | Triggered | Status |
|---|
Route Incidents
Accidents, construction, and other road incidents Mapbox's traffic-aware routing detected along a driver's active navigation route — this is Mapbox's own aggregated traffic data, not something a driver personally reported.
Incident Location
| Driver | Trip | Type | Reported | Status |
|---|
Terminal Arrivals
Fires when a driver's GPS position reaches a defined airport terminal area — this is proximity detection using the driver's regular location reporting, not true tracking inside the building itself. GPS becomes unreliable once genuinely indoors, so this marks arrival rather than following movement within the terminal.
| Driver | Trip | Location | Arrived | Status |
|---|
Airport Info
Live incoming flights via Flightradar24 — separate from per-booking flight tracking on each booking's own detail view. Refreshed at most every 5 minutes.
Live Flight Tracking
Terminal View
Flight Status
Today's Numbers
Busiest Origins
No arrivals to summarize yet.
Recent Flight Activity
No recent activity yet.
Incidents
Reporting an incident holds that booking's driver payout. Click a row to review evidence and resolve it — resolving with No Penalty releases the payout as-is for the next payment cycle; Penalty Applied deducts the chosen % of the fare from what's owed.
| Booking | Type | Description | Status | Outcome | Reported |
|---|
Fleet Tracking
Live location from the Driver App, for any driver who's gone online — a driver only shows a location once they've toggled online themselves and at least one GPS update has landed; otherwise it says so honestly rather than guessing. Click a vehicle for details, or use "View on map" in the table below to open their exact position in Google Maps.
| Driver | Vehicle Type | Status | Live Location |
|---|
Cash Flow
Last 6 months — Income vs ExpenseExpense Breakdown
This monthRecent Pay History
Driver and supplier payments actually made| Paid To | Description | Amount | Last Updated |
|---|
Driver Payments
| Driver | Trips | Owed | No-Shows | Held |
|---|
Supplier Payments
| Supplier | Booking | Description | Amount | Status |
|---|
OTA Payments
Revenue Luxride Connect is owed from each OTA for bookings they sourced, and when that payment is expected — the reverse direction from Supplier Payments. Expected dates are calculated directly from each OTA's own stated payment cycle rules, not tracked or confirmed against anything the OTA has actually reported paying.