Bookings and the life of a job

The life of a job

A client's request arrives as To confirm. You confirm it, put a driver on it (To assign → assigned), the driver runs it — en route, arrived, picked up, dropped off — and it completes. The client can cancel until the trip is underway, always with a reason you'll see; you can cancel from your side at any stage.

Confirming

Confirmation is one tap on the trip — and several things you'd naturally do confirm it for you: pricing an unpriced request, assigning a driver, or taking any payment each confirms a pending booking in the same gesture. Bookings you create on a client's behalf skip the queue and start confirmed.

The rules you control

You decide what can be booked: minimum notice (out of the box, 2 hours — set it to what your operation needs), which services you offer (transfers, hourly, delivery), which vehicle classes serve which services, and your own booking restrictions with messages in your words. Clients who don't clear a rule see your message at booking time — they never get a silent failure. When you book on a client's behalf, your restrictions defer to you.

Changes and cancellations

Clients don't edit a booked trip directly — they send a change request (new time, address, vehicle class) that you approve or decline; approving applies the change automatically and the trip thread records it. Cancelling is available to the client up until the trip is underway, always with a reason attached.

"Ride now" requests

On-demand requests work on a promise clock: the client asks for a car now, you (and every admin) get pinged instantly, and you dispatch from a live view of your drivers. The mechanics live in Assigning drivers.