What We Treat as Urgent

What counts as urgent

• A service that is completely down or unreachable, not just slow.
• A security issue in progress, active unauthorized access, an ongoing attack, a compromised account.
• A billing error actively blocking access to a service you have already paid for.

These get triaged ahead of the general queue. Everything else, configuration questions, feature requests, non-blocking issues, is answered in the order it arrives, still quickly, just without jumping the line.

What does not need the urgent flag

A slow site, a question about how a feature works, or a request that is not time-critical are all valid tickets, just not urgent ones. Marking everything urgent does not get it answered faster, it just makes the flag meaningless for the tickets that actually need it.

Writing a ticket that gets answered faster

• Say what service is affected, by name or ID, not just "my server".
• Say what you expected to happen and what actually happened, the gap between those two is usually the whole diagnosis.
• Include the exact error message if there is one, paraphrasing it usually loses the one detail that would have identified the problem immediately.
• Say when it started, "just now" and "for three days" point support in very different directions.

Live chat vs tickets

Live chat on the site and in the customer panel is the fastest path for a quick question and can escalate straight to a human agent when needed. Anything that needs investigation, file access, or a paper trail is better as a support ticket from the start.

The fastest way to get a useful answer is the same regardless of urgency: say exactly what you expected, what happened instead, and when it started.