[bboy]

The last couple times i've been out, starting with a week ago Saturday
I've been getting a LOT more Next Trip requests on Uber, where it puts you on the next pick up while finishing your current drop off.

I was curious if others have had similar experiences recently?

It was especially interesting, as I was driving Friday night, and gotten almost none of these requests but never-the-less was steady between Uber & Lyft. (No real surge of course...)

Then I drove Saturday night (last week) and started around 10pm. From my first trip, I was Always ON a ride and/or picking up my next PAX. It was remarkable... In one case as soon as I hit START trip as the PAX entered the car my next request was already waiting! (it was a short ride). For other cases, as i got within 5-8 minutes of the drop off, I was getting another request. This happened no less than 10 times in a row. Surge was non-existent or at best very modest. In fact I let one pass request pass (no surge) and another came (all while in trip) and the second was a modest 1.3x surge. For it to be THAT busy and NO surge in Mpls was disappointing.

I'm suspicious, as the pickups weren't extremely close to the drop, rather typically within 6-10 minutes. I'm thinking Uber tweaked the algorithm to keep drivers from getting onto the Lyft platform. It was effective, though as the surge was never great, the money I made wasn't to great even though I was busy for 4-5 hours straight...

thoughts?

 

[Goober]

Next trip kills surge lol

 

[rideshareMN]

I agree that if you are stacked constantly it would be nice if they were surge fares

 

[PTUber]

It can and has happened. I think I once had like 6 or 7 in a row all surges. Mostly shorter trips in the surge area but still nice.

 

[Spike00]

i agree with the OP, the new algorithm has us going way greater distances with stacked trips. It has been a thing for about a month or so. I think it's to minimize surge and too keep us off the Lyft platform. Last Saturday I was consistently busy with stacked trips, put in a way longer night then usual, and feel like I didn't do well $$$. Once the trips get stacked you can't check your earnings. I figured as busy as I was, I should easily be around $25/30 an hour....I started using the stop request feature when it gets like that

 

[JediDriver]

One weird thing happened to me the other night at bar close. I picked up a bunch of Spanish speaking girls. They either didn't hear me or understand when I asked them if there were any other stops. Well, as we came close to the destination, then they did say all four girls needed to be dropped at different spots just as a stacked request came in, so I had not had time to turn off incoming requests. Well, I obviously let it time out, but since it was bar close a new request came in immediately, then again and again. I think 5 or 6 in a row. It was a pain in the ass because I was trying to navigate and communicate with the girls, but it essentially rendered my phone useless for a while. This ever happen to anyone else?

The good news is that I realized that it would not time me out like it would have had I ignored that many requests while not on a ride. I have generally been ignoring stacked requests unless they are XL or a good surge. I don't want to accept a stacked X trip only to find out I have to either drive 12 minutes to get it or take a cancel on my record. I'll save my cancels for the 5 minute money makers.

 

[rebounder]

The last couple times i've been out, starting with a week ago Saturday
I've been getting a LOT more Next Trip requests on Uber, where it puts you on the next pick up while finishing your current drop off.

I was curious if others have had similar experiences recently?

It was especially interesting, as I was driving Friday night, and gotten almost none of these requests but never-the-less was steady between Uber & Lyft. (No real surge of course...)

Then I drove Saturday night (last week) and started around 10pm. From my first trip, I was Always ON a ride and/or picking up my next PAX. It was remarkable... In one case as soon as I hit START trip as the PAX entered the car my next request was already waiting! (it was a short ride). For other cases, as i got within 5-8 minutes of the drop off, I was getting another request. This happened no less than 10 times in a row. Surge was non-existent or at best very modest. In fact I let one pass request pass (no surge) and another came (all while in trip) and the second was a modest 1.3x surge. For it to be THAT busy and NO surge in Mpls was disappointing.

I'm suspicious, as the pickups weren't extremely close to the drop, rather typically within 6-10 minutes. I'm thinking Uber tweaked the algorithm to keep drivers from getting onto the Lyft platform. It was effective, though as the surge was never great, the money I made wasn't to great even though I was busy for 4-5 hours straight...

thoughts?

I've noticed this "phenomenon" too. You're right...it doesn't add up to much. The crappy part about trying to use both Uber and Lyft while driving, is sometimes Uber will hit you with ride after ride preventing you from logging back in on Lyft. What I started doing was ignoring the nexttrip request unless it was a surge, or it was an xl fare. I make a lot more money on Lyft for the same trip than I do on Uber. I just wish it was busier.

 

[Uzcaliber]

Next trip kills surge lol

You may be right. The Next Trip practically assume drivers (while still having passengers in their cars) are available thus increase the number drivers available in the area.

 

[UberDad55403]

One weird thing happened to me the other night at bar close. I picked up a bunch of Spanish speaking girls. They either didn't hear me or understand when I asked them if there were any other stops. Well, as we came close to the destination, then they did say all four girls needed to be dropped at different spots just as a stacked request came in, so I had not had time to turn off incoming requests. Well, I obviously let it time out, but since it was bar close a new request came in immediately, then again and again. I think 5 or 6 in a row. It was a pain in the ass because I was trying to navigate and communicate with the girls, but it essentially rendered my phone useless for a while. This ever happen to anyone else?

The good news is that I realized that it would not time me out like it would have had I ignored that many requests while not on a ride. I have generally been ignoring stacked requests unless they are XL or a good surge. I don't want to accept a stacked X trip only to find out I have to either drive 12 minutes to get it or take a cancel on my record. I'll save my cancels for the 5 minute money makers.

This has happened to me too. I do the same thing. It's like fishing for XLs and surges. It will work against you in the time out though. When you drop off if you ignored all of them you will get one or two more before you get kicked off instead of normal 3.

 

[Rat]

The last couple times i've been out, starting with a week ago Saturday
I've been getting a LOT more Next Trip requests on Uber, where it puts you on the next pick up while finishing your current drop off.

I was curious if others have had similar experiences recently?

It was especially interesting, as I was driving Friday night, and gotten almost none of these requests but never-the-less was steady between Uber & Lyft. (No real surge of course...)

Then I drove Saturday night (last week) and started around 10pm. From my first trip, I was Always ON a ride and/or picking up my next PAX. It was remarkable... In one case as soon as I hit START trip as the PAX entered the car my next request was already waiting! (it was a short ride). For other cases, as i got within 5-8 minutes of the drop off, I was getting another request. This happened no less than 10 times in a row. Surge was non-existent or at best very modest. In fact I let one pass request pass (no surge) and another came (all while in trip) and the second was a modest 1.3x surge. For it to be THAT busy and NO surge in Mpls was disappointing.

I'm suspicious, as the pickups weren't extremely close to the drop, rather typically within 6-10 minutes. I'm thinking Uber tweaked the algorithm to keep drivers from getting onto the Lyft platform. It was effective, though as the surge was never great, the money I made wasn't to great even though I was busy for 4-5 hours straight...

thoughts?

I often ignore next trip requests that aren't surge only to get one that is surge

 

[Curmudg]

One weird thing happened to me the other night at bar close. I picked up a bunch of Spanish speaking girls. They either didn't hear me or understand when I asked them if there were any other stops. Well, as we came close to the destination, then they did say all four girls needed to be dropped at different spots just as a stacked request came in, so I had not had time to turn off incoming requests. Well, I obviously let it time out, but since it was bar close a new request came in immediately, then again and again. I think 5 or 6 in a row. It was a pain in the ass because I was trying to navigate and communicate with the girls, but it essentially rendered my phone useless for a while. This ever happen to anyone else?

The good news is that I realized that it would not time me out like it would have had I ignored that many requests while not on a ride. I have generally been ignoring stacked requests unless they are XL or a good surge. I don't want to accept a stacked X trip only to find out I have to either drive 12 minutes to get it or take a cancel on my record. I'll save my cancels for the 5 minute money makers.

Turn on "no more trip requests" after current ride til you drop last one off.