3 ms·

I might be a bit slow on this one, but I don't see the problem with even a strictly enforced requirement for ride acceptance given that the driver's app is "on"

by swyman 11y ago

I might be a bit slow on this one, but I don't see the problem with even a strictly enforced requirement for ride acceptance given that the driver's app is "on". Uber's business is in efficiently matching available drivers with riders, and adjusting the market price based upon the relative supplies. Drivers with the app "on" but not actually accepting rides messes with their price offering on both sides of the equation. At the margin, riders pay less in surge with an artificially inflated supply of rides, and the drivers on the other side receive less in surge pricing. Is there something I'm missing here?

prostoalex 11y ago
The drivers seem to object to a few scenarios: 1) Low-rated passengers. 2) Requests that require significant travel for pickups that are likely to result in short rides (pickup request comes from a downtown bar with next destination likely to be another downtown bar, the driver himself is not very close to downtown). Happens under low driver supply. https://www.reddit.com/r/uberdrivers/comments/2mykji/my_reply_to_ubers_low_acceptance_rate_email/ https://www.reddit.com/r/uberdrivers/comments/2mykji/my_repl... 3) Requests happening while the driver is "chasing the surge" and heading towards high-surge area while driving in non-surge vicinity and receiving a non-surge request just by being nearby. This thread has more links towards the nature of concerns http://uberpeople.net/threads/ride-skipping-deactivation.36582/ http://uberpeople.net/threads/ride-skipping-deactivation.365...