User:Voludu2/UR View history

No edit summary
 
(31 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{User:Voludu2/Voludu2 favorites}}
:''This is a collection of boilerplate responses for most typically encountered UR issues.''
:''This is a collection of boilerplate responses for most typically encountered UR issues.''
: Many thanks to DwarfLord, from whom I copied most of this text. I only changed the wording to sound more like me.
: Many thanks to DwarfLord, [[User:DwarfLord/UR|from whom I copied most of this text]]. I only changed the wording to sound more like me.
== Wrapper==
==Odds and Ends==
=== Wrapper===
Hi!  I'm a wazer like you working on your report.
Hi!  I'm a wazer like you working on your report.
Please respond using the Waze app;  emails don't work with the reporting system.   
Please respond using the Waze app;  emails don't work with the reporting system.   


Thank you for your report.
Thank you for your report.<br />
(Open to any editor)
(Any editor -- please follow up)
 
===Contact Support===
If you wish to contact the Waze team, please follow the instructions at http://wiki.waze.com/wiki/FAQ#How_do_I_get_support_for_my_Waze_question.3F
 
===Suggest Improvements===
please post on the waze forum at https://www.waze.com/forum/viewforum.php?f=3 or follow the support instructions at https://wiki.waze.com/wiki/FAQ#How_do_I_get_support_for_my_Waze_question.3F
 
== Update Requests with no immediately obvious issue ==
== Update Requests with no immediately obvious issue ==


=== General Error with no descriptive text ===
=== General Error with no descriptive text ===
Hi!  I'm a wazer like you working on the map.  If you describe the problem you had when you made your report, I'll do my best to fix it.


Hi!  I'm a wazer like you working on your "general error" report.  Waze does not tell us much about your drive and we're stumped.  What was wrong with the map?  Can you provide any detail?  Please respond using the Waze app;  emails don't work with the reporting system.
Thank you for your help.
 
(Any editor -- please follow up)
Thank you for your report.
(Open to any editor)


===  Wrong Driving Direction with no descriptive text ===
===  Wrong Driving Direction with no descriptive text ===


Hi!  I'm a wazer like you working on your "wrong driving direction" report. Waze does not tell us much about your drive; we don't even know where you were going!  What went wrong with the route Waze gave you?  Can you tell us your destination as you entered it into Waze?  Please answer from the Waze app; reply from email won't work with the reporting system.
Hi!  I'm a wazer like you working on your "wrong driving direction" report. Waze does not tell us much about your drive. What destination did you enter into Waze? What went wrong with the route Waze gave you?  Please answer from the Waze app.


Thank you for your report.
Thank you for your report.<br />
(Open to any editor)
(Any editor -- please follow up)


===  Incorrect Junction with no descriptive text ===
===  Incorrect Junction with no descriptive text ===


Hi!  I'm a wazer like you working on your "incorrect junction" report.  Waze does not tell us much about your drive.  What junction was incorrect?  What was incorrect about it?  Please answer from the Waze app; reply from email won't work with the reporting system.
Hi!  I'm a wazer like you working on your "incorrect junction" report.  Waze does not tell us much about your drive.  What junction was incorrect?  What was incorrect about it?  Please answer from the Waze app.


Thank you for your report.
Thank you for your report.<br />
(Open to any editor)
(Any editor -- please follow up)


===  Turn Not Allowed with no descriptive text ===
===  Turn Not Allowed with no descriptive text ===


Hi!  I'm a wazer like you working on your "turn not allowed" report.  Waze does not tell us much about your drive.  What turn was not allowed?  At what intersection?  Please answer from the Waze app; reply from email won't work with the reporting system.
Hi!  I'm a wazer like you working on your "turn not allowed" report.  Waze does not tell us much about your drive.  What turn was not allowed?  At what intersection?  Please answer from the Waze app.


Thank you for your report.
Thank you for your report.<br />
(Open to any editor)
(Any editor -- please follow up)
 
===Closing a UR ; not enough information to identify the problem after 1-week wait===
I am sorry we did not have enough information to identify your problem.  If the problem continues, please file a new report with details.  Thank you for your help.


== Update Requests with common solutions ==
== Update Requests with common solutions ==


=== No response ===
===Added a place or photo but it is not there ===
Hello!  I am a wazer like you working on map problems. 


We're sorry we could not identify your problem; we'll be closing this report. If it happens again, please submit a new map issue with enough information to find the problem. Thanks for your report!
I am guessing that one of three things happened.
1) You did not complete the creation of the place 00 make sure to tap the "Done" button when you are done.
2) You accidentally added the photo to another nearby place (like the police station, PS 30, or gas station), and it was rejected by a waze editor
3) You completed adding the place, but it was rejected by a waze editor.
 
For more information about adding places, and why photos or entire new places might be rejected by waze map editors, please see:
 
https://www.waze.com/en-GB/support/answer?q=42016336
https://wiki.waze.com/wiki/Places#Place_Updates_.28Moderation.29


=== Fixed -- road geometry change ===
=== Fixed -- road geometry change ===
Line 52: Line 72:
=== Pronunciation ===
=== Pronunciation ===


Hi!  I'm a wazer like you working on your report of poor pronunciation by Waze text-to-speech (TTS).  Unfortunately even the seniormost volunteers have little influence on the TTS system, and none of us can alter how any one street name is pronounced. I understand the frustration and I sympathize. Sorry not to be more help.  Thank you for your report!
Hi!  I'm a wazer like you working on your report of poor pronunciation by Waze text-to-speech (TTS).  Unfortunately, waze map editors cannot fix the way Waze pronounces street names. I wish we could. Sorry not to be more help.  Thank you for your report!


=== The "Waze 180" ===
=== The "Waze 180" ===


Hi!  I'm a wazer like you working on your report.  When you ask for a route immediately after waking up Waze, it has to guess what direction you are pointed. If it guesses wrong, it may give you an awkward route. When Waze does this, please drive a little in the direction you are pointed and then ask for the route againWaze will recalculate and may offer you a better route. If I've guessed your problem wrong, please answer from the Waze app; reply from email won't work. Otherwise we'll close out this report in a few days. Thank you for your report!  (Open to any editor)
Hi!  I'm a wazer like you working on your report.  It sounds as though Waze guessed wrong about which direction your car was pointed. Next time this happens, try driving a short distance and then ask for a route again, so Waze can recalculate. If this is not your problem, please let me know from your Waze app inbox. Thank you for your report!  (Any editor -- please follow up)
 
=== Waze location .. Search button .. remove old first ===


=== Google fu (easy) ===
Hi!  I'm a wazer like you working on your report. Waze now has the correct location for your destination. Before you search again, remove all instances of the destination from your recents and favorites lists. Then, when you search again, use the "search" button instead of the autocomplete list. Choose your destination and Waze will add it to your recents list for your future use, and you can add it to your favorite list.


Hi!  I'm a wazer like you working on your report.  The problem was caused by inaccurate data provided by Google (Waze gets most of its address locations from Google).  We asked Google to fix its database and they accepted the request.  Please allow at least three days for the fix to go live.  Then please remove the destination from your Waze app's navigation history and/or favorites list and wait at least a few minutes before adding it back.  This will remove the old (wrong) position.  Thank you for your report!
Thank you for your report!


=== Google fu (difficult) ===
=== Google Location change -- remove old first ===
 
Hi!  I'm a wazer like you working on your report.  We asked Google to correct the location and they did so. Please allow at least three days for the fix to go live.  Before you search again, remove all instances of the destination from your recents and favorites lists.
 
Thank you for your report!
 
=== Google update pending ===


Hi!  I'm a wazer like you working on your report.  The problem is caused by inaccurate data provided by Google (Waze gets most of its address locations from Google).  We have asked Google to fix its database but we have no control over how fast Google will respond.  It is usually days, but it can be weeks or even months.  We'll leave this report open in the meantime.  Thank you for your report!
Hi!  I'm a wazer like you working on your report.  The problem is caused by inaccurate data provided by Google (Waze gets most of its address locations from Google).  We have asked Google to fix its database but we have no control over how fast Google will respond.  It is usually days, but it can be weeks or even months.  We'll leave this report open in the meantime.  Thank you for your report!


=== Google FAIL, how to use Waze ===
=== Google FAIL, how to use Waze (difficult -- if waze INSISTS on going to Google) ===
 
Hi!  I'm a wazer like you working on your report. Waze appears to be getting an incorrect location from Google, and we can't persuade Google to change it. But you can work around this problem with Waze. First, remove all instances of the destination from your recents and favorites lists. When you search again, DO NOT SELECT ANY OF THE IMMEDIATELY-OFFERED ITEMS, EVEN IF YOU SEE A PERFECT MATCH!  Instead, use the "search" button, scroll to the bottom of the menu and select "More results for...".  Under "Other search engines", choose Waze and select your destination. Waze will add it to your recents list for your future use, and you can add it to your favorite list.


Hi!  I'm a wazer like you working on your report.  The problem is caused by inaccurate data provided by Google (Waze gets most of its destination locations from Google).  We cannot persuade Google to change its database for large or high-profile areas such as parks and airports. But you can work around this problem with Waze. First, remove all instances of the destination from your recents and favorites lists.  Then search again, but when you enter your search terms, DO NOT SELECT ANY OF THE IMMEDIATELY-OFFERED ITEMS, EVEN IF YOU SEE A PERFECT MATCH!  Instead, scroll to the bottom of the menu and select "More results for...".  Under "Other search engines", choose Waze and select your destination. This adds it to your recents list, and so you won't have to repeat the process the next time.  You can also add this correct location to your favorites list.
Thank you for your report!
Thank you for your report!
=== Bogus GPS ===
=== Bogus GPS ===


Hi!  I'm a wazer like you working on your report.  It looks like your GPS position information was inaccurate.  Bad GPS position data can cause all sorts of problems.  Waze may think you are on some other road and give you wrong directions to get you back to the road you're already on.  To prevent this, please give your handheld device as clear a view of the sky as possible so it can give you more accurate GPS positions.   
Hi!  I'm a wazer like you working on your report.  It looks like your GPS position information was inaccurate.  This can cause Waze to think you are on some other road and even to give you wrong directions to get you back to the road you're already on.  To prevent this, please give your handheld device as clear a view of the sky as possible so it can give you more accurate GPS positions.   


I'm sorry that there is nothing we can do to the maps to help you with this. Thank you for your report!
I'm sorry that there is nothing we can do to the maps to help you with this. Thank you for your report!
Line 80: Line 110:
Hi!  I'm a wazer like you working on your report.  It looks like you left Waze's recommended route, but Waze thought you were still following its instructions. GPS isn't perfect, and when you are travelling very close to the Waze route, Waze assumes you are still on its suggested route.  The instructions simply don't make any sense because you aren't on that route any more.
Hi!  I'm a wazer like you working on your report.  It looks like you left Waze's recommended route, but Waze thought you were still following its instructions. GPS isn't perfect, and when you are travelling very close to the Waze route, Waze assumes you are still on its suggested route.  The instructions simply don't make any sense because you aren't on that route any more.


Did you leave the route intentionally, or because the Waze instructions were confusing? Please respond using the Waze app; emails don't work with the reporting system.   
Did you leave the route intentionally, or because the Waze instructions were confusing? Please answer from  the Waze app.   


Thank you for your report.
Thank you for your report.<br />
(Open to any editor)
(Any editor -- please follow up)




Line 115: Line 145:
Hi!  I'm a wazer like you working on your report of a missing road or bridge overpass.  The drivable roads along this highway have been pretty thoroughly mapped and we can't see anything missing that should ordinarily be there. If you were driving at highway speeds, Waze could have chosen not to show you some smaller roads to avoid clutter. And the waze map display does not show the physical "stacking order" at overpasses; it puts more-major roads on top.  
Hi!  I'm a wazer like you working on your report of a missing road or bridge overpass.  The drivable roads along this highway have been pretty thoroughly mapped and we can't see anything missing that should ordinarily be there. If you were driving at highway speeds, Waze could have chosen not to show you some smaller roads to avoid clutter. And the waze map display does not show the physical "stacking order" at overpasses; it puts more-major roads on top.  


If you are certain a road is missing from the map (zoom in while parked off the road), please answer from the Waze app; reply from email won't work.  Thank you for your report!
If you are certain a road is missing from the map (zoom in while parked off the road), please answer from the Waze app.  Thank you for your report!


(Open to any editor)
(Any editor -- please follow up)


=== Short-term closure reported as a map issue ===
=== Short-term closure reported as a map issue ===


Hi!  I'm a wazer like you working on your report regarding a road closure.  How long will the road be closed? If it is only for a few days or less, we volunteer map editors can't be much help.  It takes at least that long for our edits to make it to handheld devices!  Next time you see short-term road closures, please use the Report->Closure feature in the Waze app (you used Report->Map issue to file this report).  If this is a long-term closure please answer from the Waze app (reply from email won't work) and tell us as much as you can.  Otherwise we'll close out this report in a few days. 
Hi!  I'm a wazer like you working on your report regarding a road closure.  How long will the road be closed? If it is only for a few days or less, please use the Report->Closure feature in the Waze app; it can show up on the map immediately.  Using Report->Map takes longer, and is good for longer-term closures, and even closures you know about well ahead of time.
 
If you are ever aware of a scheduled closure in advance of the road closing, please make a report with full details so we can schedule the map closure in advance.


Thank you for your report!  (Open to any editor)
If this is a long-term closure, please tell us as much as you can. If not, we'll close this report in a few days.
Thank you for your report!  (Any editor -- please follow up)


=== Used Map-Issue field to enter navigation destination ===
=== Used Map-Issue field to enter navigation destination ===


Hi!  I'm a wazer like you working on your report, which only contained an address. Did you mean to enter the address as a navigation destination?  If there is a problem with the address please answer from the Waze app (reply from email won't work) and explain what went wrong. Otherwise we'll assume this was an accident and close out this report in a few days.  Thank you for your report!  (Open to any editor)
Hi!  I'm a wazer like you working on your report, which only contained an address. Did you mean to enter the address as a navigation destination?  If there is a problem with the address please answer from the Waze app and explain what went wrong. Otherwise we'll assume this was an accident and close out this report in a few days.  Thank you for your report!  (Any editor -- please follow up)


=== No hablo muy bien el Español ===
=== No hablo muy bien el Español ===
Line 160: Line 189:


There is nothing we can do to the map to change this behavior.  I am sorry I can't help.  Thanks for your report.
There is nothing we can do to the map to change this behavior.  I am sorry I can't help.  Thanks for your report.
[[Category:Sample responses]]

Latest revision as of 20:37, 16 March 2015

This is a collection of boilerplate responses for most typically encountered UR issues.
Many thanks to DwarfLord, from whom I copied most of this text. I only changed the wording to sound more like me.

Odds and Ends

Wrapper

Hi! I'm a wazer like you working on your report. Please respond using the Waze app; emails don't work with the reporting system.

Thank you for your report.
(Any editor -- please follow up)

Contact Support

If you wish to contact the Waze team, please follow the instructions at http://wiki.waze.com/wiki/FAQ#How_do_I_get_support_for_my_Waze_question.3F

Suggest Improvements

please post on the waze forum at https://www.waze.com/forum/viewforum.php?f=3 or follow the support instructions at https://wiki.waze.com/wiki/FAQ#How_do_I_get_support_for_my_Waze_question.3F

Update Requests with no immediately obvious issue

General Error with no descriptive text

Hi! I'm a wazer like you working on the map. If you describe the problem you had when you made your report, I'll do my best to fix it.

Thank you for your help. (Any editor -- please follow up)

Wrong Driving Direction with no descriptive text

Hi! I'm a wazer like you working on your "wrong driving direction" report. Waze does not tell us much about your drive. What destination did you enter into Waze? What went wrong with the route Waze gave you? Please answer from the Waze app.

Thank you for your report.
(Any editor -- please follow up)

Incorrect Junction with no descriptive text

Hi! I'm a wazer like you working on your "incorrect junction" report. Waze does not tell us much about your drive. What junction was incorrect? What was incorrect about it? Please answer from the Waze app.

Thank you for your report.
(Any editor -- please follow up)

Turn Not Allowed with no descriptive text

Hi! I'm a wazer like you working on your "turn not allowed" report. Waze does not tell us much about your drive. What turn was not allowed? At what intersection? Please answer from the Waze app.

Thank you for your report.
(Any editor -- please follow up)

Closing a UR ; not enough information to identify the problem after 1-week wait

I am sorry we did not have enough information to identify your problem. If the problem continues, please file a new report with details. Thank you for your help.

Update Requests with common solutions

Added a place or photo but it is not there

Hello! I am a wazer like you working on map problems.

I am guessing that one of three things happened. 1) You did not complete the creation of the place 00 make sure to tap the "Done" button when you are done. 2) You accidentally added the photo to another nearby place (like the police station, PS 30, or gas station), and it was rejected by a waze editor 3) You completed adding the place, but it was rejected by a waze editor.

For more information about adding places, and why photos or entire new places might be rejected by waze map editors, please see:

https://www.waze.com/en-GB/support/answer?q=42016336 https://wiki.waze.com/wiki/Places#Place_Updates_.28Moderation.29

Fixed -- road geometry change

Hi! I'm a wazer like you working on your report. Thanks to your report we've found and fixed a problem with the map. You should see the fix within 2 days. Thank you for your report!


Fixed -- other change

Hi! I'm a wazer like you working on your report. Thanks to your report we've found and fixed a problem with the map. You should see the fix within 2 weeks. Thank you for your report!

Pronunciation

Hi! I'm a wazer like you working on your report of poor pronunciation by Waze text-to-speech (TTS). Unfortunately, waze map editors cannot fix the way Waze pronounces street names. I wish we could. Sorry not to be more help. Thank you for your report!

The "Waze 180"

Hi! I'm a wazer like you working on your report. It sounds as though Waze guessed wrong about which direction your car was pointed. Next time this happens, try driving a short distance and then ask for a route again, so Waze can recalculate. If this is not your problem, please let me know from your Waze app inbox. Thank you for your report! (Any editor -- please follow up)

Waze location .. Search button .. remove old first

Hi! I'm a wazer like you working on your report. Waze now has the correct location for your destination. Before you search again, remove all instances of the destination from your recents and favorites lists. Then, when you search again, use the "search" button instead of the autocomplete list. Choose your destination and Waze will add it to your recents list for your future use, and you can add it to your favorite list.

Thank you for your report!

Google Location change -- remove old first

Hi! I'm a wazer like you working on your report. We asked Google to correct the location and they did so. Please allow at least three days for the fix to go live. Before you search again, remove all instances of the destination from your recents and favorites lists.

Thank you for your report!

Google update pending

Hi! I'm a wazer like you working on your report. The problem is caused by inaccurate data provided by Google (Waze gets most of its address locations from Google). We have asked Google to fix its database but we have no control over how fast Google will respond. It is usually days, but it can be weeks or even months. We'll leave this report open in the meantime. Thank you for your report!

Google FAIL, how to use Waze (difficult -- if waze INSISTS on going to Google)

Hi! I'm a wazer like you working on your report. Waze appears to be getting an incorrect location from Google, and we can't persuade Google to change it. But you can work around this problem with Waze. First, remove all instances of the destination from your recents and favorites lists. When you search again, DO NOT SELECT ANY OF THE IMMEDIATELY-OFFERED ITEMS, EVEN IF YOU SEE A PERFECT MATCH! Instead, use the "search" button, scroll to the bottom of the menu and select "More results for...". Under "Other search engines", choose Waze and select your destination. Waze will add it to your recents list for your future use, and you can add it to your favorite list.

Thank you for your report!

Bogus GPS

Hi! I'm a wazer like you working on your report. It looks like your GPS position information was inaccurate. This can cause Waze to think you are on some other road and even to give you wrong directions to get you back to the road you're already on. To prevent this, please give your handheld device as clear a view of the sky as possible so it can give you more accurate GPS positions.

I'm sorry that there is nothing we can do to the maps to help you with this. Thank you for your report!

Still tracking stale route

Hi! I'm a wazer like you working on your report. It looks like you left Waze's recommended route, but Waze thought you were still following its instructions. GPS isn't perfect, and when you are travelling very close to the Waze route, Waze assumes you are still on its suggested route. The instructions simply don't make any sense because you aren't on that route any more.

Did you leave the route intentionally, or because the Waze instructions were confusing? Please answer from the Waze app.

Thank you for your report.
(Any editor -- please follow up)


Stale or bogus traffic indications/routing

Hi! I'm a wazer like you working on your report about wrong traffic indications. We volunteer map editors can't do anything about Waze's traffic reporting, but I can explain what may have happened.

Waze relies on data from people using Waze to assess traffic. In the case of a fresh accident or slowdown, Waze may not yet have enough data to realize it needs to route you around it. After enough Wazers are caught in the slow-down, Waze will start routing wazers around the traffic. Then, after the traffic improves, it may take a while before Waze has enough data to understand this, and may keep routing wazers around the area. Sometimes, slow-moving or parked Wazers can make Waze think there is bad traffic (never run Waze while walking, biking, or parking along roads).

I'm sorry we can't help you with this. Thank you for your report!

Waited forever to make Waze's recommended left turn

Hi! I'm a wazer like you working on your report. I would hate it too if Waze asked me to make a left turn through heavy traffic!

Unfortunately, there is nothing we can do to tell waze to recommend a different route. The good news is that Waze keeps track of how long it takes to make a turn. Thanks to your experience, other drivers are less likely to be routed this way during peak traffic hours. Thank you for your report!

Unexplained detour

Hi! I'm a wazer like you working on your report. I can't find anything in the map to explain the detour Waze gave you. Waze may have thought there was traffic, or a daily pattern of traffic at that time. Or maybe Waze does not have enough data to know that the detour is not actually faster. Sometimes, waze suggests complex detours to shave a few seconds off your trip, or it is relying on slightly stale traffic data while it waits for more Wazers to drive through. Or other Wazers may have reported a temporary street closure in the area.

Because we cannot identify any problem with the map itself, we cannot find anything to fix. I'm sorry we cannot help you. Thank you for your report!

Unexplained NON-detour

Hi! I'm a wazer like you working on your report. I can't find anything on the map to explain why Waze did not route you around the traffic. Waze may not yet have had enough data from wazers to know the traffic was bad on the route it recommended, or had stale traffic data about the route it rejected.

Map editors can't do anything about Waze traffic detection and routing, but we have checked that the map itself looks OK. Thank you for your report!

Bogus "missing road" and "missing bridge overpass" reports from highway drivers

Hi! I'm a wazer like you working on your report of a missing road or bridge overpass. The drivable roads along this highway have been pretty thoroughly mapped and we can't see anything missing that should ordinarily be there. If you were driving at highway speeds, Waze could have chosen not to show you some smaller roads to avoid clutter. And the waze map display does not show the physical "stacking order" at overpasses; it puts more-major roads on top.

If you are certain a road is missing from the map (zoom in while parked off the road), please answer from the Waze app. Thank you for your report!

(Any editor -- please follow up)

Short-term closure reported as a map issue

Hi! I'm a wazer like you working on your report regarding a road closure. How long will the road be closed? If it is only for a few days or less, please use the Report->Closure feature in the Waze app; it can show up on the map immediately. Using Report->Map takes longer, and is good for longer-term closures, and even closures you know about well ahead of time.

If this is a long-term closure, please tell us as much as you can. If not, we'll close this report in a few days. Thank you for your report! (Any editor -- please follow up)

Used Map-Issue field to enter navigation destination

Hi! I'm a wazer like you working on your report, which only contained an address. Did you mean to enter the address as a navigation destination? If there is a problem with the address please answer from the Waze app and explain what went wrong. Otherwise we'll assume this was an accident and close out this report in a few days. Thank you for your report! (Any editor -- please follow up)

No hablo muy bien el Español

Lo siento, estamos voluntarios solamente para mantener las mapas. No hablamos muy bien el Español y no podemos ayudar con el aplicación.

(Regrets, we are volunteers only for maintaining the maps. We don't speak Spanish well and we can't help with the application.)

NO THRU TRAFFIC

Hi! I'm a wazer like you working on your report. When a road is posted RESIDENTIAL ONLY or NO THRU TRAFFIC, we map editors need to respect that. And the only way to signal this in Waze is to call it a private road. If you do choose to drive on this road, Waze will automatically recalculate a route toward your destination.

I'm sorry for the confusion. It is confusing for map editors too. Thank you for your report.

Possible routing bug

Hi! I'm a wazer like you working on your report. The little bit of your drive Waze shows with your report looks like a weird choice to me, too. I've checked everywhere I can think of and unfortunately I can't find anything wrong with the map.

At the moment, Waze is currently working speed detection for different turns out of an intersection. In rare instances this issue can lead Waze to suggest non-ideal routes, usually involving one or more U-turns or loops. I have no way to know if this is the cause of your issue, I am certain that I cannot identify any possible cause on the map.

I'm sorry I cannot help. Thanks for your report.

We can't do U-turns

Hi! I'm a wazer like you working on your report about U-turns. Waze does consider U-turns when preparing a route for you, but the app cannot yet give voice instructions for U-turns. Since this could make it hard for drivers to follow any route that includes U-turns, the editing community has decided to tell Waze that these U-turns are not allowed. This includes the U-turn that you wanted to make. One day, we hope Waze will improve this feature. Until then, I am sorry that I cannot identify any map fixes to help you. Thank you for your report.

We can't do "continue straight" (usually a followup response)

I've seen that too, and it can be confusing. The Waze app by intention has no "continue straight" voice instruction, to limit the distractions while you drive.

There is nothing we can do to the map to change this behavior. I am sorry I can't help. Thanks for your report.