We have experienced first-hand the down-side of addressing this issue by making toll penalties cumulative: Eventually, the penalty builds up to the point where it is "better" to violate a turn restriction or directionality.
IMO, if you're already on a toll road when you start to navigate, and you have "avoid tolls" set, Waze can leave it to the driver to find a legal way off the toll system. Scenario: user has "avoid tolls" set, but on a particular trip selects an alternate route that includes a toll road. While on the toll road, Waze recalculates for whatever reason. Does the driver want Waze to keep trying to route him off of a toll road that he voluntarily entered?
This is another case where Waze should assume a certain amount of competence on the part of the driver. Exits on toll roads are usually clearly marked.
IMO, if you're already on a toll road when you start to navigate, and you have "avoid tolls" set, Waze can leave it to the driver to find a legal way off the toll system. Scenario: user has "avoid tolls" set, but on a particular trip selects an alternate route that includes a toll road. While on the toll road, Waze recalculates for whatever reason. Does the driver want Waze to keep trying to route him off of a toll road that he voluntarily entered?
This is another case where Waze should assume a certain amount of competence on the part of the driver. Exits on toll roads are usually clearly marked.
Re: Toll roads option in the client