How to Get Faster Support: Ticket Guidelines
Our goal at Jiinubi is to resolve your issues on the very first reply. To help our engineers identify and fix problems quickly, follow these best practices when submitting a support request.
1. Use a Descriptive Subject Line
Avoid vague subjects like "Help" or "Website broken." Instead, be specific.
- Poor: "Problem with email."
- Better: "Cannot send emails from [email protected] - Error 550."
2. The "What, Where, and When" Rule
A perfect ticket includes three key pieces of information:
- What is happening? Describe the exact error. Copy and paste the error message if possible.
- Where is it happening? Provide the specific URL, domain name, or email address involved.
- When did it start? Mention if the issue started after you made a specific change (like installing a plugin or updating DNS).
If you are seeing a specific error on your screen, use a tool like Lightshot or Snipping Tool to take a screenshot and attach it to the ticket.
3. Steps to Reproduce
If the issue only happens sometimes, tell us how to see it ourselves:
- "I go to mydomain.com/contact."
- "I fill out the form and click Send."
- "The page stays white and nothing happens."
4. One Issue Per Ticket
To keep things organized, please open separate tickets for unrelated issues. For example, keep a billing question separate from a website technical error. This allows the right experts to handle each task simultaneously.
Avoid "bumping" your ticket by replying "Any updates?" before we respond. Our system sorts tickets by the last reply time, so replying to your own ticket moves it to the back of the queue.
Summary
Clear Subject Line
Domain/Service selected
Exact error message included
Screenshots attached (if applicable)
Steps to reproduce described
By following these guidelines, you help the Jiinubi Support Team provide the high-quality, rapid service you deserve.