Skip to content
B.I.T. Datentechnik
Support Improve my IT

NEWS & INSIGHTS

A useful support request: Five details that help assessment

Tips & practice · 26.10.2026 · about 2 min

Describe what you observed

A useful request begins with the difference between expectation and observation. Instead of saying only that something does not work, describe the specific action: a file will not open, sign-in is rejected or a print job remains in the queue. Include the application or device involved. You do not need technical terminology to explain a problem clearly. What matters is that another person can understand what you wanted to do and the point at which it failed.

Add timing and scope

State roughly when the issue started and whether it happens continuously or occasionally. It also helps to know whether only your workstation or several people are affected. If the behaviour repeats in a particular place or after a particular step, include that observation. Separate facts from guesses. Saying that three people see the same error is more dependable than immediately concluding that the entire server has failed. Mention whether other applications are still working normally.

Explain previous steps and enable follow-up

Briefly describe what you have already tried and the result. An existing ticket number helps bring related information together. Provide a suitable contact route and your availability without assuming a particular response time. If a screenshot is needed, check it first for confidential customer information or personal material. Passwords, secret keys and complete access credentials do not belong in an ordinary support message or screenshot. Share sensitive diagnostic details only through the agreed appropriate channel.

Coordinate further changes

After reporting the issue, avoid making extensive changes to settings while the cause is still being investigated. Report new observations and significant changes in the symptoms instead. If work becomes possible again, that information is useful too. A good request makes the scope and impact visible; it does not replace a technical diagnosis. With a clear description, timing, affected people, previous steps and a contact route, you provide a practical foundation for investigating the specific problem and agreeing what should happen next.