How to Write an Effective Support Request

When you encounter an issue with Server Scout, a well-written support ticket can make the difference between a quick resolution and a lengthy back-and-forth exchange. Our AI support bot responds within approximately one minute, and if escalation to human support is needed, our team reviews tickets within 24 hours on business days. Here's how to craft an effective support request that gets results.

Use a Clear, Specific Subject Line

Your subject line is the first thing our support team sees, so make it count. Instead of vague titles like "Help needed" or "Problem with server," be specific about what's happening and where.

Good examples:

  • "Agent not reporting data on web-server-03"
  • "Disk usage alerts triggering incorrectly on database server"
  • "Cannot add new server - getting authentication error"

Poor examples:

  • "Urgent help needed"
  • "Server Scout not working"
  • "Question about monitoring"

Include Essential Details in Your Description

Paint a complete picture of the issue by covering these key points:

  • What you expected to happen - "I expected the agent to report CPU metrics every 5 seconds"
  • What actually happened - "No data has been received for the past 2 hours"
  • When the issue started - "The problem began at approximately 14:30 GMT today"
  • Any error messages - Include the exact text of any errors you've seen

Link a Server to Your Ticket

This is one of the most helpful things you can do. When you link a server to your support ticket, our team gains access to:

  • Your server's current metrics and historical data
  • Recent alerts and notifications
  • Agent status and connection logs
  • Configuration details

This information allows us to start investigating immediately rather than asking for basic diagnostic information.

Provide Steps to Reproduce

If your issue is reproducible, list the exact steps you took:

  1. Navigate to the Servers page
  2. Click "Add Server"
  3. Enter server details (IP: 192.168.1.100, name: web-server-04)
  4. Click "Generate Installation Script"
  5. Error message appears: "Failed to generate script"

This helps our team recreate the issue in our test environment if needed.

Mention What You've Already Tried

Save time by telling us what troubleshooting steps you've already attempted:

  • "I've restarted the Server Scout agent using sudo systemctl restart serverscout"
  • "I checked the firewall settings and confirmed port 443 is open outbound"
  • "I reviewed the agent logs at /var/log/serverscout/agent.log but saw no obvious errors"

This prevents us from suggesting solutions you've already attempted and helps us move to more advanced troubleshooting.

Specify the Impact

Help us understand the urgency by explaining how the issue affects you:

  • "This is affecting our production web servers and we cannot monitor uptime"
  • "The issue affects 3 out of 12 servers, but they're all development machines"
  • "I'm evaluating Server Scout for my organisation and this is blocking my assessment"

Choose the Right Priority Level

Select the appropriate priority to help us triage effectively:

  • Low priority: General questions, feature requests, non-urgent issues
  • Medium priority: Issues affecting monitoring functionality but not critical systems
  • High priority: Problems impacting production server monitoring or preventing you from using Server Scout entirely

Attach Screenshots When Relevant

Visual information can be incredibly helpful. The ticket form supports file attachments, so include screenshots of:

  • Error messages or unexpected behaviour
  • Configuration screens showing your settings
  • Graphs or charts that aren't displaying correctly
  • Browser console errors (press F12 and check the Console tab)

The Result: Faster Resolution

Well-crafted tickets allow our support team to begin investigating immediately rather than spending time gathering basic information. This means faster resolution times and less frustration for everyone involved.

Remember, our AI support bot is available 24/7 and responds within approximately one minute with relevant knowledge base articles and troubleshooting steps. For issues requiring human attention, our team provides follow-up within 24 hours during business days (Monday to Friday, Irish timezone).

Taking a few extra minutes to write a comprehensive support request will save time for both you and our support team, leading to quicker resolution of your Server Scout issues.

Frequently Asked Questions

How long does ServerScout support take to respond to tickets?

ServerScout's AI support bot responds within approximately one minute with relevant knowledge base articles and troubleshooting steps. If escalation to human support is needed, the team reviews tickets within 24 hours on business days (Monday to Friday, Irish timezone).

What should I include in my support ticket subject line?

Use a clear, specific subject line that describes what's happening and where. Good examples include 'Agent not reporting data on web-server-03' or 'Cannot add new server - getting authentication error'. Avoid vague titles like 'Help needed' or 'Server Scout not working'.

How does linking a server to my support ticket help?

When you link a server to your support ticket, the team gains access to your server's current metrics and historical data, recent alerts and notifications, agent status and connection logs, and configuration details. This allows them to start investigating immediately rather than asking for basic diagnostic information.

What essential details should I include in my support request?

Include what you expected to happen, what actually happened, when the issue started, and any exact error messages. Also mention what troubleshooting steps you've already tried and explain how the issue impacts your operations to help with prioritization.

Should I include screenshots with my support ticket?

Yes, visual information can be incredibly helpful. The ticket form supports file attachments, so include screenshots of error messages, configuration screens, graphs that aren't displaying correctly, or browser console errors (press F12 and check the Console tab).

How do I choose the right priority level for my support ticket?

Use low priority for general questions and non-urgent issues, medium priority for issues affecting monitoring functionality but not critical systems, and high priority for problems impacting production server monitoring or preventing you from using ServerScout entirely.

What if my ServerScout issue is reproducible?

List the exact steps you took to encounter the issue, such as which pages you navigated to, what buttons you clicked, and what data you entered. This helps the support team recreate the issue in their test environment if needed for troubleshooting.

Was this article helpful?