Should Your MSP Offer Voice Services?

The MSP's Guide to VoIP: Part 1 of 20

Disclaimer: This post is educational content about the business considerations of offering VoIP services as an MSP. It is not legal advice. Regulations change, interpretations vary, and your specific situation may differ from the general scenarios described here. Consult with a telecom attorney to determine how these regulations apply to your business.

If you run a managed services provider, you have heard the question. Maybe it came from an existing client whose phone contract is up for renewal. Maybe it came from a prospect who assumed you already handled phones. Maybe it came from your own sales team who noticed that every client engagement starts with a conversation about internet and networking but ends with someone else getting the voice deal.

The question is always some variation of: "Can you do our phones?"

And the honest answer for a lot of MSPs is: we could, but should we?

This series is about helping you answer that question with open eyes. Not with a vendor's slide deck that makes everything look like easy margin, and not with the cynicism of someone who tried it once, got burned, and swore it off. Voice services can be genuinely profitable and strategically valuable for an MSP. They can also be a support nightmare that eats into your margins on everything else. The difference comes down to understanding what you are getting into before you commit.

The revenue case

Let's start with why so many MSPs are interested in voice in the first place: the numbers.

Voice services generate recurring monthly revenue. Per-seat pricing for hosted VoIP platforms typically ranges from $15 to $35 per user per month at retail, with wholesale costs that leave meaningful margin. For an MSP managing a 50-seat client, that could be $750 to $1,750 in monthly recurring revenue from a single account. Multiply across your client base and voice starts to look like a serious line of business.

Beyond the direct revenue, voice creates stickiness. A client who buys internet management, endpoint management, and voice from the same MSP is significantly harder to displace than a client who buys those services from three different providers. When everything is integrated, switching any one piece becomes painful. That stickiness translates to lower churn, longer contract terms, and higher lifetime value per client.

There is also the competitive angle. If you don't offer voice, someone else will. And that someone else now has a relationship with your client, a foot in the door, and a reason to be in their office talking about technology. Today they are selling phones. Tomorrow they are pitching managed services. The MSP that handles voice is in the room for the full technology conversation. The one that doesn't is hoping nobody else brings it up.

The support reality

Now for the part the vendor slide deck glosses over.

Voice support is different from data support in ways that matter operationally. When a file server goes down, someone opens a ticket. It is disruptive and urgent, but it is a known quantity. You triage, you escalate, you fix it.

When the phones sound bad, or calls are dropping, or a client's caller ID is showing the wrong number, you get a different kind of engagement entirely. Phone problems are immediate and emotional. The person calling you is often in the middle of a conversation with their customer, their patient, their vendor, and the technology is making them look unprofessional. They are not submitting a ticket and waiting. They are calling your support line, and they are frustrated right now.

This changes the cadence of support. Most voice issues happen during business hours, because that is when people are on the phone. Your support team needs to be responsive during exactly the hours when they are also handling every other client's needs. You cannot push voice troubleshooting to evening maintenance windows. The problem is happening live, and the client expects you to be working on it live.

The troubleshooting itself requires different skills than most data support work. Diagnosing why calls sound choppy and robotic requires understanding of jitter buffers and packet loss. Figuring out why calls are dropping after a set time requires knowledge of SIP timers and NAT behavior. Understanding why there is one-way audio means you need to understand how RTP media streams are established and how firewalls can interfere. These are not skills most MSP technicians have on day one. Building that competency takes time, training, and a willingness to invest in an area that is genuinely complex.

What clients actually want

When a client asks "can you do our phones," they almost never mean what you think they mean. They are not asking about SIP trunking architectures or codec selection or DSCP marking. They are asking for someone to make phones work and to be responsible when they don't.

What they want is deceptively simple:

Dial tone. Phones that work when you pick them up. Calls that connect, sound clear, and don't drop. This is the baseline, and it is non-negotiable. Nobody thanks you for dial tone. They only notice when it is missing.

Features that match expectations. Auto attendants, voicemail to email, call recording, ring groups, find-me-follow-me. These are table stakes for any modern business phone system, and clients expect them to work without thinking about them. They also expect you to program and modify these features when their needs change, which happens more often than you might expect. People get promoted, departments reorganize, new hires start, employees leave. Every one of those events touches the phone system.

A single throat to choke. This is the big one. Clients do not want to call their phone vendor, who tells them to call their internet provider, who tells them to call their IT company. They want one number to call when something is wrong, and they want that person to own the problem until it is fixed. If you offer voice, you become that person. Even when the problem is actually their internet connection or their local network, the first call comes to you because you are the phone company.

This last point is both the opportunity and the trap. Being the single point of contact is what creates the stickiness and the perceived value. It is also what creates the support burden, because you will be triaging problems that span networking, internet, and telephony, often simultaneously, and the client expects you to sort it out regardless of where the root cause lives.

The three models

Not all voice offerings are created equal. How you structure your voice offering determines everything: your margin, your support load, your technical requirements, and your regulatory exposure. The spectrum runs from lightest touch to deepest involvement.

Referral. You point the client to a hosted VoIP provider, maybe make an introduction, and step back. You might earn a referral fee or a small ongoing commission, but you are not providing the service. The provider handles sales, provisioning, support, and billing. Your involvement is minimal. Your revenue is minimal. Your liability is minimal. But you have also given away the client relationship for that piece of the stack, and you have no control over the client's experience.

White-label resale. You sell a hosted platform under your brand (or a shared brand). The underlying infrastructure is operated by a wholesale provider, but the client sees your name on the invoice and calls your team for support. You handle first-line support and configuration changes; the wholesale provider handles the platform, trunking, and carrier relationships. Your margin is better than a referral, and you own the client relationship. But you also own the support obligation, and your ability to resolve problems is limited by what the wholesale provider gives you access to.

Full stack. You operate your own PBX infrastructure (physical or virtual), contract directly with SIP trunk providers for PSTN connectivity, and manage the entire voice environment end to end. Your margin potential is the highest, but so is your operational complexity. You are responsible for platform uptime, security, upgrades, capacity planning, and regulatory compliance. You need staff who understand not just how to configure a phone system but how to maintain one. Even in the evaluation phase, tools like a Bandwidth Calculator can help you model whether a prospective client's network can support the call volumes you are sizing for.

Each of these models changes the answer to the original question in fundamental ways. We will dig into the specifics of each model in the next post, but the important thing to understand now is that "offering voice" is not a single decision. It is a spectrum, and where you land on that spectrum determines what you need to build, what you need to learn, and what you are signing up for.

The cost of doing it poorly

Here is where a lot of MSPs get into trouble. They decide to offer voice, pick a platform, do a few deployments, and then discover that they underestimated the support and operational requirements. The result is a voice offering that loses money when you account for the support time it consumes, or worse, a voice offering that damages the client relationships you built on the data side.

Bad voice experiences are visceral. If your managed antivirus misses an update, nobody notices until something happens. If your client's phones sound terrible for a week, everyone in that office notices every single day. They notice when they are on calls with their customers. They notice when they are on calls with each other. And they associate that experience with you, because you are the one who sold them the phone system.

The damage extends beyond the voice service itself. A client who is unhappy with their phones will start questioning everything else you manage. "If they can't get the phones right, what else are they missing?" Voice quality problems erode trust across your entire relationship, not just the voice piece.

The inverse is also true, and this is the part worth paying attention to. An MSP that delivers rock-solid voice becomes deeply embedded in the client's operations. When phones work perfectly and the MSP is responsive to changes and proactive about maintenance, the client sees the MSP as genuinely essential to their business. That perception is worth more than the monthly recurring revenue from the voice service itself.

The regulatory threshold most MSPs miss

Offering voice services to clients crosses a legal threshold that most MSPs do not see coming. You are no longer just providing IT services. You are entering telecommunications, and that comes with a distinct set of regulatory obligations.

The distinction catches people off guard because of a common confusion around the Universal Service Fund. If you pay USF surcharges on your own business VoIP lines, that is a consumer obligation passed through by your provider. The moment you begin offering interconnected VoIP to clients, you become a voice service provider in the eyes of the FCC, and your obligations change fundamentally.

The key obligations for a voice service provider include: FCC registration, obtaining an Operating Company Number (OCN), STIR/SHAKEN call authentication compliance, registration with the Robocall Mitigation Database, annual FCC filings (Form 499-A), and USF contribution obligations as a provider rather than a consumer. These are not optional, and they apply whether you think of yourself as a phone company or as an MSP that happens to sell phones.

Fines for non-compliance can exceed six figures. The FCC can assess USF contributions retroactively, meaning years of unfiled obligations can land as a single bill. An MSP that has been operating a voice business for three years without proper filings could face a retroactive assessment that erases every dollar of profit those voice services ever generated.

This is not a theoretical risk reserved for large carriers. MSPs operating small voice businesses have the same filing obligations as national providers. The FCC classifies providers based on what they do, not how big they are. Years of profit can be erased overnight by violations you did not know you were committing.

This series covers the regulatory landscape in detail in Parts 17 through 20. Do not treat those posts as optional reading you will get to later. Understand your obligations before you sign your first wholesale agreement.

The skills gap

Delivering quality voice services requires competency in areas that most MSP technicians are not trained in. This is not a criticism. It is a reflection of the fact that voice and data have historically been separate disciplines, and the MSP model grew up on the data side.

Your team needs to understand how VoIP works at a level deeper than "it's phone calls over the internet." They need to understand SIP signaling well enough to read a registration failure and know whether the problem is credentials, DNS, or a firewall. They need to understand QoS well enough to configure it correctly and to recognize when a quality problem is caused by its absence. They need to understand how the internet path affects voice well enough to tell the difference between a local network problem and a provider problem, because the client is going to expect them to make that determination.

This competency does not appear overnight. You either hire people who already have it (expensive and hard to find), train your existing team (time-consuming but builds long-term capability), or partner with a platform that abstracts away enough of the complexity that your team can operate effectively without deep telephony expertise (which is the appeal of the white-label resale model).

None of these approaches is wrong, but all of them require deliberate investment. The MSPs that struggle with voice are usually the ones that assumed their existing technical team could handle it without additional training or resources.

Competitive pressure

There is a defensive argument for offering voice that is worth acknowledging separately. The managed services market is consolidating, and the MSPs that are winning are the ones offering a comprehensive technology stack. Voice is part of that stack.

When a prospect is evaluating MSPs, the one that can handle endpoints, servers, networking, security, cloud, and voice has a significant advantage over the one that handles everything except voice. The comprehensive MSP gets a single contract, a single relationship, a single point of accountability. The other MSP gets a more limited engagement and a competitor in the account from day one.

If you are losing deals because you do not offer voice, that is a signal worth paying attention to. It does not mean you should rush into voice without preparation, but it does mean the market is telling you something.

The honest assessment

Here is how to think about whether voice makes sense for your business right now.

It probably makes sense if: you have a stable client base asking for it, you are willing to invest in training or hiring for voice-specific skills, you have (or can build) a support workflow that handles real-time issues during business hours, and you have identified a service model that matches your current capabilities. You do not need to start with full stack. Starting with white-label resale and building competency over time is a perfectly valid path.

It probably does not make sense if: your current support team is already stretched thin, you are not willing to invest in voice-specific training, or you are primarily motivated by the revenue without a plan for the support load it creates. Adding voice to an already overloaded operation is a recipe for poor delivery, which will cost you more in damaged client relationships than you will gain in recurring revenue.

It might make sense later if: you are interested but not ready. In that case, the best move is to build competency now. Learn the technology, understand the support requirements, get your network fundamentals solid, and position yourself to add voice when your operation can support it. Everything in this series will help with that.

What this series covers

This is the first post in a twenty-part series that covers everything an MSP needs to know to evaluate, build, and operate a voice business. We will work through service models, client expectations, network readiness, platform selection, provisioning, troubleshooting, operations, and compliance.

The series assumes you already have a working MSP and a solid understanding of networking fundamentals. We are not going to explain what a VLAN is or how DHCP works. If you need a refresher on how VoIP works at a fundamental level, the VoIP From the Ground Up series is the place to start. If you need to understand the internet connectivity piece, the Getting the Internet Right series covers that. This series builds on both and focuses specifically on the business and operational aspects of delivering voice as a managed service.

The goal is not to sell you on offering voice. It is to give you the information you need to make a good decision, and if you decide to move forward, to do it in a way that works for your clients and for your business.

Next up: Voice Service Models: Reseller, Referral, and Full Stack, a detailed look at each model, its margins, its support requirements, and its implications for the rest of your business.