Changes

From Wazeopedia

User:DwarfLord/UR

1,200 bytes added, 4 years ago
Likely cause identified, give reporter opportunity to clarify
Volunteer responding to your report of a road closure. Do you know how long the closure will last? If it is only for a few days or less, we volunteer map editors can't help. It takes at least that long for our edits to make it to handheld devices! The best way to report short-term road closures is with the Report->Closure feature in the Waze app (you used Report->Map Issue to file this report). However, if this is a long-term closure or time-based or vehicle-type-based restriction, please respond using the app (emails don't work with the reporting system) and let us know as much detail as you can. Cheers! (Open to any editor)
 
=== Failed route, user rants at Waze regarding road closure ===
 
Dear reporter, I'm a volunteer responding to your report. Sorry for your experience. Please note that Waze employees never see "Map Issue" reports. The reports simply appear on the volunteer editing screen. The idea is that a volunteer editor will happen to see them and will do something. Unfortunately the number of volunteers watching this area is small. Meanwhile the number of "map issue" reports has increased dramatically. Sadly, most reports are not about actual problems with the map, but they still take time to handle properly. As a result, even the volunteers we have can lose heart. With few volunteers watching and our map covered in a sea of unactionable but labor-intensive map issues, important reports can go unnoticed for a long time. All I can suggest is that you make use of the Report->Closure feature. This allows you to mark closures in real time, unlike Report->Map Issue. The good news is, Waze developers are aware of the map-issue overload problem and are planning to improve the interface so that important map issues are more likely to detected sooner. I wish I could be more help. Cheers!
=== Unexplained alternate route, surely traffic-related ===
1,097
edits