How to Write a Support Ticket That Gets Answered Fast

We've written honestly about what our support actually covers before. Here's the practical flip side: how to write a ticket that gets resolved in one reply instead of five back-and-forths.

The One Thing That Matters Most

Include your service/order ID. Support can look up exactly what plan, node, and configuration you're on instantly with it — without it, the first reply is almost always just "can you share your service ID," which burns an entire round trip before real troubleshooting even starts. Find it on your service's management page.

The Information That Actually Speeds Things Up

• What you expected to happen, vs. what actually happened. "It's not working" describes nothing; "I restarted the server and it shows 'Connection refused' when I try to join" describes something we can act on immediately.
• The exact error message, copy-pasted or screenshotted — not paraphrased. Error text often contains the actual diagnostic clue (a file path, an error code, a specific plugin name) that gets lost in a summary.
• Console output, if it's a startup/crash issue — check our console guide for where to find it, and paste the relevant lines (usually the last 20-30 lines before the failure, not just one line out of context).
• What changed recently. A plugin install, a config edit, a version change, an add-on purchase — most issues trace directly back to the most recent change, and naming it upfront skips a whole investigation step.
• When it started, roughly — helps correlate with anything on our side (maintenance, an incident) versus something specific to your service.

What Slows Things Down

• Vague titles like "help" or "server broken" — a specific title ("Minecraft server crashes on startup after Paper update") lets the right person pick it up faster.
• Multiple unrelated issues crammed into one ticket — separate tickets for separate problems get resolved faster than one ticket juggling three things at once.
• Screenshots of text instead of pasted text, when pasting is possible — text is searchable and copyable for troubleshooting; a screenshot of an error isn't.

Urgent vs Not

For anything genuinely time-sensitive, live chat/Discord gets a faster response than the ticket queue — save tickets for things that benefit from a documented, detailed back-and-forth (config issues, billing questions, anything needing investigation) rather than "is the server down right now."

The Bottom Line

A ticket with a service ID, a clear description, and the actual error/console output usually gets solved in one reply. A ticket that just says something's wrong usually takes three replies just to get to the point where real troubleshooting can start — the extra two minutes writing it properly is faster than it feels.