What information to include in a support ticket

Quick answer: A solvable ticket names the service (ID or IP), the exact time with timezone, the precise symptom (error text, not "doesn't work"), what changed right before, and what you already tried. With those five items support can start working immediately instead of asking clarifying questions for a day.

Overview

Support sees your account and platform-side state, but not inside your unmanaged server — your description and logs are the only window. The difference between a one-reply fix and a long back-and-forth is almost always the quality of the first message.

Before you start

• Five minutes to gather facts — it pays back the same day.

Step-by-step guide

1. Identify the service: service ID from My Services or the main IP. If you have several servers, name the affected one explicitly.
2. Time and timezone: "2026-07-16 14:07 EEST, still ongoing" — support correlates this with platform logs.
3. Exact symptom: paste the error verbatim (SSH output, browser error code, log line). Include the URL if web-related.
4. What changed: updates, config edits, new plugins, traffic spikes, invoices — the honest answer often IS the diagnosis.
5. What you tried: "rebooted, checked df -h (40% free), nginx restarts cleanly" prevents duplicate suggestions.
6. Attach evidence: the log excerpts from collecting logs for support; for network issues, MTR both directions per the network report guide.
7. Pick the right department when opening the ticket and keep one issue per ticket.

Common issues

• "Server slow, fix asap" with no data: guarantees a first reply that only asks questions.
• Mixing three problems in one ticket: threads tangle and things get missed — split them.
• Replying from a different email: tickets are tied to your account address — see contacting support.
• Withholding the recent change: support finds it anyway, later — telling upfront saves a day.

When to contact support

Always, when the platform side is suspect or you are stuck — a well-formed ticket via the Client Area (or email to [email protected]) is the fastest path to resolution.

Frequently asked questions

What are the five essentials of a good ticket?

The affected service ID or IP, the exact time with timezone, the verbatim error message, what changed right before the problem, and the steps you already tried with their results.

Can support fix problems inside my server for me?

Services are unmanaged, so the OS and applications are customer territory, but support diagnoses platform-side issues and guides you — good evidence in the ticket makes that fast.

Can I open a ticket by email?

Yes — write to [email protected] from your account email address and the message automatically becomes a ticket linked to your account, exactly like one opened in the Client Area.

Related articles

• How to collect logs for support
• How to contact Cloud2Y support
• How to report network issues to support

Need a hand? Contact Cloud2Y support →