Danger Zone Tier

Severity 2: High

The system is not completely dead — but it is operating so poorly or with such limited functionality that it is actively harming the client’s business.

SEV 1 SEV 2 SEV 3 SEV 4
Business Impact
High
Critical workflows severely impaired
Workaround
None exists
The differentiator from Sev 3
Environment
Production only
Live, paying operations suffering

The absolute defining characteristic of a Severity 2 issue is the total absence of a viable workaround. Because the business cannot bypass the problem, immediate, dedicated engineering intervention is required to prevent a total collapse into a Severity 1 outage.

1

Definition and Scope

The software is technically running, but its functionality is severely degraded, unstable, or limited in a live production environment.

The Nextcloud web interface is accessible, but the underlying database connection pool is exhausted, causing 80% of file sync requests to time out.
The LibreSign e-signature API is experiencing severe latency, making it impossible for an SME’s sales team to execute time-sensitive contracts — even though the server itself has not crashed.
2

Business Impact, Workaround & Environment

The tests that separate Sev 2 from Sev 1 and Sev 3.

📉

Business Impact (Production)

Impact level: High. Significant portions of business operations are negatively affected. Critical workflows are severely impaired. While the entire enterprise may not be at a complete standstill, the degradation is causing measurable financial loss, operational bottlenecks, or compliance risks. The business is bleeding efficiency, if not immediate revenue.

🚫

Workaround Status

None exists. This is the critical differentiator from Severity 3. The client cannot manually upload files, cannot route around the failed service, and cannot use an alternative process to achieve their business goal. The inability to bypass the issue is precisely what elevates it to a Severity 2.

🏭

Environment

Strictly production. Issues in development or staging environments, even if they block a project, are typically classified as Severity 3 because they do not impact live business operations or revenue. A Severity 2 declaration means live, paying operations are actively suffering.

3

Recommended Action & Workflow

A phone call is mandatory — this is non-negotiable.

1

Intake

Immediate online submission to capture logs, error messages, and system state.

2

Communication

A phone call is mandatory immediately following the online submission.

3

Purpose of the Call

To rapidly triage the issue, verbally confirm the exact scope of the degradation, rule out user error, and assure the client that dedicated resources are being allocated. It prevents the delay of asynchronous email ping-pong during a crisis.

4

Strategic Value for Remote Support LLC

Managing Severity 2 effectively is the primary defense mechanism for protecting profitability, reputation, and SLA commitments.

🛡️

Protects the 99.9% Uptime SLA

Severity 2 is the last line of defense before a Severity 1 outage. Rapid, aggressive intervention at the Severity 2 stage is often what prevents a total system failure. Preventing a Sev 1 directly protects you from issuing SLA service credits and maintains your 99.9% uptime guarantee.

🔎

Enforces the “Trust but Verify” Model

When a client declares a Severity 2, the technical leadership team must immediately verify the claim. You must confirm that the degradation is real, that it is in production, and that no workaround actually exists. This objective verification prevents resource drain on exaggerated claims while ensuring legitimate crises get immediate attention.

⏱️

Triggers the 48-Hour Leadership Resolution Clock

The company resolves disputes regarding service quality or billing within 48 hours via the technical leadership team. A Severity 2 issue that is mishandled or allowed to linger is the most common catalyst for these disputes. Swift, transparent action at the Sev 2 level builds the long-term, founder-to-founder trust you value.

5

Operational Workflow & Best Practices

Speed, transparency, and relentless mitigation.

1

Immediate Triage (Minutes, not Hours)

The moment a Severity 2 ticket is logged and the phone call is received, a senior engineer or technical lead must be assigned.

2

Establish a Communication Cadence

Do not go silent while investigating. Provide the client with an initial update within 30–60 minutes (e.g., “We have reproduced the database timeout issue, our lead engineer is actively reviewing the logs, next update in 2 hours”). This transparency reduces client panic.

3

Relentless Pursuit of a Workaround

Even though the client claims no workaround exists, your engineering team should actively look for one. If you can discover a temporary mitigation (e.g., restarting a specific systemd service, throttling bandwidth to stabilize the database), you can immediately downgrade the ticket to Severity 3, relieving the emergency pressure.

4

Post-Mortem Requirement

Every Severity 2 incident must conclude with a brief root-cause analysis. This feeds directly into your automation and infrastructure scaling goals, ensuring the same degradation does not happen twice.

6

Common Pitfalls & How to Manage Them

Inflated claims, missed workarounds, and starved resources.

Severity Inflation (The “Boy Who Cried Wolf”) Pitfall

Clients may label a minor inconvenience as a Severity 2 because they are frustrated.

SolutionThe support team must politely but firmly verify the criteria.
“I understand this is frustrating, but because you can still access your data via the web interface while the desktop client syncs, a workaround exists. We are classifying this as a Severity 3 to ensure it is routed to the correct specialist, and we will have an update for you by tomorrow.”

Workaround Blindness Pitfall

Assuming a workaround doesn’t exist just because the client couldn’t find one.

SolutionEmpower your support engineers to think creatively. Often, a simple configuration tweak or temporary resource reallocation can serve as a bridge until a permanent code fix is deployed.

Resource Starvation Pitfall

Allowing Severity 2 tickets to sit in a queue behind other work.

SolutionImplement strict ticketing automation. A Severity 2 tag should instantly trigger SMS or pager alerts to the on-call technical leadership team, bypassing standard queue routing.

Closing Principle

By treating Severity 2 with the urgency it demands, while maintaining strict, objective verification of its criteria, Remote Support LLC demonstrates technical competence, protects its SLA margins, and solidifies its reputation as a reliable, reality-focused partner for SMEs.