RideBits / Help ridebits.app ↗
Help Assigning drivers
Browse topics
03

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. Each driver has a default style you set — fleet drivers default to direct assignment, independent drivers default to offers — but you choose per trip, every time.

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.

"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.

Didn't find your answer? Message us from the chat bubble in the corner of this page — we read everything.