● Non-Critical Tier

Severity 4: Low

Fundamentally non-urgent, non-break/fix interactions. The system is functioning exactly as designed — but the user requires assistance, clarification, or is providing feedback for future improvements.

SEV 1 SEV 2 SEV 3 SEV 4
Production Impact
Low-to-none
Core operations unaffected
Workaround
Not applicable
No actual break to work around
Communication
Email / Ticket
No phone call required

Properly managing this tier is critical for maintaining profitability, protecting engineering time, and building a better product roadmap. These are not failures — they are education, documentation, and feedback channels.

1

Definition and Scope

Severity 4 encompasses three primary categories of requests.

01

General Usage Questions

“How-to” inquiries.

“How do I configure two-factor authentication for a new user in Nextcloud?” / “What is the command to restart the LibreSign service via systemd?”
02

Documentation Errors

Reporting typos, outdated screenshots, or missing steps in your manuals or knowledge base.

03

Enhancement Requests

Suggestions for new features, UI improvements, or modifications to existing workflows.

“It would be helpful if the backup dashboard showed storage usage in LTC as well as TB.”
2

Business Impact & Workaround Status

Stable in production; a minor delay at most in development.

Production — Impact: Low-to-no impact

Core business operations, revenue generation, and data integrity remain completely unaffected. The software is stable, secure, and performing within expected parameters.

Development — Impact: Medium-to-low impact

A development or staging project might experience a minor delay (e.g., waiting for clarification on an API parameter), but the project is not blocked. The team can continue working on other modules or use a temporary procedural workaround while awaiting a documentation update or future feature release.

Workaround Status: the concept of a “workaround” is not strictly applicable here because there is no actual “break” to work around. The system is behaving as designed. The gap lies in user knowledge, documentation clarity, or product capabilities — not in system failure.

3

Recommended Action & Workflow

Standard portal submission, business-hours handling, batched for efficiency.

1

Intake

Standard online submission via the support portal.

2

Communication

No phone call is required or recommended. Email or ticketing system updates are the appropriate communication channels.

3

Resolution Timing

Handled in the normal course of business during standard working hours. These tickets are often batched (grouped together) for efficiency. For example, a support engineer might dedicate a specific block of time on Tuesday and Thursday afternoons to clear all pending Severity 4 tickets, answer knowledge-base questions, and log feature requests.

4

Strategic Value for Remote Support LLC

Not just about closing tickets — a strategic business function aligned with transparency, predictable pricing, and ethical governance.

🛡️

Protects SLA Margins

The company guarantees 99.9% uptime and offers service credits for failures. If engineers are distracted by Severity 4 requests during off-hours, it increases operational costs and risks burnout — which can indirectly threaten the ability to meet strict Severity 1 and 2 SLA targets. Keeping Sev 4 strictly to business hours protects the bottom line.

🗺️

Feeds the Product Roadmap

Enhancement requests (Sev 4) are a goldmine for product development. By tagging and tracking these requests, you can identify patterns. If five different SME clients request the same Nextcloud integration, it validates a feature that can be added to the roadmap — demonstrating that you listen to your customers.

📚

Drives Content Marketing and Self-Service

A high volume of “how-to” Severity 4 tickets indicates a gap in documentation or onboarding. Resolving these by creating clear, structured guides (or top-rated Linux training materials) reduces future ticket volume, empowers clients, and lowers long-term support costs.

5

Common Pitfalls & How to Manage Them

Inflation at the top, neglect at the bottom.

Severity Inflation Pitfall

Clients often panic and label a “how-to” question as Severity 1 because they are frustrated or unfamiliar with the system.

SolutionImplement a transparent triage process. The technical leadership team should politely but firmly downgrade the ticket to Severity 4, explicitly stating why.
“The system is fully operational, and this is a configuration question. We have downgraded this to Severity 4 and will respond within our standard business-hour timeframe. If the system were actually down, it would remain Severity 1.”
OutcomeThis reinforces the “Trust but Verify” model.

Ignoring Severity 4 Pitfall

Because they are low priority, these tickets can sometimes be neglected, leading to customer frustration over time.

SolutionEstablish a clear, published SLA for Severity 4 (e.g., “Initial response within 2 business days”). This sets accurate expectations and ensures that even low-priority items are systematically addressed.

Closing Principle

By treating Severity 4 not as a nuisance, but as a structured channel for education, documentation improvement, and product feedback, Remote Support LLC can turn routine inquiries into long-term customer loyalty and operational efficiency.