Back to General FAQ

Internal documentation only

This page has been marked as draft.

🀝 Working with ITRS Product Support

At ITRS, our goal is simple: keep your monitoring stable, performant, and your business-critical systems running smoothly.

Here’s what you can expect when working with us - who can access support, what we cover, and how we collaborate with you.


πŸ‘₯ Who Can Access ITRS Support? Copied

Support is available to all clients with an active maintenance or subscription agreement.

To ensure security and compliance:

Once registered, users can:

πŸ” Any internal restrictions around downloads or deployments remain the responsibility of the client organisation.


πŸš€ What Level of Support Can You Expect? Copied

ITRS operates a structured Level 1 β†’ Level 2 technical support model.

πŸ₯‡ Level 1 Support Copied

Your first point of contact:

πŸ₯ˆ Level 2 Support Copied

Escalated cases are handled by experienced product specialists with deeper technical expertise.

As investigations progress, tickets may move between engineers to ensure the right skill set is applied at the right time.

Our approach is collaborative, transparent, and focused on resolution.


🧠 What Does ITRS Support Cover? Copied

We support all queries relating directly to ITRS products and services, including:

βœ” Installation guidance βœ” Assistance setting up new monitoring βœ” Advice on configuration changes βœ” Performance tuning and best practice βœ” Enhancement requests βœ” Investigation of suspected defects βœ” Documentation clarification and improvement suggestions

We expect users to have a working level of technical knowledge of:

This helps us work efficiently together and accelerate resolution.


🚫 What Falls Outside Our Scope? Copied

To keep our service focused and effective, certain areas fall outside standard support scope:

❌ Troubleshooting non-ITRS software (operating systems, third-party tools, custom scripts) ❌ Hardware support ❌ Third-party components (we will typically refer you to the relevant vendor) ❌ Large-scale reconfiguration or greenfield deployments (normally handled by Professional Services) ❌ Custom client-written code or scripts ❌ Scripts provided under the ITRS MIT license ❌ Product usage outside documented standards

While many of our engineers have broad technical expertise (sysadmins, DBAs, market data specialists, dashboard experts), our primary responsibility is supporting ITRS products.

That said, where appropriate and capacity allows, we may offer guidance on a best endeavours basis to help you progress, particularly where an issue interacts with ITRS software. Any such assistance is advisory and remains outside the formal scope of product support.


πŸ”„ How Tickets Progress Copied

Once raised, your ticket enters a structured workflow:

  1. 🎫 Case created
  2. πŸ’¬ Ongoing discussion and investigation
  3. πŸ›  Resolution or conversion to a development change request

🀝 Working with ITRS Product Support

⏳ Automatic Closure Policy Copied

If we request information and receive no response for two weeks, the ticket will automatically close after reminder notifications.

Duplicate tickets may be cancelled to maintain clarity and efficiency.


βš– How We Classify Severity Copied

Cases are prioritised based on business impact, using the following model:

Severity Definition / Conditions
πŸ”΄ Severity 1 - Severely Impacted - A key PRODUCTION component is down or repeatedly failing - Organisation-wide or multi-team impact - No workaround available - A dedicated technical contact must be available throughout the incident
🟠 Severity 2 - Limited Capabilities - Production system disrupted but partially operational - Degraded or unstable component - Workaround available
🟑 Severity 3 - Minor Issue - Limited to a single component or user - Monitoring capability largely unaffected - Includes UAT/DEV issues - Workaround available
πŸ”΅ Severity 4 - General Enquiry - Clarification requests - β€œHow-to” guidance - Documentation questions - Product information queries - Feature Requests

Our engineers may adjust severity based on the information provided. If you believe the severity should change, simply provide business justification and we’ll reassess.


🧩 Change Requests & Enhancements Copied

For enhancement requests:

These updates generate informational tickets that close automatically.

For confirmed bugs:


πŸ†• Onboarding New Clients Copied

When a new client is activated:

This ensures a seamless transition into supported status.


πŸ’¬ How We Work With You Copied

We aim to be flexible and practical in our collaboration:

βœ” Ticket-based investigations βœ” Guided troubleshooting βœ” Remote screen-sharing sessions (when appropriate) βœ” Clear written communication and structured updates

For complex or urgent issues, remote sessions may be scheduled at the discretion of our technical team.


πŸ“š Self-Service Resources Copied

In addition to direct support, clients have access to:

We encourage customers to make full use of these resources to accelerate troubleshooting and learning.


πŸ“Š We Act on Your Feedback Copied

After ticket closure, you’ll receive a short feedback survey.

We genuinely use this input to improve our service. Past improvements driven by customer feedback include:

Your feedback directly shapes our service evolution.


🎯 Our Commitment Copied

We are committed to:

ITRS Support exists to protect your operational resilience β€” and we take that responsibility seriously.

["Geneos"] ["FAQ"]

Was this topic helpful?