Describe the problem, not only the symptom
A strong ticket helps support reproduce the issue and understand its impact.
Include these details
- The page, project, invoice, or program involved.
- What you expected to happen.
- What actually happened, including the exact message shown.
- The approximate time and device or browser used.
- A screenshot or document when it does not expose sensitive information.
Keep follow-up in one thread
Reply to the existing ticket instead of creating duplicates. This preserves the investigation history and prevents different staff members from repeating the same work.