Have you ever opened up a product with ‘some assembly required’ that failed to include instructions (or included them, but only in a language you don’t understand)? So frustrating. Sadly, many clients feel the same way about their managed services agreements.
And that’s not good for your profit potential in this practice area your business.
As an IT solution provider, you want to build a relationship and position yourself as a trusted advisor. Make agreement terms clear and concise—no confusing jargon. The better your agreement, the more you and your clients benefit.
6 Things You Gain from Managed Services Agreements
Developing a managed services agreement (MSA) is often the first thing that a technology solution provider (TSP) does to prepare for delivering services to a prospective client. It helps you:
- Identify what hardware, users, vendors and services are covered, as well as those that aren’t
- Clearly document the managed service roles and responsibilities for the client and the TSP
- Accurately represent the clients’ existing environments
- Define environmental prerequisites for service
- Establish a baseline environment
- Create a framework to ensure profitability
What to Include in a Managed Services Agreement
The agreement should embody your service level agreement (SLA), prioritization process, response times, termination clause, limitation of liability and a definition of support tiers and your service desk escalation process. Plus, it should reflect your labor rates or fees for requested services that fall outside of flat-fee support. Here are the top 11 things you should clearly outline in your managed services agreements:
1. Services. Brass tacks, what is your client getting? Managed email security, telecommunications, just network security? Clearly explain what’s included in their offering (and examples of what’s not).
2. Responsibilities. If Johnny Receptionist pulls an Office Space on his boss’s printer, that shouldn’t be your responsibility to fix. Willful destruction of property shouldn’t be covered, but general wear and tear should be. Define what each looks like in your agreement.
3. Availability. Be realistic here. What can you actually provide? Less than 2 hours of downtime per month? Think about what your clients are averaging today when you set this expectation.
4. Performance. You can have 99.999% uptime, but if the machines are slow as mud, it doesn’t mean much. For contracts that pertain to hardware-as-a-service, ISPs, operating systems and bandwidth-heavy add-ons, set performance expectations.
5. Response. In a nutshell, how quickly can a customer expect to hear back from you after reporting an issue? Be sure to factor in your hours of operation. If you commit to responding to all requests within 10 hours, be sure to define those as business hours.
6. Priories. Define what constitutes a priority or work stoppage. Just because a printer is jammed doesn’t mean your tech should drop everything they’re doing to go fix it.
7. Guarantees. These can help convert an uncertain prospect into a customer, but make sure you can absolutely follow through on whatever you promise to deliver.
8. Serviceablity. If your client’s data center is underwater, you’re most likely going to be unable to provide on-site service. Set expectations around what you classify as serviceable.
9. Operation. Define your support and escalation procedures, as well as your policy for providing service outside normal coverage hours.
10. Resolution. Response and resolution are two completely different matters. While you may respond immediately, it’s not always possible to resolve issues right away. Define reasonable resolution windows you can commit to.
11. System Requirements. Document the minimum standards the environment must meet in order to qualify for services.
While this list scratches the surface of what to include in a managed services agreement, it provides a strong foundation for MSAs that satisfy clients and build your business.
Ensure client satisfaction with expert advice and tools for all aspects of IT service.