MysticCobra wrote:Yes, as you said waze SHOULD provide an alternative but it doesn't do this consistently. Often, I will click the Routes button and still only get 1 option. That's what I want to address... the "WHY?"

Waze does seem to make some unnecessary assumptions when it provides alternative routes that causes it not provide available options. For example, if I ask for a route from Georgetown Pike to Van Dorn Rd with my default settings, waze gives the two routes on the Beltway (one via the express lanes and one via the regular lanes). But waze only gives those two choices.

2options.jpg (22.41 KiB) Viewed 701 times

If I then change my settings to "Avoid major highways" and try again, waze has no problem finding three additional options (albeit with much later ETAs).

Waze on occasion will only suggest one route. I don't think it should matter if it is a toll route or not, I feel like waze should ALWAYS suggest an alternative (whether the primary route is a toll or not). Even if route A is 14 minutes to destination and route B is 28 minutes. I still want a CHOICE!

Why doesn't waze suggest more alternatives? How do we submit a bug fix/request to get more alternate routes EXPECIALLY when 1 route is a TOLL route?

Yes, as you said waze SHOULD provide an alternative but it doesn't do this consistently. Often, I will click the Routes button and still only get 1 option. That's what I want to address... the "WHY?"

And as for that specific UR, yes I was speculating. There were several URs on the beltway where I couldn't determine exactly what the problem was with the info given but my best guess is that waze had directed the user onto the Toll lanes and the user was actually driving on the regular lanes. Thus, waze gave "wrong directions" to get off. There's really no fix for that. This leads back to my previous suggestion to have waze suggest a toll and no toll route. But the user could still have pushed the wrong button or ignored the route, or something else.