Utah/Other/Main: Difference between revisions View history

(changed UR schedule to ASAP/7/7)
 
Line 5: Line 5:
=== Working with URs ===
=== Working with URs ===


{{RootPage2}} has adopted a '''36hr/4/7 day''' standard when dealing with User Requests.
{{RootPage2}} has adopted a '''ASAP/7/7 day''' standard when dealing with User Requests.
[[Image:Request pin open-low.png|left]] Our goal is to respond to new URs within 36 hours. Fix the issue and solve the UR (if within our control, and identifiable), or solicit additional needed information from the reporter.
[[Image:Request pin open-low.png|left]] Our goal is to respond to new URs as soon as possible. Fix the issue and solve the UR (if within our control, and identifiable), or solicit additional needed information from the reporter.
{{clear}}
{{clear}}
[[Image:Request pin open-med.png|left]] If there is no response from the reporter within 4 days, "bump" the request with a reminder message.  
[[Image:Request pin open-med.png|left]] If there is no response from the reporter within 7 days, "bump" the request with a reminder message.  
{{clear}}
{{clear}}
[[Image:Request pin open-med.png|left]] If there is a response from the reporter, and a conversation starts about the error and how to resolve it, the 7 day clock starts over.  
[[Image:Request pin open-med.png|left]] If there is a response from the reporter, and a conversation starts about the error and how to resolve it, the 7 day clock starts over.  
{{clear}}
{{clear}}
[[Image:Request pin open-high.png|left]] Resolve URs that have no response to comment in 7 days, or are completed. '''NEVER close a UR without leaving a closing comment''', even if it's something as simple as ''"No info received, closing."''
[[Image:Request pin open-high.png|left]] Resolve URs that have no response to comment in 7 days, or are completed. '''NEVER close a UR without leaving a closing comment''', even if it's something as simple as ''"No info received, closing."'' This includes URs you've left for yourself to address, as closed URs with zero comments show up as "red flags" to area managers.


<br />
<br />

Latest revision as of 16:54, 27 March 2017



Working with URs

Utah has adopted a ASAP/7/7 day standard when dealing with User Requests.

Our goal is to respond to new URs as soon as possible. Fix the issue and solve the UR (if within our control, and identifiable), or solicit additional needed information from the reporter.

If there is no response from the reporter within 7 days, "bump" the request with a reminder message.

If there is a response from the reporter, and a conversation starts about the error and how to resolve it, the 7 day clock starts over.

Resolve URs that have no response to comment in 7 days, or are completed. NEVER close a UR without leaving a closing comment, even if it's something as simple as "No info received, closing." This includes URs you've left for yourself to address, as closed URs with zero comments show up as "red flags" to area managers.


When responding to URs, please remember the wise words of the scholar, brevity is the soul of wit.

More than likely, the user is going to be reading your response in the Waze App, so try and keep it as short as possible, while still conveying the information, or request desired.

Before working with URs, you should review the Wiki documentation on URs and especially the section on etiquette.


Don't be this guy.

Live Users

If you're editing in Utah, we ask that you turn on the LIVE USERS layer in the editor. If you see another editor show up where you are editing, and move around you, please check WME Chat. Also, check and see if you have a Private Message (PM) in the Forum.

There may be an issue with the area you're editing in, or what you are doing.

Never Be Unreachable!