The acceptance mechanic — where a contractor sees your booking request and decides whether to accept it — is the core structural problem of the app model. A booking that can be declined is not a confirmed booking. It is a pending request wearing confirmation's clothes.
Here is how it works on most platforms: you complete a booking, receive a confirmation notification, and a request is simultaneously broadcast to nearby contractors. If they decline — because they are close to the end of a shift, because the destination is inconvenient, because they decided not to — the platform tries another. If enough decline, you get a cancellation notification and start again.
The platform calls this a confirmed booking. It is not. It is a conditional offer that requires contractor acceptance to become real. The confirmation you received was the system's optimism, not a guarantee.
This matters because the point of booking in advance is to remove the variable. You book 24 hours ahead because you have a flight, a meeting, a fixed obligation. The acceptance mechanic reintroduces the variable at the worst point — not when you are browsing, but when you are committed.
At chauffeur.co.nz, there is no acceptance step. When you confirm a booking, a chauffeur is assigned. Not offered to a pool — assigned. The booking is confirmed because the employment relationship makes it confirmed: the chauffeur is on our payroll and is going to your pickup.
This is not a technical feature. It is a consequence of employment. A contractor chooses jobs. An employee does the job.
Why do apps use the acceptance mechanic?
Because the app-platform model is built on independent contractors who are not obliged to work any particular shift or accept any particular job. The platform cannot compel acceptance because it has no employment relationship. The acceptance mechanic is the inevitable result of the gig model — it is not a design flaw, it is the design. The flaw is calling the result a 'confirmed booking'.
What happens if a contractor cancels after accepting?
On most platforms, the booking re-enters the acceptance queue. Your departure time has now moved. On a busy morning — airport peak, weather event, public holiday — the queue may be long. The platform's cancellation rate statistics, if they publish them, describe this problem in aggregate. You are experiencing it individually, with a flight to catch.
How does chauffeur.co.nz handle this?
There is no acceptance queue because there are no contractors. Every chauffeur employed by us is on our payroll. When you confirm a booking — airport transfer, point-to-point, hourly, or the day — a specific person is assigned to it. The assignment is not contingent on their choice. It is the employment arrangement. Book via the booking page and your chauffeur is confirmed at the point you confirm.
Since 2002 — fixed prices — the vehicle you book is the vehicle that arrives — drivers employed by us.