Version Differences for Common Support Issues

*Use the same ticket for a different problem unless it stems from the original issue (we use tickets for future troubleshooting)

*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)

+

== Webexes ==

+

We would always rather have a meeting to immediately address the issue and close the ticket, rather than having a long dialogue. Unfortunately, our workload often impedes this possibility barring dire circumstances. It's a simple matter of when on a meeting, one support specialist can help one customer at a time. When handling issues over tickets, one support specialist can help multiple customers simultaneously. Many tickets require reproduction or feedback that we could do or receive offline, and a meeting would be inefficient for these tasks. With that being said, if you've already configured production deployments and they have suddenly encountered errors, these types of ticket take priority and a webex will likely be arranged immediately if needed. If you have problems or questions about configuration, these meetings will need to be scheduled for when it will have the least impact on supporting other customers, and may not be scheduled immediately. If for some reason your configuration is under an urgent time constraint, every effort should be made to make Urbancode aware of your situation before it becomes urgent so that we can prepare resources beforehand to handle your needs. When creating your tickets, please adhere as closely to the above guideline so that when we can't schedule a meeting, the dialogue over the ticket is kept to a minimum, and the issue is identified and resolved efficiently.

 *Use the same ticket for a different problem unless it stems from the original issue (we use tickets for future troubleshooting)
 *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)
                 == Webexes ==
                 We would always rather have a meeting to immediately address the issue and close the ticket, rather than having a long dialogue. Unfortunately, our workload often impedes this possibility barring dire circumstances. It's a simple matter of when on a meeting, one support specialist can help one customer at a time. When handling issues over tickets, one support specialist can help multiple customers simultaneously. Many tickets require reproduction or feedback that we could do or receive offline, and a meeting would be inefficient for these tasks. With that being said, if you've already configured production deployments and they have suddenly encountered errors, these types of ticket take priority and a webex will likely be arranged immediately if needed. If you have problems or questions about configuration, these meetings will need to be scheduled for when it will have the least impact on supporting other customers, and may not be scheduled immediately. If for some reason your configuration is under an urgent time constraint, every effort should be made to make Urbancode aware of your situation before it becomes urgent so that we can prepare resources beforehand to handle your needs. When creating your tickets, please adhere as closely to the above guideline so that when we can't schedule a meeting, the dialogue over the ticket is kept to a minimum, and the issue is identified and resolved efficiently.