TxAgBQ
My feedback
50 results found
-
198 votes
Great timing! We’re currently working on having the history of closures. Keep an eye out for updates on the WME.
TxAgBQ
supported this idea
·
An error occurred while saving the comment -
1,671 votesTxAgBQ
supported this idea
·
-
325 votes
Hi all,
Thank you for voting for this suggestion!
We’d like to know if this is still relevant, or if the issue was solved through auto-complete for prioritized Waze addresses.
Please let us know in the comments if it was, so we can close the suggestion.
Thanks!
-StaffAn error occurred while saving the comment TxAgBQ
commented
To restate my reply:
You said: We’d like to know if this is still relevant, or if the issue was solved through auto-complete for prioritized Waze addresses.
Yes, it's still relevant.
Waze results are NOT prioritized in autocomplete. Let me know if you need specific examples.
TxAgBQ
supported this idea
·
An error occurred while saving the comment TxAgBQ
commented
Yes, it's still relevant. Waze is supposed to put RPPs at the top (according to the hierarchy) but it does not. Sometimes they aren't even visible at all, without very specific searches beyond the auto-complete.
Wazers start typing and choose an address and if they pick the GMaps address, it might be junk. I've had a few update requests lately for incorrect address where GMaps had duplicates and the only way to fix the issue was to call my GMaps buddy and have him fix it. The RPP never showed up (and still doesn't) in the search priority... just GMaps. Another workaround is to add a PP to the residence then link externally. What we're asking for here is to be able to link externally to the RPP, so we don't have to game the Waze system to make up for 1) search shortcomings and 2) Gmaps errors. Thank you
-
3 votesTxAgBQ
shared this idea
·
-
3 votesTxAgBQ
shared this idea
·
-
8 votesTxAgBQ
supported this idea
·
-
16 votesTxAgBQ
supported this idea
·
An error occurred while saving the comment TxAgBQ
commented
Simply reordering the buttons will help. Closure needs to be MUCH higher on the list.
Row 1) Traffic, Police, Crash and Hazard are all things Wazers report that are immediately fed to other Wazers.
Row 2) Gas prices, Map Chat, Map Issue and Place --- reorder to Closure, then Map Issue, then Place. Does anyone actually use Map Chat? Why is it higher priority than closure, which is at the very bottom?
Row 3) Whatever is left.
-
14 votes
An error occurred while saving the comment TxAgBQ
commented
Another option is for Waze to very clearly state, in the email, not to reply to the email. Because Waze doesn't do this, I do this as an editor, but it just makes my request for info, such as destination, even longer and less likely to be read.
-
262 votes
Hey jangliss,
Thank you very much for this detailed suggestion.
Currently there is a lot of work around communication between the WME and the client (the app), to find how best should be handled.We will do our best to share some more details about it in the near future.
At this point this is currently not planned, and therefore won’t move to our back log.
If any thing in this direction will be changed, we will update accordingly.
Best,
HeziAn error occurred while saving the comment TxAgBQ
commented
I would like to see email reply BUT as it it not being planned, at a minimum the email that goes to Wazers needs to clearly tell them to NOT reply to the email.
- Since there is nothing saying not to reply by email, Wazers do and those emails do not get rejected at all... they just disappear into a black hole.
- Since Waze doesn't tell Wazers not to reply, editors end up doing it. It just makes our responses, where we have to ask for info such as destination, longer and less likely to be read and responded to. -
8 votes
Thanks for your feedback. At this time, this doesn't fit on our roadmap, but we'll keep it in mind for future product planning.
TxAgBQ
supported this idea
·
I don't believe in-app closures show in history. I often get URs for map issues reporting closures (because the Closure function wasn't obvious to the Wazer) and while I'm researching/following up for more info I later find a closure that appeared in the Discord closure feed for that segment. But I don't see that closure in the segment history.
If I could see if in history and I saw multiple in-app closures recently, I'd know Wazers saw it and closed it, leading to more confidence in closing it from within WME.