When you’re the owner of an MSP, you might have an inbox that’s full of all sorts of random messages from your clients and staff every day. On one hand, your phone is ringing constantly, and on the other, your chat notifications are firing off. 

It can be absolute chaos!

Directions, guide to best communication policy

To save time, and above all, sanity, you need to put in place an ironclad MSP communication policy. As MSP staffing specialists, we here at Support Adventure have seen that the companies who flourish and scale faster are those who have taken this critical step. Their minds are set at ease by eliminating the constant unnecessary pinging and ringing. 

But how can you do that without losing track of what’s happening in your company? Here’s our comprehensive guide to establishing a formidable MSP communication policy!


MSPs often grow into large organizations without having put in place a communication policy. This creates a disorganized environment which can spell disaster for your business.

Systematized communication guidelines help you prioritize what is and isn’t urgent. They differentiate between the top issues that need to get in front of the right people immediately, and the non-urgent issues that can be visited later in a meeting. 

There are many ways to communicate in an MSP environment, but the core should always be the ticketing system. Each ticket keeps a record of events that happened regarding internal and external communication.

If your staff are not using the ticketing system to record such events, then misunderstandings are bound to happen. This leads to client complaints as responsibilities and troubleshooting steps end up getting lost. 

It will then be very difficult to figure out the best course of action to take in each particular case, resulting in an enormous loss of time and energy. This directly affects your clients and can break trust, causing them to stop working with you. 

So why not take the time to create a communication policy? It will only benefit you in the long run as it will:

  • Prevent information from getting lost.
  • Categorize issues according to urgency.
  • Establish ownership-based accountability.
  • Bring peace of mind to you, your managers, and your staff.


Knowing how to utilize the ticketing system is the next step towards order and good communication within your company. Every MSP needs to have a well-defined note-taking policy that tells their engineers what needs to be put in the ticketing system and what the policy is for logging any communication outside of it.  

We actually have a ticket-writing guide that we give to all our new clients for free. You’re welcome to it as well! 

You can download it here.

But back to our tips. 

A good ticket should be rich in quality, not necessarily quantity. It should contain:

  • the troubleshooting process.
  • steps taken to solve the issue.
  • any outstanding issues or situations.

A key part of the guide is that every case note should end with one of four things:

  •  Ticket resolved: The case, task, or project is resolved and no further actions are required.
  • Next Steps: The ticket owner takes responsibility on moving forward with the case, task or project.
  • Waiting For: The ticket’s progress requires next steps to be performed by a vendor, third party, client, etc. 
  • Escalation Required: The worker assigned to the case does not have the time, resources or ability to complete the case, task or project. The ticket should be reassigned by a manager.

In regards to communicating about escalations, your technicians shouldn’t rely on the chat, as that is a recipe for forgotten information and miscommunication. 

It’s best to document all the details about a ticket that requires escalation within the ticket itself. 

Technicians should:

  1. Write ticket notes about the nature of the issue.
  2. Document the steps taken prior to escalation.
  3. Note if there is a need for a call-back. 
  4. Note the client’s expectations regarding their case.
  5. Finish the ticket with “Escalation required.” 

The ticket is then assigned to your manager or helpdesk coordinator if there is one. They will solve the issue or forward it to a senior, more knowledgeable technician to handle it.

However, simply using the ticketing system will not necessarily bring order to your MSP. If your technicians are swamped with incoming calls, emails and chats, the quality of their work and their focus will degrade. 

Productivity, technician ring groups


Before we get into the pitfalls of ring groups, they’re actually not so bad if an MSP has five or less technicians and a relatively calm workflow. However, anything above that number, or handling a greater number of tickets, will make your technicians feel like they’re drowning in work.

Luckily, there are alternatives to this chaotic practice that we’ve witnessed. This includes:

  1. Hiring a dispatcher.
  2. Hiring a help desk coordinator.
  3. Placing a level 1 technician in training to handle the intake of calls.

These steps will strengthen your frontline and hold down the fort while your technicians and managers have the focus they need for their tasks. They will have the breathing room to successfully knock down tickets one-by-one with less stress and distraction.


What happens if something really urgent occurs? Your MSP communication policy must define what is urgent and what the threshold should be.

Situations like the following can be considered urgent: 

  1. A whole network goes down.
  2. A major data breach.
  3. Major data loss.
  4. VIP user issues. 

When situations like these arise, you should define who will be alerted first.

If you are a service manager and want to be notified every time there’s a complaint about a technician, put that in your communication policy. 

Be detailed and specific about what you want sent to you and whether or not it should be sent via email, a phone call,an assigned ticket, a chat message or a combination of the above.

Rather than relying on word-of-mouth, provide solid documentation where you lay out the procedures you want to be followed. Here are some dos and don’ts to consider.

Define when to be contacted.Stress over non-urgent matters.
Define the way you are contacted.Communicate about escalation everywhere but the ticketing system.
Define the type of information you want.Allow urgent or time-sensitive information to be lost in long chat or email threads.
Keep documentation of everything.Use word of mouth.
boy shouting, escalation processes for urgent matters


A strategy that will definitely up your MSP’s communication game is utilizing incident management software like PagerDuty or Opsgenie.

PagerDuty and Opsgenie set up pre-arranged escalation patterns. For instance, an email sent to an inbox dedicated to urgent matters only could then trigger an email notification for the service desk manager. Two minutes later, they can receive a phone call or an SMS. After five minutes,  the director of operations can receive the same notification. 

You can set up your preferred escalation pattern however you like. Just make sure only real emergencies end up triggering these patterns.

You can also use escalation patterns for after-hours support. 

For example, if you use an outsourced front-line support tech for after-hours, and an urgent situation arises that’s outside of their scope, a PagerDuty alert can escalate the issue to a more senior engineer on call. 

That engineer can receive a notification that includes all relevant information instead of receiving a phone call without knowing who is calling or what the issue is. 

This is also very beneficial for the technician because they can see what the issue is about via message before being thrown into an urgent situation. It helps them to have a couple of minutes to think about what to do before they jump into action.

cables, board, channels of communication


When AN MSP’s communication isn’t streamlined and efficient, it can waste time and lower productivity. 

Getting calls without voicemails could have you wondering what the call was about, and whether or not it needs urgent attention. 

Receiving chat messages may distract you, especially if they start with a simple ‘Hi’ as opposed to having the whole issue sent immediately. 

Some things are better communicated in a ticket, others in an email, or they could wait until a weekly meeting and be added to the agenda.

We always recommend saving non-urgent issues for a scheduled meeting using Calendly. It’s an efficient way to give focused attention in real-time so that people can brainstorm and discuss how to work things out.

It’s also a good idea to create a sheet with all the information and procedures you want your employees to follow when they want to talk to you. 

This way, you will be able to digest all the information without being overwhelmed or distracted from your work. 

ChatVideo meeting booked in advance
Email with URGENT as a subjectTicketing system


documents, papers, missing documentation

When documentation procedures are not followed, problems of discontinuity can arise for an MSP’s helpdesk. But this can be dealt with using better communication strategies.  

With detailed guidelines and accountability systems in place, things can still go missing. In these cases, you need to define in your communication policy how missing documentation is dealt with. 

Here’s an example:

William is a senior technician who was on site last week to set up a printer, but he didn’t leave any ticket notes in the system. He left no details about the IP address of the printer, where to install the drivers, the WIFI network and password, etc. A week later, this is an inconvenience when someone is encountering issues with the printer while preparing some urgent documents to hand out for a meeting. If William is not around, the tech dealing with the situation will have to track William down and get all those details.

One way to prevent this is to insist on having every contact documented, especially the in-person ones. If there still is missing documentation, you want to make sure that the urgency of the issue is dealt with according to the system you’ve established for contacting you.


An absolute MUST for great MSP communication is to make your customers feel cared for before they even reach out to you.

One way to do this is by using help center articles. 

You can create a section of helpful guides on your website that will empower customers and encourage them to tackle simple issues, cutting their need to ring you up. This material can be used in technician training as well when your staff gets stuck on an issue.

Self-diagnostics is another good practice. Present your clients with a diagnostics sheet where they can choose the severity of an issue they need help with. Of course, this does not work in every scenario, but it is still very beneficial.

Set expectations with your customers regarding the time it will take for the issue to be solved or when they can expect a call back from you. Choosing a communication channel based on that urgency which will prevent push-back. 

Here’s an example chart for setting expectations.

Urgency of the IssueBest Way to CommunicateExpected Solution Time
Blocker or CriticalPhone callDepending on the issue
Not affecting crucial pointsLive chat/emailEnd of the day
Trivial, advice, inquiryEmailDay/Two
People at table talking, discussing, feedback, meeting


Being a good listener and being there for your MSP staff should be a crown you wear proudly on top of your head. 

Be it in-person or over Zoom, it can bring your business to the next level! In these meetings, you can discuss novelties in your business, exchange ideas, and discuss ways communication can be improved.

Staff meetings are awesome because they open space for collaboration and receiving feedback.

Emails bring clarity and communicate ideas directly, but they lack the warmth,  complete insight, and real-time reactions you get from seeing the person. Sometimes, when a team member is feeling lonely or overwhelmed, having face-to-face support is crucial.

Some other benefits of MSPs communicating via meetings are:

  • Learning about the personality of your team.
  • Discussing their strengths and ways they can improve their weak points.
  • Clear out any misunderstandings.
  • Build constructive routines.

Utilizing Zoom for virtual team-building can bring more joy in these uncertain times as well. 


With more than 70 team members, Support Adventure specializes in MSP staffing. We have employees all across the world doing great work while enjoying the remote life, and we can help you with finding the best remote talent!

We’ve helped over 40 MSPs already–be it with consulting about documentation, management, or providing staff. You can build your team with Support Adventure too!

Our technicians are handpicked talented individuals who go through our testing and training program to ensure they are compatible with and can contribute to your MSP goals. They possess proficient English language social skills and a friendly approach.

Kristina @ Support Adventure

Hi there! I'm Kristina Antic, the voice behind the articles you've been enjoying on the Support Adventure blog.Welcome to the crossroads of travel, transformative career advice, and all things MSP!Since joining the team in 2020, I've been weaving my experiences from traveling across Europe and Asia into stories that resonate with tech enthusiasts and wanderlust-filled souls alike.From the world of translating and IT customer service to teaching, I’ve worn many hats, all of which I now bring together to help you navigate the exciting remote landscape.Whether you’re looking to kickstart your career in tech, dreaming of digital nomad life, or seeking the best MSP practices and staff, I’m here to share what I’ve learned in a way that feels like we’re just chatting over coffee.See you on the blog!

1 Comment

Is your MSP TOO CORPORATE? Why that’s a Huge MSP Hiring Mistake - Support Adventure · March 29, 2023 at 7:42 am

[…] communication within an MSP is not open and collaborative, it leads to unclear roles that are defined by corporate jargon. And […]

Leave a Reply

Avatar placeholder

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.