Good evidence helps AvrinTech reproduce a problem and choose the right next step. You do not need to diagnose the cause yourself; a clear description of what you expected and what actually happened is more useful than a guess.
Describe the problem in a repeatable way
- Name the service or application and the device you are using.
- Describe the action that triggers the problem, such as opening a page, submitting a form, or sending a message.
- Quote the exact error text and include the time and time zone.
- Explain whether it happens every time and whether colleagues or other devices are affected.
Include any recent change, such as an update, new device, account change, or hosting migration. State which checks you already tried and their results.
Capture enough context
A screenshot should show the relevant application or page, the complete error, and the surrounding controls needed to understand it. Very tight crops can hide which account, page, or action is involved.
If a problem involves an address or link, include the non-sensitive page location. Sign-in callbacks, password-reset links, and session-bearing URLs can contain secrets; do not paste those complete URLs into a ticket.
Protect unrelated information
Remove passwords, MFA codes, payment information, and unrelated customer or employee details before attaching a screenshot. Use a solid redaction rather than a light blur. If the evidence itself contains sensitive material, ask us how to provide it through an approved method.
Do not attach an entire mailbox export or device log collection when a specific error is sufficient. We can request additional evidence if needed.
Keep the investigation together
Reply to the existing ticket when adding screenshots, timestamps, or test results for the same issue. Label attachments so we know which device or step they show.
Finish with the business impact and any deadline: for example, one user cannot open a file, several users cannot sign in, or customers cannot complete a website form.
