Operations
The operator workspace on Mac and Windows: booking records, quotations, chauffeur allocation and oversight of the journey workflow.
THE OPERATIONAL PLATFORM
Booking logic.
Dispatch workflows.
Operational control.
Connect bookings, dispatch, payments and client service in one operational workflow. Give your team visibility across journeys, coordinate chauffeurs and manage an existing fleet or a new transport business.
AIRPORT TRANSFERAirport → Home
Awaiting paymentSecure payment
CLIENT PAYMENTPayment confirmationPayment processed
PaymentInvoiceWeekly payout
Client selects the journey and proceeds to payment.Illustrative
CLIENT APPComplete your bookingAirport pickup · Home destination
CHAUFFEUR APPAvailableReady for the next assignment
01 APPLICATION ROLES
Three roles.
One operating model.
Chauffeurs
Mobile workflows for job offers, assignments and journey status updates, connecting the chauffeur with operations.
Clients & passengers
Client booking and account workflows, with a separate, restricted journey view for permitted passengers.
London provides the first live operating reference. For your deployment, we agree the workflows, integrations, delivery plan and onboarding slot before the first payment.
02 WORKFLOW LOGIC
The operational detail
behind every journey.
Quote-to-booking workflow
Structure enquiries, quotations and booking records around the information an operator needs to confirm and coordinate a journey.
Dispatch orchestration
Chauffeur assignment, job offers and responses, with the operator in control of allocation decisions.
Journey lifecycle
Organise journey states, actions and updates around each role, from the assigned chauffeur to the customer and permitted passenger.
Fleet data & eligibility
Vehicle and chauffeur records, supporting documents and eligibility workflows within the agreed deployment scope.
Identity & permissions
Distinct access for operations, chauffeurs, clients and permitted passengers, with information and actions defined by role.
Payment integrations
Connect customer checkout and payment status with booking records. The London platform includes Stripe integration for customer payments; providers and enabled workflows are agreed for each deployment.
Chauffeur earnings & settlement
The settlement design covers chauffeur earnings, approval, scheduled bank payouts, reconciliation and self-billing. Provider connections and delivery milestones are defined in the implementation scope.
Financial document workflows
Payment records and client financial documents are defined around the operating requirements. Reporting and billing workflows are specified in the agreed scope.
03 CITY APPLICATIONS
Dedicated applications.
A maintained core.
Each City Partner setup includes a dedicated client app and a dedicated chauffeur app, both for iOS and Android.
The city deployment model combines a maintained software core with local configuration for operator identity, services, currency, time zone and operating rules.
Each app carries the Black Fleet city identity alongside the operator workspace for Mac and Windows computers. Both apps are included in City Launch setup, with release, distribution and onboarding scheduled as part of the city implementation.
Explore the architecture04 PLAN YOUR DEPLOYMENT
Your fleet.
Your implementation plan.
Tell us about your existing fleet or the business you want to launch. We will review the operating requirements, discuss the platform and define the scope and delivery schedule with you.
Your enquiry starts the assessment. Scope, delivery milestones and an onboarding slot are agreed before the first payment. Platform walkthroughs and evaluation access are arranged as part of that discussion.
View subscription plans