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:
- Requests must come from a registered corporate email address
- The email domain must match the one registered in your support agreement
Once registered, users can:
- Raise and track tickets
- Respond to support updates
- Access documentation and software downloads
π 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:
- Triage and issue validation
- Initial technical investigation
- Guidance and troubleshooting
- Resolution where possible
π₯ 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:
- The operating systems hosting ITRS software
- The relevant ITRS product(s)
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:
- π« Case created
- π¬ Ongoing discussion and investigation
- π Resolution or conversion to a development change request
β³ 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:
-
Once logged and accepted, the support ticket is marked Solved
-
The internal development request continues in our backlog
-
Youβll receive update notifications when:
- It enters development
- It becomes available in a release
These updates generate informational tickets that close automatically.
For confirmed bugs:
- The original ticket remains open until resolution status is Fixed or Will Not Fix
π Onboarding New Clients Copied
When a new client is activated:
- Their organisationβs email domain is registered in our support systems
- Access is enabled for support services, training, documentation, and downloads
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:
- Software downloads
- Technical reference guides
- Release notes
- Compatibility matrices
- FAQ content
- Free online training materials
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:
- Launching and expanding our FAQ site
- Extending support hours in high-demand regions
- Introducing Gateway Diagnostics to accelerate issue detection
- Adding user-intent metrics to identify documentation gaps
Your feedback directly shapes our service evolution.
π― Our Commitment Copied
We are committed to:
- Clear communication
- Fast engagement
- Practical solutions
- Continuous improvement
ITRS Support exists to protect your operational resilience β and we take that responsibility seriously.