Tips: How to write a proper technical request Print

  • 0

A well-structured ticket reduces resolution time by up to 70%.

✔️ Include:

  • What you are trying to do
  • What is happening instead
  • When the problem started
  • URL related to the issue
  • Relevant service (shared, reseller, VPS, etc.)
  • Screenshots or logs
  • If you changed anything before the error occurred

✔️ Examples of good descriptions:

"The site example.com has been returning a 500 error since last night. No changes were made to the code. I am attaching an error log from my WordPress website debug log."

"Emails from the domain mydomain.gr are not being delivered to outlook.com. I am attaching a bounce message."

What to avoid:

  • "Nothing is working."
  • "Fix it urgently."
  • No information or blurry/cropped screenshots.

Was this answer helpful?

« Back