Guest Column | August 22, 2013

A Checklist For Your Managed Services Portfolio

By Dave Sobel, director of partner community for Level Platforms, an AVG Company

A rich managed services portfolio is a key approach for an MSP to ensure customer loyalty. The more MSPs can monitor and manage, the more vital they become to customers’ operations and the more “sticky” the relationship becomes. Stickiness ensures the MSP is far less likely to be displaced by a competing provider, as the MSP is able to show a considerable distinctiveness from the competitor.

  • To start, an MSP should focus on the basics. Inventory, monitoring, alerting, and asset management are the tenants of a good MSP offering, as this is a basic offering that most small SMBs are unable to manage well on their own.   
  • Everything that can be monitored should be monitored. This includes antivirus, backups, spam systems, email systems, and email flow. Some sophisticated MSPs even monitor customers’ domain names for expiration and to watch to make sure they aren’t placed on a spam black list.  
  • Every device should also be monitored. This includes routers, switches, printers, VoIP phones, firewalls, and the like. If it has an IP address, it should be monitored. Start with up/down status, and move on to service monitoring. Printers can be even more aggressively monitored, monitoring both usage and consumable levels. Those consumables can also prove to be a lucrative stream of revenue as well!

Sign in to read more.

access the Guest Column!

Get unlimited access to:

Trend and Thought Leadership Articles
Case Studies & White Papers
Extensive Product Database
Members-Only Premium Content
Welcome Back! Please Log In to Continue. X

Enter your credentials below to log in. Not yet a member of VAR Insights? Subscribe today.

Subscribe to VAR Insights X
  • The value '20' is not valid for NewsletterUserId.

Please enter your email address and create a password to access the full content, Or log in to your account to continue.

or

Subscribe to VAR Insights
  • The value '20' is not valid for NewsletterUserId.