BeNeLux Wiki in English, translation into other languages is started...
The global Wiki page on Update Requests contains an extensive description of all aspects of the User Request. This page describes the BeNeLux approach.
The conversation start with your first response, often asking for information. When the reporter doesn't react a friendly reminder should be send. After two reminders the UR can be closed with Mark as not identified. In case the reporter replies on your response the problem might be solved. Perhaps an explanation is sufficient, sometimes the map should be corrected. If the problem is fixed the UR can be closed with Mark as closed.
- Thank user for reporting the issue.
- Give streetname/area so the reporter knows about the location (could make a difference in case of multiple reports on that day by this reporter).
- If your reply is not on the date of the UR itself give an indication of the day and time.
- Ask for more information necessary to solve this UR.
- Indicate that they cannot answer directly by email because of the email@example.com address used. You could include an email address of your own allowing the reporter to answer by email replacing the firstname.lastname@example.org address with yours.
- Sign off with your name.
- First reply > First reminder after 5 days > Optional second reminder 4 days later > Mark as Not identified 2 days later.
- React on reporter's answers untill a conclusion is reached > Mark as Solved 2 days later to give the reporter the opportunity to give a last reaction.
When you respond to user reports, you are interacting with the original reporter, and you may also be interacting with other Waze editors who respond to the same request. The first responding editor has no absolute ownership of the problem resolution. Other editors should not step in, other than to send a next reminder to the reporter, or unless they think the owner needs help (whether the owner realizes it or not), or the first reporting editor has abandoned/lost track of the report over time.
- Always react friendly, helpful.
- Don't use jargon
- Keep your reactions short and to the point.
Example Turn not allowed
Looking at the green line (=GPS track driven by user in reality), a turn was made at the end of the road where the purple line (Waze route) starts.
If there are no obvious reason’s to be found (like red Turn Restrictions, or unconnected roads) you will have to investigate further and probably need the help of the user. In this case the reason is unclear so we will try to get in contact with the reporter using the Conversation Box asking for more information.
This is a NO-REPLY email. Please use the app or email below. Thanks for your report on the Noorddijk, Rockanje! Waze did not send us enough information to fix your request. Would you please let us know what went wrong? Your route indicates that you had to turn around. What was your destination? Best regards, <name> (username <wazeusername>, email email@example.com )
Depending on a response (and information given) it could mean that several messages goes back and forth until reason (and solution) is clear.
Example Address unknown
The report indicates “Incorrect address”: Wolwevershaven 19 Dordrecht.
The report is made on the junction Vlak and Nieuwe Haven. The Wolwevershaven is northwest of the water. Bij Checking the address, house number is halfway the quay, approximately 200 meter further.
After checking the address on the Waze map and in the land register (BAG) the location of the house number in Waze proves to be right. So the report proves to be incorrect.
This is a NO-REPLY email. Please use the app or email below. Thanks for your report on the junction Nieuwe Haven, Roobrug and Vlak in Dordrecht! You wrote "Wolwevershaven 19 bevindt zich op deze locatie ", but your report is made on before address Vlak 11. The address you mentioned is about 200 meter further. Would you please let us know why you thought the address was incorrect? What was your destination? Best regards, <name> (username <waze username>, email firstname.lastname@example.org )