A useful ticket describes a reproducible symptom and its impact. “My website is broken” leaves many possibilities open, while an exact URL, error and timestamp help Support investigate the right component. Keep each ticket focused on one issue and reply to the same conversation when more evidence becomes available.
Recommended steps
- Select Technical Support for website or server faults, Domains & SSL for domain and certificate questions, Billing for invoices, and Migrations for planned transfers of website data.
- Identify the affected service and hostname. Include the exact page or action that fails, what you expected to happen, and whether the problem affects every visitor or only a particular user.
- Record the first observed time and your time zone. Copy the visible error message and HTTP status if available. Include relevant log excerpts around that time rather than an entire unrelated log archive.
- Describe recent changes such as a plugin update, DNS edit, certificate installation or PHP switch. Explain the checks already completed and their results, including a test from another network where useful.
- Remove passwords, session cookies, authentication tokens and personal customer data from screenshots and logs. Ask for an approved secure access method if a technician needs temporary permissions.
State the business impact accurately, such as a checkout failure or a single mailbox delivery issue. Clear evidence helps distinguish application errors, account limits and network problems, and reduces the number of clarification messages needed before investigation can begin.
