I couldn't log into my personal account on the server

[nusaibatara]

Clear and concise content of the letter in the subject is 70% for the formation of the fastest response. Meaningless words, such as: "Help", "Error", "There was a problem", etc. are not acceptable, since they do not specify the facts. Instead, you should use topics like "Unable to create an account in AD", "Table parts in the write-off section are not filled in", "Issuing an invoice SF-1234567890", etc. For clarity, provide an example of comparison or a sample request on the request page: Request #1 : "Hello, technical support for the program I use to automate my IT department.



I haven't used my favorite program for a long venezuela phone number list time, and today, when I turned on the computer, I was shocked - it didn't turn on. I began to suspect that technical work on the server was the reason why the site didn't want to load. - the password is incorrect. Help me quickly, please!" Request #2 : "Hello! 1. On the softonit.ru website, the page "softonit.ru/FAQ/" does not load - error 500 Server Error 2. I connected to the site li ond request is devoid of "water" - after reading it, you can immediately start diagnosing the server, but the first one requires an understanding of what is being discussed, then diagnostics.



Finding out additional information will take time, and therefore the answer will not be quick. Provide as much detail as possible details A sufficient number of useful additional materials speeds up the localization of the problem and further elimination of the cause several times. Thus, providing help "About the program", where information about the product edition is indicated, will be the starting point for the developer in the support process. Screenshots and videos eliminate the need to "play ping-pong" like a question and answer and clearly show what is seen on the screen through the eyes of the client.