Ditto to all that DwarfLord said!

I'm wasting (no exaggeration) hours per day mindlessly responding to new URs to ask for the destination, since Waze won't provide it from the anonymous... yes, anonymous reporter. Then I'm reminding some of them, if I have time, at the 4-day point. Then I'm closing about 85% of the reports that got no response at the 8-day point, without improving the map nor fixing the reported issue. I'm typically juggling 250 - 350 open URs at any point in time.

Every single thing DwarfLord said is true and would help. Thanks Dev Team for looking into improving the situation.

This would be hugely beneficial, and help more of the donated hours from our editors go toward more impactful things than sending off nearly-automatic messages that nearly never cause a reply from the submitter. Configurable by country and perhaps state/region/etc. would be needed probably, but this could help a lot.

I'm upvoting this for sure. This has been a huge problem for years and can lead to editor burnout. But, besides auto-closing URs with no reporter response, there are SO MANY other things Waze can do to help editors waste less time with URs: (1) At reporting time, ask reporter if OK to send origin and destination data; (2) Automated reminder to the reporter to add a description to the UR if one was not originally provided; (3) source control/throttling - reporters with a history of not engaging on URs are not allowed to report as many; (4) MUCH clearer message notifications and inbox navigation in the Waze app; (5) redundantly offer "road closed" as an option under "map issue", as MANY reporters use "map issue" to report temporary closures instead of the "closure" feature.

This feature would save us a ton of time as we'd only need to do a third of the tasks we now have to do for URs. It would allow us to focus on the URs where we actually get a response instead of having to maintain the ones that go unanswered. The time can probably best be made configurable by country as in Belgium we generally follow the "3 days until reminder, 3 more days until closure" rule and that is going to be different for each country.

Waze's UR handling system is so inefficient that it risks alienating editors who want the energy they put into Waze to make a bigger difference. However it is also so complex, and in many ways independent of other aspects of WME, that I think Waze should make a dedicated suggestion box or subfolder specifically for UR handling. If folks like that idea please upvote my suggestion to that effect at https://waze.uservoice.com/forums/59225-map-editor-suggestions/suggestions/42096814-new-suggestion-subcategories-1-ur-handling-and

I think this idea is great. It also stops you relying on the same editor interacting with the open UR's when they may be having a break from Waze (I know, I know, who would do that) as it is confronting when you see so many open. It would also help when another editor looks at them and doesn't want to "stand on someone's toes" if the original comment is there by someone but is waiting to be followed up on.
Looking at many of the NSW ones, some have been open some time and people may even forget what they were reporting in the first place even if they do see the comment on them.

Most editor questions on URs are not responded to by the reporter, most likely because the response is not drawn to the attention of the reporter sufficiently. As a reporter, I've only ever seen editor responses because I'm looking for them.

But I would suggest more than 7 days. I currently mark as Not Identified 30 days after my last response.

And L2 or L3 minimum seems ok.

Agree 100%

I'd also possibly suggest that a user needs at least 50 UR closures before the option to toggle on appears, to ensure they have experience investigation and managing URs.