- Don't want to read so much? Jump straight to the canned responses
- 1 Before you start
- 2 Some tips
- 3 Canned responses
Before you start
Also, please see this forum post that describes the two basic styles of getting information from users, EDGE and OSHI. The canned responses below favor the EDGE method, but there is a sprinkling of OSHI thrown in. You can also find other editors posting their "goto" canned responses in the same thread, especially on pages 11-14 if sorted by date (ascending).
It may be beneficial to load these responses into a tool that allows easy cut and paste into the URs, by simply selecting them from a dropdown.
What the reporter sees may not be what you expect
One final note before the canned responses. When you, the editor, receive an e-mail notification of a response to your report (whether you are the reporter or a responding editor), you will get a much different experience than when you get a notification in the Waze app. The app shows all responses together, with newest on top (the opposite of how they appear in the editor). However, you currently do not see the original text associated with the report when it was made, nor the location of the report, nor a link to it in the editor. When you get the notification in e-mail, you see the text of the response that generated the notification, the original text of the UR, the date it was originally reported, and a link to the the editor that will display the UR. If available, you will also see the name of the approximate location of the UR (street and/or city).
Because many drivers do not give Waze their e-mail address or permission to contact them, drivers typically only see the app version of the notification. Due to the way the app works, they may never even look at it -- many users aren't aware that they may get a response, and will dismiss the notification on their phone, and never look at the messages feature in the app. That is one source of the lack of responses to URs.
In addition, since they don't have context (no link, no image of he location, no description of the location, no text, no date), they may have trouble remembering what you are talking about if you don't prompt them -- increasing irritability, and decreasing the chance of any response or a useful response.
When you really just have very little to go on:
Hi, volunteer map editor here to solve your problem. What happened?
Turn not allowed
Longer and shorter versions for this. The first one (longer) is mre OSHI, and the second is fairly EDGE-y.
Hi, volunteer map editor here to solve the turn problem you reported. Which turn is not allowed? Please provide: From/to; starting direction (N,S,E,W); and ending direction. Thanks for the detailed info, so we can set this straight.
Hi, volunteer map editor here to solve the turn problem you reported. Which turn is not allowed - intersection and which turn in the intersection, please?
Driving directions incorrect - long version only, sometimes use the short generic version above
Hi, volunteer map editor here to solve your problem. What happened? Please include your origin, destination, and how Waze routed your wrong... it will help me figure out what's going on so I can try fixing it. Thanks!
Google pin issues:
Hi, volunteer map editor here to solve your problem. Waze got the address location from Google's database, and Google marked this address toward the back, which unfortunately also makes it as far from this street as it is from the cross street. I've asked Google to correct, but their responsiveness and approval are unpredictable.
No response - warning
The first one below is for my own, second if I see a fairly stale case from another editor - actual closure doesn't take place for at least 4 days, one day text is just to get them moving
Hi, again! I'm still willing to help if you're interested, otherwise, can we close this case? Let me know your intentions in the next day or so, please.
Hello, again, driver! Map editors are still willing to help if you're interested, otherwise, can we close this case? Let us know your intentions in the next day or so, please.
I submitted the changes needed to fix this problem. They should be applied in a day or two. If you like, please check them out at that point, and report back. You've made Waze better!