Quick answer
A good issue report describes what you tried, what happened, and what should have happened. Specific evidence helps support distinguish a repeatable website defect from a device, account, network, or cached-session problem.
Before you begin
Note the website URL, date and time with time zone, browser, device, and whether you were signed in. Avoid posting passwords, payment information, or customer data.
What to do
- Write the shortest sequence of steps that produces the issue. Start from a known page and include the exact control or option you selected.
- Describe the expected result and actual result separately. Include the complete visible error message if it does not contain private information.
- Capture a screenshot or short recording showing relevant context. Redact account details and unrelated browser tabs.
- Check a fresh visit or another supported browser if safe. Record whether the issue is consistent, intermittent, or limited to one account.
- Provide an example reference, such as an order or form submission ID, through the approved support channel. Do not repeatedly submit real transactions to gather more examples.
How to check the result
Another person should be able to repeat your steps or understand exactly what evidence is missing. A report saying only that the website is broken usually needs further clarification before work can begin.
If you need help
If customers are blocked or data may be affected, state the business impact early. Keep a single support thread updated so investigation notes, decisions, and recovery actions remain connected.
Related help
- Send a website support request with useful troubleshooting details
- Check that website integrations continue to work
- Create a clear handoff after a website incident
Official references
Reviewed October 31, 2026. Interfaces, vendor availability, and account features can change. Check your current account before making changes.
