The Problem with High-Severity Outages
When a major incident hits a client environment, the last thing an engineer needs is someone else inadvertently interfering with the recovery process. In an MSP environment, Tier 1 support staff often work through ticket queues unaware that a specific server or application is currently the subject of an emergency response. This results in unnecessary RDP sessions, configuration changes, or accidental restarts that complicate the troubleshooting process.
Communication during a crisis often fails because standard ticketing workflows are designed for routine requests, not for broadcasting state-of-emergency warnings. Relying on chat channels or internal email often fails to reach everyone in time. If a technician is already deep in a console session, they are not checking notifications. You need a way to make the incident status visible within the very interface they are using to access client credentials and configuration data.
The Major Incident Feature
OpsLens includes a dedicated Major Incident feature designed specifically to address this communication gap. When a senior engineer identifies a critical failure, they can trigger a Major Incident status directly on the customer page. This does not just send a ping; it changes the visual state of the client page across the entire platform.
When a Major Incident is active, the interface alerts all engineers accessing that client's documentation. The UI shifts, the page branding turns red, and a prominent banner appears. This serves as a immediate, unavoidable visual indicator that a high-priority event is underway. Any engineer—regardless of their seniority level—will immediately see that the environment is locked or restricted for emergency recovery.
Preventing Overlapping Work
By forcing this visual change, you prevent Tier 1 or other staff from performing routine maintenance or troubleshooting on the affected system. The red alert acts as a standard 'stop work' signal for that specific client. It removes the need for follow-up emails, channel alerts, or individual pings to keep the rest of the team informed. If an engineer opens the client page, they are already informed of the situation.
This is about minimizing the cognitive load during a crisis. You should not have to manually coordinate with every member of the team while trying to restore services. If your documentation tool is the centralized point for accessing client environments, it must also be the point of communication for the current status of that environment.
Implementation within Your Workflow
To handle major incidents effectively, you need a process that is as fast as the incident itself. The feature in OpsLens is designed to be toggled with a single action. There are no forms to fill out, no complex ticketing flows, and no waiting for administrative approval.
- Identify the incident: Confirm the client impact is severe enough to warrant a 'Major Incident' status.
- Trigger the status: Select the Major Incident toggle on the client's landing page in OpsLens.
- Communicate visibility: Every team member logged into the system will immediately see the red alert status upon accessing that client's information.
- Resolve and Clear: Once the incident is mitigated, toggle the status off to return the documentation to its standard state.
Access and Pricing
We keep our platform accessible to ensure all MSPs can maintain order during critical outages. The OpsLens Solo plan is free for a single engineer, providing full access to all features, including the Major Incident tracking. For growing teams, our Team and MSP plans are available on a per-license basis. We do not believe in gating crisis management behind complex enterprise tiers. Whether you are a solo consultant or managing a multi-engineer firm, you need the same baseline operational intelligence to prevent unnecessary downtime.