Identify the service
Include the domain, hosting account, or cloud server involved and describe which action is failing.
Support
Get to the right support path quickly.
Existing customers should use the client area and ticket system so service, billing, and technical requests keep the right account context. Pre-sales and general questions can use the contact page.
Before you submit
A useful ticket reduces back-and-forth.
Give support enough context to identify the service and reproduce the issue without sending secrets that should never be in a ticket.
Add timing and changes
Include timestamps, when the issue began, and any update, deployment, DNS change, or configuration change that happened first.
Keep credentials private
Do not send passwords, private keys, API secrets, or full payment details in general contact forms.
Common routes