| - |
*Post only the error in the description (this hardly ever enough information for us to help you)
|
+ |
*Post <u>only</u> the error in the description (this hardly ever enough information for us to help you)
|
| - |
*Leave out basic information about the third party product you're interfacing with (We're way more familiar with uDeploy than what we integrate with here in support)
|
+ |
*Leave out basic information about the third party product you're interfacing with (We're way more familiar with uDeploy than we are with third party products here in support)
|
| - |
*Use the same ticket for a different problem unless it stems from the original issue (we use tickets for future troubleshooting)
|
+ |
*Use the same ticket for a different problem unless it stems from the original issue (we use tickets for future troubleshooting. Please, no "oh by the way"s)
|
| |
*Use the same priority for all tickets (If it's very time sensitive and/or detrimental to production, make it High. If not, it's probably medium or low. Check your SLAs. This helps us manage our work queue) |
|
*Use the same priority for all tickets (If it's very time sensitive and/or detrimental to production, make it High. If not, it's probably medium or low. Check your SLAs. This helps us manage our work queue) |
