Uber Drivers Forum banner
1 - 20 of 23 Posts

· Registered
Joined
·
110 Posts
Discussion Starter · #1 ·
Caught a rematch at LAX; accepted the ride, went to Terminal B to pick-up (base fare); loaded her luggage, clicked start the trip and seen the destination was Bakersfield.

I immediately thought: "I am not taking that ride." So, I called Uber support, explained she is going to Bakersfield, I can't accept the ride, and I didn't get any notification (45 plus or 60 plus) or else I wouldn't have accepted.

After saying she couldn't cancel on her app (she was was playing stupid for a few mins), she finally cancelled.

Question: can I get into trouble for this? A base ride to Bakersfield is not worth it.
 

· Premium Member
Joined
·
6,924 Posts
No you are not getting deactivated for this. If you do it a lot at lax you could lose your lax "privileges" and also get deactivated, but it happens from time to time. I suggest ALWAYS making sure the pax gets refunded if you get a cancellation fee.

I did the exact same thing, not at lax though. Started the ride and it was to Bakersfield. Told the pax I couldn't do a ride like that. There is no way you are getting anything coming back. Soonest would be Valencia, and that is a total crap shoot.
 

· Premium Member
Joined
·
6,924 Posts
The key factor in this case SHE canceled, not YOU
Not necessarily, because one of the reasons for a cancellation by pax is "did the driver ask you to cancel". But like I said, if it happens a couple of times, no worries, make a habit of it, and all bets are off.



There is a term for it, called"quick Cancelling", where the driver starts the ride to see where the pax is going, when the driver sees its a destination he doesn't want to go to, or its a short ride, he then cancels the ride. So obviously, uber doesn't want this happening, even though we should get a destination when we accept the ride if we really are independent contractors, but lyft can and will deactivate you for habitually doing this... like 10times a day.
 

· Super Moderator
Joined
·
7,632 Posts
I did the same thing once, except it was LAX to San Diego. Actually took 12 minutes and leaving the airport to figure out how to cancel it. (I was new). Told support what happened, that I'd been driving for almost 12 hours and it was too dangerous for me to be on the road that long. Told them not to charge pax too. Ended up getting paid for my side of the 12 minutes and a couple miles, customer wasn't charged, and never heard a negative word about it! Pax wasn't happy, but better that than to be driving 4 more hours dead tired.
 

· Registered
Joined
·
28 Posts
I always ask where they are going before starting the ride, if it is to a destination where I don’t want to go I let them know I’m not heading that way and then I cancel so they can call someone else. Some get mad and some understand, I used to take them anywhere but now U/L is a numbers game and There is money to be made but need to play the game right. U/L playing this game right and screwing us so hoping everyone is doing the same.
 

· Premium Member
Joined
·
6,924 Posts
I always ask where they are going before starting the ride, if it is to a destination where I don't want to go I let them know I'm not heading that way and then I cancel so they can call someone else. Some get mad and some understand, I used to take them anywhere but now U/L is a numbers game and There is money to be made but need to play the game right. U/L playing this game right and screwing us so hoping everyone is doing the same.
Its uber and lyft's won fault drivers are forced to do this.
 

· Banned
Joined
·
3,535 Posts
Caught a rematch at LAX; accepted the ride, went to Terminal B to pick-up (base fare); loaded her luggage, clicked start the trip and seen the destination was Bakersfield.

I immediately thought: "I am not taking that ride." So, I called Uber support, explained she is going to Bakersfield, I can't accept the ride, and I didn't get any notification (45 plus or 60 plus) or else I wouldn't have accepted.

After saying she couldn't cancel on her app (she was was playing stupid for a few mins), she finally cancelled.

Question: can I get into trouble for this? A base ride to Bakersfield is not worth it.
They can't legally require you to accept such a lengthy trip without notifying you. They also can't force you to work at a loss, which is what this trip would be. If they used this as an excuse to harm you financially you could sure them for sure.
 

· Premium Member
Joined
·
6,924 Posts
They can't legally require you to accept such a lengthy trip without notifying you. They also can't force you to work at a loss, which is what this trip would be. If they used this as an excuse to harm you financially you could sure them for sure.
Talk to me about this "they can't force you to work at a loss"? I'm serious. Because any short ride is a financial loss. Spend 5-10 minutes picking pax up. Wait 5 minutes, without tires turning. Drive another 5-7 minutes for minimum fare of what $2.75 (don't know what the minimum is right now as I haven't done one since new earnings structure). But I guarantee you, we spend more than $2.75 for this ride.

If this is indeed true, this is argument for an increased minimum and destination notification on ping request.
 

· Premium Member
Joined
·
2,934 Posts
Cancelling a ride because of the destination could be cause for deactivation.
In the case of long trips like Bakersfield , Vegas, or San Diego hopefully U/L would take that into account.
I would use the fatigued driver/safety excuse if possible.
 
  • Like
Reactions: gunigham1

· Banned
Joined
·
3,535 Posts
Talk to me about this "they can't force you to work at a loss"? I'm serious. Because any short ride is a financial loss. Spend 5-10 minutes picking pax up. Wait 5 minutes, without tires turning. Drive another 5-7 minutes for minimum fare of what $2.75 (don't know what the minimum is right now as I haven't done one since new earnings structure). But I guarantee you, we spend more than $2.75 for this ride.

If this is indeed true, this is argument for an increased minimum and destination notification on ping request.
Collect the evidence. Do the math and make sure it sticks.

Everything about Uber is a fraud. Read every letter of your contract and compare it to the Borello Test. There are a lot of studies on how much drivers have to be paid to be able to provide a safe, quality service. NYC sets that floor at $1.75. Obviously Uber pays well below this.

This company is over. The stock performance is gonna be a train wreck. Now that everyone is getting to see the internals people will realize all the negative things said about the company are true and then some. For a company to pay so unbelievably poorly yet still lose so much money proves what a joke of a company and business model they are.

Cancelling a ride because of the destination could be cause for deactivation.
In the case of long trips like Bakersfield , Vegas, or San Diego hopefully U/L would take that into account.
I would use the fatigued driver/safety excuse if possible.
I use the "this ride will lose me money and you can't force me to do that" argument. Because it's true.

Uber knows that withholding destination information is illegal in the context of an independent contractor relationship.

Look up "contract of adhesion" and you'll quickly realize that's what we're under with Uber, which is not an IC agreement.
 

· Premium Member
Joined
·
6,924 Posts
Collect the evidence. Do the math and make sure it sticks.

Everything about Uber is a fraud. Read every letter of your contract and compare it to the Borello Test. There are a lot of studies on how much drivers have to be paid to be able to provide a safe, quality service. NYC sets that floor at $1.75. Obviously Uber pays well below this.

This company is over. The stock performance is gonna be a train wreck. Now that everyone is getting to see the internals people will realize all the negative things said about the company are true and then some. For a company to pay so unbelievably poorly yet still lose so much money proves what a joke of a company and business model they are.


I use the "this ride will lose me money and you can't force me to do that" argument. Because it's true.

Uber knows that withholding destination information is illegal in the context of an independent contractor relationship.

Look up "contract of adhesion" and you'll quickly realize that's what we're under with Uber, which is not an IC agreement.
So the lawsuit should have never been about making us employees, it should be about giving us the rights of an independent contractor. Show us the damn destination in the ride request? Has THIS been litigated?
 
1 - 20 of 23 Posts
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Top