Where Does Your Ticket Stand in the Support Queue?
Your website is down, a 500 error appears on every page, and you have opened a ticket titled "The site has a problem." Eight hours have passed and still no response. You have also submitted another ticket to change the PHP version and think no one has seen it. Both tickets are in the same queue, but only one of them should get an immediate response.
The problem starts when you don't know what "ticket priority" means or you choose it incorrectly. In this guide, we will explain what each level exactly means, what information determines the level, and how long you should expect to wait for a response for each one.
The Four Ticket Priority Levels and What Each One Means
At ServerNet, every support ticket receives one of four levels: Normal, Important, Urgent, and Critical. These levels are not random; they are determined based on the impact of the issue on your service and the number of users affected.
Normal — General Questions and Non-Urgent Requests
A question about how to configure a feature, a request to change settings without any rush, or a question about billing. Your service is healthy and no users are affected. Expected response time: up to 24 business hours.
Real-world example: "How can I activate the free SSL on my second domain?" This is a normal ticket, even if it matters to you. Because the main site is working and this request can wait a few hours.
Important — Minor Disruption or a Request with a Specific Deadline
Part of your service is having an issue, but the entire site is not out of reach. Or you have a request that must be completed by a specific time. Expected response time: up to 8 business hours.
Example: The contact form on your site is throwing an error, but the rest of the pages are fine. Or "I need to move the domain to a new server by tomorrow morning." This level requires action, but it's not a fire.
Urgent — Complete Service Outage or Widespread Error
The site is completely inaccessible, the database is not responding, or an error appears on every page. Your users are affected, and every hour of downtime means lost revenue or credibility. Expected response time: up to 2 hours.
Here you need to provide evidence. Not just "the site isn't working," but the output of curl -I https://example.com, a screenshot of the error, and the exact time the issue started. The more initial information you provide, the faster the support team can get to the root of the matter.
Critical — Complete Outage with Financial or Security Damage
An e-commerce site is down during peak shopping hours, or you see evidence of a server intrusion. This level is for situations where every minute of downtime has a direct cost or sensitive data is at risk. Expected response time: maximum 30 minutes.
Keep the critical ticket for truly critical situations only. If you choose this level for every small issue, you will lose credibility with the support team, and when you really need immediate help, it might not be taken seriously.
What Information Determines the Ticket Level?
Three main factors determine the level of your ticket. If you include these in the first ticket, both the correct level will be assigned and the response time will be shorter.
- Scope of impact: How many users are affected? Just you or all site visitors?
- Error severity: Is the service completely down or does only one part have an issue? A 500 error is different from a 404 error.
- Time sensitivity: Is there a specific deadline? For example, "An advertising campaign starts tomorrow."
A good ticket looks something like this: "Since 2:30 PM today, the site has been responding with a 503 error. I have attached the curl output. All pages are affected, and our store has the most traffic between 4 PM and 10 PM. Priority: Critical."
This ticket is understandable within the first 30 seconds, and the support team immediately knows where to start. In contrast, a ticket saying "the site has a problem" requires several rounds of back-and-forth and wastes time.
Where People Go Wrong: Choosing the Level Based on Emotion, Not Facts
The most common mistake is that users mark a ticket as "Urgent" because they are stressed, not because the issue is actually urgent. What's the result? The support team sees the real critical tickets in the queue and reviews your ticket with a lower level. Then you get upset that "why didn't they respond to my urgent ticket?"
The sign of this mistake: a ticket with urgent priority whose content is a simple configuration question. Or the opposite, a ticket with normal priority while the site is down. Both situations are equally problematic. The first destroys the support team's trust, and the second causes your real issue to sit in the queue for hours.
Before choosing a level, ask yourself one question: "If it were 3 AM right now and no one was at their desk, could this issue wait until morning?" If the answer is yes, your level is not urgent or critical.
Response Time vs. Resolution Time: Don't Confuse the Two
Response time means the first reaction of the support team to your ticket. This does not necessarily mean the issue is resolved. The first response might be: "We see the problem, we are investigating" or "Please send the output of this command for a more accurate diagnosis."
Resolution time depends on the nature of the issue. A simple settings change might be done in 10 minutes. A DDoS attack or hardware failure might take hours. No hosting company can give a definitive resolution time for all issues, because some problems depend on factors outside their control.
Keep this difference in mind in your ticket. If you received the first response within the expected time but the issue is not resolved, should you close the ticket and open a new one? No. Continue on the same ticket and follow up. Opening a new ticket only removes the history and makes diagnosing the issue harder.
How to Prepare Your Ticket for a Faster Response
Before submitting a ticket, go through this checklist. Every item you miss adds an extra round-trip to the support process.
- Attach the output of
curl -Iorcurl -vfrom the problematic address. - Write the exact time the issue started. "Since yesterday" doesn't help; "since 2:30 PM today" can be investigated.
- Mention recent changes on the server: have you installed a plugin? Changed DNS settings?
- Be sure to include the service number or the relevant domain.
- If you see an error in the logs, copy the last few lines. Not the entire file, just the part related to the error.
This information allows the support team to go straight to troubleshooting without asking additional questions. The result: a faster and more accurate first response.
Choosing Between Levels: A Rule of Thumb
If you are torn between two levels, choose the lower one. Why? Because a ticket with a higher level than needed raises your expectation of the response time, and if you don't get a response within that window, you become dissatisfied. A ticket with a lower level that gets a response earlier than expected creates a better experience for you.
The only exception: if you have a security issue or see evidence of an intrusion, choose the critical level without hesitation. In this case, erring in the opposite direction is better than being too late.
To learn about the structure of services and which option is right for your work, you can see the guide to choosing between shared hosting, VPS, and dedicated servers. Also, if you have just purchased a service, the first 24 hours checklist tells you what settings you should configure before getting started. To better understand the terms you see in tickets and documentation, review the hosting terms glossary and the networking terms glossary.
Frequently Asked Questions
What is the maximum response time for a critical ticket?
A critical ticket receives an initial response within a maximum of 30 minutes. This response may only be an acknowledgment of receipt and the start of an investigation, not a complete resolution. If no response comes after 30 minutes, follow up on the ticket by phone.
What happens if I choose the ticket priority incorrectly?
The support team may correct the level of your ticket. If you have chosen a level higher than needed, the ticket will be lowered to the actual level, and the response time will be calculated based on that level. If you have chosen a lower level and the issue is truly urgent, the level will be raised after the initial review.
Can I change the ticket priority after submitting it?
Yes, as long as the support team has not started working on the ticket. After the investigation has begun, changing the priority only affects responses to subsequent follow-ups. If the situation changes (for example, the issue spreads from one part to the entire site), open a new ticket with a higher priority and refer to the previous ticket.
What is the difference between responding to and resolving an issue in a ticket?
A response means the first reaction of the support team to your ticket, which is done within the specified time frame for each level. Resolving the issue means completely fixing the error or fulfilling your request, the time for which depends on the nature of the issue and cannot be given a definitive time. Your ticket remains open until the issue is resolved.