Let editors tell app users why Places or Place updates were rejected
Editors must sometimes reject Places and Place updates submitted from the app. But WME provides no means to communicate WHY. This is discouraging for both editors and submitters.
WME should allow editors to select from a list of the most common reasons for rejecting Places or Place Updates in order to inform app users how to improve their Place suggestions. An example list:
- Photos must provide clear exterior orientation for drivers
- Descriptions must meet Waze community guidelines
- Could not verify deletion, renaming, or other significant change
- Non-residential Places must be meaningful to the general public
- Gas prices cannot be moderated, they can only be entered via the app
DwarfLord
shared this idea
-
DwarfLord
commented
Staff permanently closed this suggestion as "Not Right Now" without comment on May 19, 2024. Not sure what that means. A Champ has informed me that Waze's recommended solution is now to provide feedback by engaging submitters in open-ended, free-form text conversations using the new chat feature. If so, I'm not sure why Waze didn't simply say so here and close this suggestion as "Now Available" if they believe the underlying concern has been addressed. Anyway, apparently, that's the end of that.
-
armand commented
photos should not include peoples faces for privacy
-
fmis13 commented
Hi, since 2021 (last Staff comment) I haven’t seen a update to this (nor implementation). When can we expect a implementation of this?
Best regards -
TheMet4lGod
commented
If they implement this, it needs to be standardized. I don't want to have to type out the reasons every time I have to reject something.
-
wxw777 commented
Yes, great suggestion (had meant to make it myself!). I believe this would greatly enhance user satisfaction when they see their PUR rejected.
Might require a free text option as local community standards vary.