How MSPs Can Design Support Tiers Based on Client Criticality

As MSPs, you should know that not all clients vary greatly in how critical their IT environments are. Applying a one-size-fits-all approach to IT support tiers often results in overserving low-risk clients and undeserving mission-critical ones, leading to wasted resources and client dissatisfaction. Crafting tiered coverage enables MSPs to tailor service levels more effectively and sustainably.

Since monitoring tools like NinjaOne give MSPs powerful monitoring, alerting, and management capabilities, MSPs can use them to enhance support tier creation. They can incorporate monitoring tools with other tasks that curate segment support based on client risk or importance. This guide will show you how to build a clear, scalable tier-based support model grounded in client criticality.

At a glance

Prerequisites for designing support tiers

Before proceeding with designing support tiers based on client criticality, make sure you meet the following requirements:

• Agreement on client criticality tiers: Everyone in your team should know what each criticality tier denotes (for example, Tier 1—Platinum, Tier 2—Gold, Tier 3—Silver).
• Business impact criteria: A solid definition of what makes a client more critical must be established. This may include criteria such as uptime importance, regulatory/compliance risk, revenue dependency, and more.
• Defined SLAs or response metrics per tier: This helps set clients’ expectations when it comes to response time, resolution time, escalation path, etc.
• Monitoring tools: A robust remote monitoring and management (RMM) tool like NinjaOne can align alert thresholds and must support different severities, response triggers, and escalation paths.
• Quarterly service reviews: This regular process should be in place to reassess tier alignment that can be influenced by whether clients are in the correct tiers, whether SLAs are being met, and adjust resources as needed.

Task 1: Define clear client criticality levels

📌 Use Case:

Establishing a solid client criticality level dynamic aligns tone and language with business outcomes, reducing ambiguity.

Below are recommended criticality tiers and how you can define each of them:

Task 2: Map support components per tier

📌 Use Case:

Aligning support components ensures that the most skilled personnel are properly allocated and resources are distributed where client risk is highest, while offering adequate service to less critical clients.

Once levels are defined, map specific support components to each tier so clients and your team always know what’s included. Key support aspects include the following:

Task 3: Assign tiers using risk assessment

📌 Use Case:

A decision matrix that scores specific criteria helps assign clients to tiers consistently and fairly.

You can assign scores to the following components in a decision matrix to determine the appropriate tier for each client:

• Dependency: Determines how much of a client’s operations rely on the IT system
• Revenue: Involves revenue data that is at stake in instances of system downtime
• Compliance risk: Describes any regulatory repercussions or reputational risks associated if systems go down or a security failure happens
• Operational impact: How broadly an outage or issue would affect business functions (e.g., just a few users vs the entire organization)

Task 4: Automate tier-aware response mechanisms

📌 Use Case:

Automatically escalate Platinum-tier alerts to higher expertise to ensure timely and appropriate handling.

You can use monitoring tools like NinjaOne to automate tier-aware responses. Here’s an example:

if ($tier -eq "Platinum" -and $alert.Severity -eq "Critical") {

Send-MailMessage -To "[email protected]"

}

• if ($tier -eq "Platinum" -and $alert.Severity -eq "Critical") checks two conditions, of which both must be true for the next step to commence. It confirms:
  • The client’s tier is Platinum.
  • The alert severity is Critical.
• Send-MailMessage -To "[email protected]" sends an email notification to the Level 2 support team’s inbox. In practice, you’d also specify the following parameters to make the email usable:
  • Subject
  • Body
  • SMTP server

💡 Tip: Automatically escalate Platinum-tier alerts to higher expertise to ensure timely and appropriate handling.

Task 5: Review and adapt tiers quarterly

📌 Use Case:

Tier assessment in this cadence can ensure alignment with the client’s current realities while maintaining both fairness and profitability.

Monitor Service-Level Agreements (SLA) compliance, incident volume, and business developments each quarter. Use insights to:

• Adjust client tiers: Factors such as a business’s level of dependency on the IT system may change over time. This improvement may impact your client’s tier position.
• Refine SLA definitions: Reassess if your SLAs still reflect client expectations and operational demands.
• Reallocate resources when needed: Check if resource reallocation is necessary for particular scenarios. Perhaps the Platinum tier needs more support hours, or the Gold tier is spending more than enough on features it doesn’t use.

Task 6: Clearly communicate tier benefits

📌 Use Case:

This ensures both you and your clients share a clear understanding of what comprises each tier.

Here’s how you should break down the services, response times, and support levels included in each tier to your clients for accurate expectations:

1. Produce a digestible and well-explained one-page overview of tiers to distribute to clients.
2. Ensure that you highlight response times, availability, and monitoring frequency so they know the exact parameters of each operation.
3. Present clear escalation protocols so clients know the issue resolution process, who will be involved, and when escalation will occur.

Automation touchpoint example

Here’s a practical sample workflow where automation is used to design support tiers.

• Evaluate client criticality and assign tier: A decision matrix should help determine which support tier a client belongs to.
• Configure monitoring thresholds and alert paths per tier: In a monitoring tool (like NInjaOne), thresholds and escalation routes can be adjusted based on tier.
• Automate responses based on alert severity and tier: Utilize scripts or policies that can automate notification of the right support team, alert escalation, or ticket creation in the integrated PSA.
• Track and report SLA performance per tier: Leverage dashboards that showcase how well you’re meeting SLA commitments across tiers, helping you proactively spot gaps.
• Review and reassign tiers during quarterly business reviews: Consider collected data when deciding whether a client needs to be moved to another tier.

NinjaOne integration for designing support tiers for clients

NinjaoOne and its tools can help with different tasks involved in designing support tiers based on client criticality.

Final thoughts on building support tiers for clients

A streamlined support helps build trust and brings client satisfaction. To establish this, designing support tiers based on client criticality is essential. This helps MSPs deliver precision service without unnecessary complexity. However, one of the first considerations you have to understand is clearly communicating the advantages of each support tier to your clients. Meanwhile, here are some key tasks you should accomplish:

• Define 3-tier criticality levels (e.g., Platinum, Gold, Silver) based on business risk.
• Map support components (SLA, escalation, monitoring) per tier for clarity.
• Assign clients consistently using a documented risk assessment model.
• Automate responses and alerting to reflect assigned tier coverage.
• Review tiers quarterly based on incident volume and SLA trends.
• Communicate tier benefits with clients using simple one-pagers to reinforce value.

Doing these sets accurate expectations when it comes to response times, availability, monitoring frequency, and escalation protocols. You can also incorporate a robust monitoring tool like NinjaOne, especially its automation features, to streamline support tier curation.

Related topics:

• IT Automation – Everything You Need to Know
• 10 IT Help Desk Best Practices for IT Professionals
• What is an MSP Service Level Agreement (SLA)?