VoIP for MSPs: Should You Add Hosted PBX to Your Services?

Tom Reed · Updated 24 October 2026

Adding hosted voice makes sense for an MSP when your clients already rely on you for IT, you're comfortable with SIP trunks, numbers and call flows, and you pick a platform that runs the servers for you. Before you sell it, check the skills you'll need, what the platform handles versus what you support, and test it with one friendly customer first.

This guide on VoIP for MSPs is for managed service providers and IT resellers deciding whether to add a hosted PBX to their services. It's vendor-neutral until the section on SessionPBX near the end. Teams Phone and Teams Business, mentioned there, are SessionPBX plans, not Microsoft Teams.

Why are MSPs adding voice to their services?

Most MSPs don't go looking for a phone system to sell. Their clients ask for one. A client moves office, their old phone contract comes up for renewal, or half the team now works from home and the desk-bound system no longer fits. They already trust you with their laptops, email and network, so they ask whether you can sort the phones too.

There are three common reasons MSPs say yes:

• Consolidation. Clients like one supplier for their IT. If you already manage their devices and network, voice is a natural next step, and it removes one more vendor from their list.
• Recurring revenue. Hosted voice is billed as an ongoing service, so it fits the same monthly or annual model as the rest of your managed services. You set the price, so you decide how it fits your contracts.
• A stickier service. A phone system touches every person in the business every day. When it works well and you run it, the relationship gets deeper.

If you need a refresher on how the parts of a hosted system fit together, our guide to the PBX phone system covers the basics.

That doesn't mean every MSP should sell voice. The rest of this guide helps you decide whether your business is ready, and what you'd be taking on.

Is your MSP ready to sell VoIP?

Before you work out how to sell VoIP, check whether you can deliver it well. Voice is less forgiving than most IT services: a slow file share is annoying, but a missed call can cost your client a customer. Use this checklist to see where you stand. If you can tick most of it, you're in a good position to start a VoIP business line inside your MSP. If you can't, the gaps tell you what to fix first.

Is your MSP ready to sell hosted voice?

1. Clients already ask about phones. You have real demand, not a guess.
2. Someone on the team understands SIP trunks and carriers. They know how a trunk connects, how it authenticates and where numbers come from.
3. You have, or can pick, a SIP carrier. You know which carrier you'd use and how you'll set up an account with them.
4. You can build call flows. Business hours, IVR menus, queues and ring groups are things your team can design and change.
5. You can provision softphones on Windows, macOS, iOS and Android. Ideally without anyone typing SIP settings by hand.
6. You've decided your support scope and hours. You know what you'll handle, what goes to the carrier and what goes to the platform.
7. You know how you'll price it. You've checked the platform's partner pricing (for SessionPBX, that's on the partner programme page) and how voice fits your contracts.
8. One pilot customer is lined up. A friendly client who will give honest feedback.
9. You have a handover pack template. A short document for each client covering how to use the system and how to get help.

If you're still comparing partner programmes rather than deciding whether to sell at all, our guide on how to choose a VoIP reseller program covers what to ask each vendor.

What skills does your team need for hosted voice?

An MSP VoIP offer doesn't need a team of telecoms engineers, but it does need a few specific skills. A hosted platform removes the server work. It doesn't remove the need to understand how calls get in and out, or why a call sounds bad.

SIP trunks and carriers. Someone on your team should understand how a SIP trunk connects the phone system to the outside world, how it authenticates (by IP or by credentials), and what the carrier is responsible for. Our guide to choosing a SIP trunk provider for a hosted PBX walks through how to compare carriers.

Numbers through the carrier. With a bring-your-own-trunk platform, phone numbers come from the carrier. Your team needs to know how to order numbers from the carrier, point them at the right trunk and route them to the right place in the phone system.

Channel planning. You'll need to size each customer's trunk for how many calls they make at once. Our guide to how many SIP channels you need explains how to estimate it without guessing.

Call flows and IVR. Building a call flow is part design, part configuration. Your team should be able to sit with a client, map out what happens when someone calls in and out of hours, and turn that into menus, queues and ring groups.

Softphone provisioning. Most hosted voice today runs on softphones on computers and mobiles. Your team needs a reliable way to get each user set up, ideally by QR code or setup link rather than typed passwords.

Basic network and call-quality troubleshooting. When a client says calls are choppy, someone needs to check the usual suspects: Wi-Fi, firewall and NAT rules, available bandwidth on the office connection and quality-of-service settings. This is where your existing network skills pay off.

What does the platform run, and what do you run?

The biggest decision when you sell VoIP is who does what. Clear lines stop tickets bouncing between you, the platform and the carrier, and they help you set your support scope. Here's how it typically splits on a hosted, bring-your-own-trunk platform, using SessionPBX hosted as the example.

Who does what with hosted voice

The pattern is simple. The platform runs the infrastructure. You run the customer. The carrier runs the trunk and the numbers. Write this split into your contracts and your handover pack so the client knows who to call, and so do your engineers.

What should your voice support cover?

Voice support works best in tiers. Your team takes the first call, fixes what it can and escalates the rest to the right party with the evidence they'll need.

What you handle. User setup and removals, call flow changes, out-of-hours routing, app sign-in problems, headsets and audio settings, Wi-Fi and network issues at the client's site, and training. These are the bulk of voice tickets, and they're the ones your client expects you to fix quickly.

What goes to the carrier. Calls that won't connect to outside numbers, numbers that don't ring through, caller ID problems on the trunk and call charges. Before you escalate, check whether the trunk is registered and whether internal calls still work. That tells you whether the fault is likely to be on the trunk side.

What goes to the platform. Anything that looks like a platform fault rather than a configuration or network issue. Check the platform's partner docs first, then raise it through the partner support route with times, extensions and what you've already ruled out.

Decide your support hours before you sell. Phones matter most when the client's business is open, and some clients open earlier or close later than your service desk. If you can't cover their hours, say so in the contract and agree what happens out of hours.

Provisioning is the support area that catches new MSPs out. Sending SIP passwords by email or typing them in on someone's phone creates risk and extra tickets. Our guide to secure softphone provisioning for MSPs explains how to set up users with QR codes and setup links so credentials stay safe.

How do you pilot hosted PBX with your first customer?

Don't launch voice to your whole client base at once. Pilot it with one customer first, learn from it, then roll out. A good pilot looks like this:

1. Pick one friendly client. Choose someone who trusts you, will tell you what isn't working and won't be hurt by a rough edge. A small office is ideal.
2. Keep the seat count small. Start with the people who will actually use it daily, not every user in the business.
3. Use the partner customer-tenant trial. If your platform offers trials on customer tenants, use one so you aren't paying while you learn. On SessionPBX, new partner customer tenants receive a 30-day trial, subject to your concurrent trial allowance, and a partner administrator must explicitly purchase the subscription to continue service.
4. Define success before you start. For example: calls reach the right person, the out-of-hours message plays, users can make and take calls on mobile and desktop, and nobody needs to call you about sign-in.
5. Connect a test trunk. Use your chosen carrier and test inbound and outbound calls before any of the client's real numbers move.
6. Build the call flow with the client. Sit with them, agree what happens when someone calls, and build it together.
7. Write the handover pack. Use your template and fix anything that was unclear during the pilot.
8. Review, then roll out. Look at what went well and what didn't, update your runbook and checklist, then offer it to the next clients on your list.

Put a reminder in your process before any trial ends. If the platform needs a partner admin to buy the subscription to keep service running, you don't want a client to lose their phones because nobody clicked buy.

When is voice a bad fit for an MSP?

Hosted voice isn't right for every MSP, and saying no is a valid answer. It's probably a bad fit if:

• Nobody has SIP skills, and nobody wants to learn. A hosted platform removes the servers, not the need to understand trunks, numbers and call routing. If nobody on the team will own it, tickets will sit.
• Your clients need things your chosen platform doesn't offer. Some clients want physical phones on every desk, or expect you to supply their numbers yourself rather than through a carrier. Check the platform's feature list against what clients actually ask for before you promise anything.
• You have no capacity for call-quality support. Voice problems are often network problems. If your team is already stretched, choppy calls and one-way audio will land on people who don't have time for them.
• Your support hours don't match your clients' business hours. Phones are critical during opening hours. If you can't cover them, a client will notice quickly.
• Your clients are happy and not asking. If nobody wants it, there's no rush. Revisit the decision when demand appears.

How does SessionPBX work for MSPs?

Here's how SessionPBX fits the model in this guide, using what the SessionPBX Partner Programme page says.

Who it's for. The programme is for PBX resellers, managed service providers, IT companies and communications providers that sell phone systems to business customers.

Hosted or self-hosted. On hosted, SessionTalk hosts and maintains SessionPBX and there's nothing to install. You choose where each customer is hosted: the UK (London), the US (New York) or Singapore, and each region has its own database. Hosted plans offer monthly or annual billing. Self-hosted is for approved partners only: you run it on your own server, with annual licences and many customer tenants on one server, each kept separate.

Customers. Each customer gets one SessionPBX project. You create it, you own it, and you manage extensions, numbers, the SIP trunk and call flows for that customer.

Carriers. SessionPBX is bring-your-own SIP trunk. You connect any SIP-compliant carrier by IP or credentials, and your carrier bills for numbers and calls. SessionPBX doesn't supply numbers or lines. Internal calls between team members are included.

Apps. Apps run on Windows, macOS, iOS and Android, with QR or link provisioning and branded setup emails. Call handling (IVR, queues, recording and supervision) is on Teams Business.

Branding. App logo branding puts your logo and in-app product name on the softphones. It's included with Teams Business and available as an add-on on Teams Phone. Teams Phone and Teams Business are SessionPBX plans, not Microsoft Teams.

Billing. Approved partners get a partner discount on every seat. You set your own price and invoice your customer, so there are no commissions to chase and no payouts to wait for. Current partner pricing is on the partner programme page.

Security. SIP signalling, messaging and the admin portal use TLS, and stored SIP trunk credentials are encrypted with AES-256-GCM.

Applying. You don't need a portal account to apply, and every application is reviewed by hand. The partner docs are at docs.sessiontalk.io/docs/partners.

Once you've decided to go ahead, our guide to packaging hosted PBX for MSPs and telecom resellers covers how to bundle it. To see the phone system your customers would use, visit the SessionPBX hosted PBX page. When you're ready, apply to the SessionPBX Partner Programme.

FAQ

Do MSPs need telecoms experience to sell VoIP?

Some SIP and call-flow knowledge helps, and someone on the team should understand SIP trunks and carriers. A hosted platform removes the server work, so most of what you need builds on the network and support skills an MSP already has.

Do I have to run my own phone servers?

Not on hosted. With SessionPBX hosted, SessionTalk hosts and maintains it and there's nothing to install. Self-hosted is an option for approved partners who want to run it on their own server.

Who supplies phone numbers and call minutes?

Your chosen SIP carrier. SessionPBX is bring-your-own SIP trunk: you connect any SIP-compliant carrier, and your carrier bills for numbers and calls.

Can I try it with a customer before committing?

Yes. On SessionPBX, new partner customer tenants receive a 30-day trial, subject to your concurrent trial allowance, and a partner administrator must explicitly purchase the subscription to continue service.

Can my logo be on the apps?

Yes. App logo branding puts your logo and in-app product name on the softphones. It's included with Teams Business and an add-on on Teams Phone. Teams Phone and Teams Business are SessionPBX plans, not Microsoft Teams.

Where do I see partner pricing?

On the SessionPBX Partner Programme page. Partner pricing applies to both hosted and self-hosted.