Assigning drivers

Scheduled trips: assign or offer

Open a trip and you'll see your drivers grouped for that time slot — free, possible conflict, or off. Then it's one of two gestures: Assign puts the driver on the trip immediately; Offer sends it to them to accept or decline, with a push and a card in your chat with them. Both are always there, and you choose per trip, every time. (Older versions of the RideBits app still show a Fleet or Independent style on each driver; it only highlights one of the two buttons and changes nothing else.)

If a driver declines, the trip returns to unassigned and you're notified. Reassigning is safe at any point: the previous driver comes off the trip and its conversation, the new one comes on. When you confirm, you can put the car on the trip too — one of your vehicles, or a new one you add right there (colour, make, model, plate — the plate, or the make and model, at least), which is saved to your vehicles; a plate you already have is that car, and you're told so. It's optional; your client sees the car so they can find it at the curb.

No driver yet? Add one from the trip

Under your drivers — or in their place, if you have none — the trip offers the people who can take it now. Assign to myself puts you on it, adding you as a driver if you aren't one (with your phone confirmed first — clients call their driver). An admin can make a teammate a driver and assign them, if their phone is confirmed. And Invite a driver starts the usual invite — by phone or email — with the trip remembered. When they join and the trip still needs a driver, it's sent to them as an offer to accept, in the name of whoever invited them — and your office is told. If its pickup time has passed by then, or whoever invited them is no longer in your office, you're asked to assign them instead; if someone took the trip in the meantime, it stays as it is. (Your company link doesn't carry the trip.) Staff can do all of this except making someone else a driver.

"Ride now": on-demand dispatch

An on-demand request pings every admin instantly, with a countdown — the client is promised an answer within a window you configure (5 minutes out of the box). You dispatch from a live roster: who's on duty, who's mid-trip, and where they are. Assign starts the trip on the spot — the client is confirmed and the driver is en route in one move. Or offer it to one driver at a time, each with a short decision window; a decline or timeout hands it back to you with the clock still honest. If nobody can take it, you decline with a reason and the client knows immediately.

On duty

Drivers flag themselves on or off duty in the app — that's what feeds the on-demand roster: on-duty drivers with a live location show as available, off-duty drivers are set aside (though the dispatch decision is always yours). Scheduled offers reach everyone regardless of duty.

Running solo

On the Solo plan there's no assignment step at all: one Accept confirms the trip and puts you on it in a single tap — for scheduled and "ride now" alike. Assigning anyone else is a Fleet feature.