● Degraded but Functional Tier

Severity 3: Medium

The system is not completely down, but it is not operating at 100% capacity. A viable procedural workaround exists — so the business can continue to operate, even if less efficiently.

SEV 1 SEV 2 SEV 3 SEV 4
Production Impact
Medium-to-low
Business continues to function
Workaround
Viable & in use
Documented procedural alternative
Environment
Production / Dev
Dev blockers = high project impact

The defining characteristic of a Severity 3 issue in a production environment is the existence of a viable procedural workaround. Because the business can continue to operate — even if less efficiently — it does not trigger the emergency response protocols of Severity 1 or 2.

1

Definition and Scope

A partial loss of functionality that does not halt immediate, day-to-day operations.

A specific department’s Nextcloud desktop client is failing to sync automatically, but users can still manually upload/download files via the web interface.
A LibreSign e-signature workflow is failing for a specific document type, but the client can temporarily revert to a manual PDF export and external signing process.
2

Business Impact & Workaround Status

The critical distinction between production and development environments.

Production — Impact: Medium-to-low

The business continues to function. Revenue is not actively bleeding, and core data is not lost. However, there is a measurable loss of efficiency, increased manual labor, or minor user frustration. The key factor is that staff are actively using a procedural workaround to keep the business moving.

Development / Staging — Impact: High for that project

This is a critical distinction. In a development or staging environment, a “workaround” is often not acceptable because the goal is to test the system exactly as it will run in production. If a bug prevents a new Nextcloud app integration from being tested or blocks a staging environment from migrating to production, that specific initiative is completely stalled. It is a “showstopper” for the project, even though the live business is unaffected.

✅

Workaround Status — Production

A documented, temporary, or alternative process exists and is being utilized.

🧪

Workaround Status — Development

A workaround may exist, but it defeats the purpose of the testing phase — hence the higher relative impact on the project timeline.

3

Recommended Action & Workflow

Email and ticketing are sufficient — a phone call would divert critical engineering resources from actual emergencies.

1

Intake

Standard online submission via the support portal.

2

Communication

Email or ticketing system updates are sufficient. A phone call is not required or recommended, as it diverts critical engineering resources from actual emergencies.

3

Escalation Trigger

A phone call is only warranted if the workaround fails (e.g., the web interface also goes down), at which point the ticket must be immediately escalated to Severity 2 or 1.

4

Strategic Value for Remote Support LLC

Managing Severity 3 effectively is a cornerstone of the “Trust but Verify” model and the commitment to predictable, transparent pricing without hidden fees.

📊

Protects SLA Margins and Profitability

The company guarantees 99.9% uptime. Severity 3 issues, by definition, do not breach this uptime guarantee if the core service remains accessible via a workaround. By keeping these tickets out of the emergency escalation queue, you protect the technical leadership team’s time — ensuring they are available to resolve actual Severity 1/2 disputes within the promised 48-hour window.

🔎

Enforces Objective Triage (Trust but Verify)

Clients may panic and label a Severity 3 issue as a Severity 1. The support team must verify the claim. If a workaround exists and is functional, the ticket is objectively a Severity 3. Communicating this transparently (“We have verified the core system is up, and the web interface workaround is functional, so this is classified as Severity 3”) builds trust and sets realistic expectations.

📈

Identifies Systemic Weaknesses

A spike in Severity 3 tickets around a specific feature (e.g., backup bandwidth throttling or a specific Linux systemd integration) is an early warning sign. It indicates that a feature is fragile or poorly documented — allowing your team to proactively fix it before it degrades into a Severity 1 outage.

5

Operational Workflow & Best Practices

Managed, documented, and routed to the right engineer.

1

Acknowledge and Validate

Respond within your standard business-hour SLA (e.g., 4–8 hours). Acknowledge the issue and explicitly confirm the workaround the client is using.

2

Document the Workaround

Ensure the workaround is clearly documented in the ticket. This serves as proof that business operations are not halted, protecting you from unwarranted SLA service credit claims.

3

Assign Appropriately

Route these tickets to mid-level support engineers or specialized developers, rather than your top-tier emergency responders.

4

Provide a Clear Timeline

Give the client a realistic estimate for a permanent fix. For example: “Our development team has reproduced the issue in staging and a patch is scheduled for the next maintenance window on Thursday.”

6

Common Pitfalls & How to Manage Them

Workaround fatigue and misclassified development blockers.

Workaround Fatigue Pitfall

A workaround might be fine for a day, but if a Severity 3 issue drags on for weeks, the “medium-to-low” impact compounds into severe user frustration and lost productivity.

SolutionImplement an automatic aging rule. If a Severity 3 ticket remains open for more than a predefined period (e.g., 5 business days), it should trigger an internal review by your technical leadership team to prioritize a permanent fix — or offer a temporary service credit as a gesture of goodwill, reinforcing your ethical governance.

Misclassification of Development Blockers Pitfall

Support teams sometimes treat a development blocker as “low priority” because it doesn’t affect production.

SolutionTrain support staff to recognize that “High impact to a specific project” in a development environment requires dedicated, focused attention to unblock the client’s roadmap — even if it doesn’t warrant a 3:00 AM phone call.

Closing Principle

By treating Severity 3 as a managed, transparent process rather than an afterthought, Remote Support LLC demonstrates reliability, protects its SLA commitments, and maintains the high standards expected by SMEs seeking data sovereignty and private cloud solutions.