Knowledgebase

Writing a Ticket That Gets Resolved Quickly Print

  • clientportal, client, errors, troubleshooting, domain, cpanel, htaccess, permalinks, plugins
  • 0

The difference between a fast answer and three days of back-and-forth is usually the first message.

A WEAK TICKET

"My site is not working. Please fix."

This tells us nothing. The reply will be a list of questions, and a day passes before any diagnosis begins.

A STRONG TICKET

"Domain: example.com. Since roughly 14:30 today, every page returns a 500 error. cPanel loads fine. The error log shows the exact text below. It started after I updated three plugins. I have renamed .htaccess and re-saved permalinks, which did not help. A test.html file loads normally."

That can be diagnosed immediately.

THE ELEMENTS

Which domain or account What is happening, in specific terms When it started Exact error text, copied not described What changed recently What you already tried and what happened

ON URGENCY

Say plainly if a business is offline or a deadline is involved. It is taken into account. Marking everything urgent has the opposite effect.

ON TONE

Frustration is understandable. A clear description gets you a fix faster than a strong one does.


Was this answer helpful?
Back

Are you happy with your experience? Leave us a review on Trustpilot.


Trustpilot