Skip to content
✅ Published
DE EN FR RU

Writing a Good Support Ticket

Providing this info helps us help you faster and more effectively.

🕒 Updated: 23.08.2026 11:24
#support #ticket #help #contact

Information to always include

  1. Affected product / contract ID (e.g. domain name, VPS hostname, invoice no.)
  2. Steps to reproduce
  3. Error message exactly as shown + screenshot (always capture the text additionally – OCR is imperfect)
  4. Steps already tried and their outcome
  5. Environment: OS/browser, source IP, firewall/proxy
Priorities

Standard — reply ≤ 24h Mon–Fri · High priority (outage of paid service) — 2h SLA · Critical outage — live chat + phone number in the portal.

Was this article helpful?

Your feedback helps us improve the documentation continuously.