No card asked for · nothing taken from a booking · your data exports
Base helps a small airport, private-driver or minibus transfer operator turn a route, pickup time and passenger request into one dispatchable booking. Confirmation checks the service zone, passenger and luggage limits, driver eligibility, vehicle suitability and every blocking period. Driver and vehicle are assigned together, so staff never promise a transfer with only half of the required capacity.
This profile fits a small airport-transfer, chauffeur or minibus operator that prices known routes or zones, checks passenger and luggage requirements, and dispatches its own eligible drivers and vehicles. It supports manual flight-reference updates, waiting and no-show decisions, atomic reassignment, pickup progress and drop-off evidence.
The lifecycle joins the route and party to one atomic driver-and-vehicle assignment.
The operator creates supported routes or zones, transfer types, passenger and luggage limits, durations, buffers, price lines and waiting policies. Vehicles hold real capacity and relevant attributes. Drivers receive shifts and required credential references; Base does not invent licences or calculate a live metered fare.
A request includes pickup, drop-off, local time, passenger count, luggage and approved additional needs, plus an optional flight reference. Verification creates a reviewable request. A route outside the active service zone or a party with no suitable vehicle remains unconfirmed for dispatcher action.
Dispatch chooses or resolves an eligible driver and suitable vehicle. Base checks credential expiry, shift, service zone, seats, luggage and all existing reservations including travel and turnaround buffers. Both resources are reserved together or the transfer remains unassigned.
A time or flight-reference change can trigger a fresh allocation check. Reassignment first reserves the replacement driver and vehicle in one transaction, then releases the previous assignment. If the replacement conflicts, the confirmed allocation stays intact and staff receive a refusal to resolve manually.
The driver sees only assigned operational details, records arrival and pickup, then marks the transfer in progress and captures drop-off evidence. After the configured waiting rule, authorised staff may record a no-show with reason. Completion or no-show releases the remaining blocking period according to the recorded decision.
A free vehicle is not enough when route, party, luggage, driver and travel buffers also constrain the promise.
The booking records adults, children where relevant, luggage and approved accessibility or equipment requirements before allocation. Vehicle seats and luggage limits are checked against the complete party. An unsuitable vehicle stays unavailable for that request even when its calendar is empty.
A confirmed transfer needs both an eligible driver and suitable vehicle across pickup, journey and configured buffers. Base reserves them in one transaction. A collision with either resource prevents confirmation instead of leaving staff with a vehicle-only or driver-only promise.
Staff can record a changed flight reference or manually reviewed time while preserving who changed it and when. The new schedule is not accepted until allocation is rechecked. A missing external feed never moves a confirmed transfer silently or erases the previous pickup instruction.
Transfer availability is the intersection of route rules, party fit and two exact resource calendars.
The vehicle must have enough approved seats and luggage capacity and meet any released accessibility or equipment requirement. The driver must be active, on shift and hold required current credentials. Both must be free across pickup, travel and buffers before confirmation can succeed.
A replacement pair is reserved as one atomic change. Concurrent dispatch cannot take one resource and leave the booking in a half-assigned state. If any collision occurs, Base rolls back the attempted change and preserves the last valid driver, vehicle and route snapshot.
A standard pickup, an unsuitable vehicle and a reassignment conflict show the dispatch boundaries.
The dispatcher reviews the route, arrival time, passenger count and luggage, confirms a driver with a current credential and a minibus with enough capacity, and sees both on the dispatch board. The driver records arrival, pickup and drop-off against the same booking.
A vehicle is free at the requested time but its recorded luggage limit is below the party requirement. Base refuses that allocation rather than allowing staff to override capacity casually. Dispatch offers a suitable vehicle or time, asks for corrected request details, or declines the transfer.
Staff update the reference and propose a later pickup, but the assigned driver or vehicle is already reserved then. The reallocation fails as a whole and the current assignment remains visible. The dispatcher can choose another eligible pair and record the agreed revised time manually.
The profile preserves staff decisions and passenger needs while keeping transport judgment with the operator.
The route snapshot, price lines, passenger and luggage counts, driver-vehicle assignment, flight-reference updates, arrival, no-show and drop-off keep actor and time. A failed reassignment cannot silently replace the last valid operational plan.
Drivers see assigned route, contact and approved operational requirements, not the complete customer catalogue. The operator owns privacy, credential, licensing, waiting and accessibility decisions. Base records evidence but does not guarantee live flight data, road conditions or a legal result.
Create supported routes or zones, transfer types, local durations, pickup and travel buffers, passenger and luggage rules, and transparent route or fee price lines. Add vehicles with real capacity, drivers with shifts and relevant credential expiry, reviewed transport, waiting, cancellation and privacy policies, and dispatch permissions. Test imports for unsupported routes, capacity mismatch, invalid credentials and driver or vehicle collisions. Keep manual fallback instructions for every flight reference.
The profile coordinates the operator’s own bookings without becoming an on-demand transport network.
Base is not a ride-hailing marketplace, live route optimiser, GPS tracker, live flight automation, fare meter or driver-payout system. It does not decide operator licensing or traffic conditions. Online customer payment is not included; the passenger pays the transport business outside Base.
Base does not find independent drivers, rank them, optimise live routes, track GPS or automatically change bookings from a flight feed. The dispatcher reviews route, time and updates, then records the operational decision.
Route, zone, waiting, selected extra and mandatory fee lines can be snapshotted. Base does not calculate a live fare meter, settle driver earnings or take passenger payments. External money remains with the operator.
An unsupported route, party that exceeds vehicle limits, expired required credential, off-shift driver or resource collision prevents confirmation or reassignment. The failed transaction leaves the last valid booking unchanged for staff to resolve or decline.
A booking is not only a time — it is a person, a room and a machine, all of which can be busy. Booking the time and discovering the rest afterwards is how a day falls apart.
ExploreThe same person books four times and is typed in four times, each time slightly differently, and by the fourth nobody can tell whether they owe money.
ExploreConfirmations are sent by hand until the day nobody does, and the customer arrives for a booking that was cancelled.
Explore
Manage sunbeds, umbrellas, boards and beach stock by period with clear issue and return records. See the workflow and setup.
Protect bicycle and e-bike stock by size, category and period without overselling the last unit. See the workflow and setup.
Reserve named vessels and required crew as one rental with handover, safety notes and return evidence. See the workflow and setup.
Yes. The airport transfer booking system gives you a booking page in English, Greek and Russian where passengers request a route and pickup time; staff then confirm a suitable driver and vehicle together. As chauffeur booking software or taxi booking software for pre-booked trips, Base takes no commission and no card payments, and sends notifications by email or Telegram.
Yes. Both exact resources are checked and reserved in one transaction with route, passenger, luggage, credential and buffer constraints. A conflict prevents partial assignment.
It can compare the recorded request with configured vehicle capacity and approved requirements. Staff remain responsible for accurate data and transport decisions.
Staff record the updated reference or time and recheck allocation. Base does not move the booking automatically; a conflict preserves the current assignment for manual resolution.
No. There is no live route optimisation, GPS tracking or automatic flight-feed dependency. The dispatch board uses the operator’s recorded schedule and decisions.
No. Passenger money stays outside Base. The booking can retain accepted price lines and factual external receipt or refund records only.
Next step
Registration takes an email address. The operating model, services and resources are configured afterwards, in the console.