Working the System Admin queue in the middle of the night I see lots of different kinds of tickets. One thing that has become clear over the months is that a well formed ticket is a happy ticket and a quickly resolved one. What makes a well-formed ticket? Mostly it is all about information and attention to these few suggestions can do a great deal toward speeding your ticket toward a conclusion.
When you create a ticket you’re asked to choose a category for it, such as “Portal Information Question” or “Reboots and Remote Access”. Selecting the proper category helps us to triage the tickets. If you’re locked out of your server, say due to a firewall configuration, you’d use “Reboots and Remote Access”. We have certain guys who are better at CDNLayer tickets, for example, and they will seek out those kind so if you have a CDN question, you’d be best served by using that category. Avoid using Sales and Accounting tickets for technical issues as those end up first in their respective departments and not in support.
This one is a bit controversial. I’m going to state straight out… I get that some people don’t want us knowing the login information for the server. My personal server at SoftLayer doesn’t have up-to-date login information in the portal. I do this knowing that this could slow things down if I ever had to have one of the guys take a look at it while I’m not at work.
If necessary, we can ask for it in the ticket but that can cost you time that we could otherwise be addressing your issue. If you would like us to log into your server for assistance, please provide us with valid login information in the ticket form. Providing up-to-date login credentials will greatly expedite the troubleshooting process and mitigate any potential downtime, but is not a requirement for us to help with issues you may be facing.
If you have multiple servers with us, please make sure to clearly identify the system involved in the issue. If we have a doubt, we’re going to stop and ask you, which again can cost you time.
This is really the big one. When typing up the problem description in the ticket please provide as much detail as you can. Each sentence of information about the issue can cut out multiple troubleshooting steps which is going to lead to a faster resolution for you.
- Not-so-good: I cannot access my server!
- Good: I was making adjustments to the Windows 2008 firewall on my server and I denied my home IP of 22.214.171.124 instead of allowing it. Please fix.
The tickets describe the same symptom. I can guarantee though we’re going to have the second customer back into his server quicker because we have good information about the situation and can go straight to the source of the problem.