Voice and Connectivity in a Practice Built for Something Else
A reader-side brief for MSP owners and principals at firms without a formal in-house telecom or connectivity practice — what the OML rubric says about voice scope, what the UCaaS resale paths actually cost, what the FCC copper sunset is bringing to your client environments, and what wallet-share displacement actually looks like when a competitor wins the scope you did not run.
Voice and connectivity sit outside your OML rubric. The scope arrives anyway.
Your service catalog rewards what your operational maturity rewards: managed security, cloud, help desk, email, RMM. Voice and connectivity are not in the OML "best-in-class" rubric, the MSP 501's top revenue producers, or Kaseya's top-five fastest-growing categories. That absence is not an oversight. It is a structural fact about the operational profile carrier resale demands — FCC compliance, telecom taxation, STIR/SHAKEN, E911, Kari's Law, RAY BAUM's Act, and 24/7 voice support.
The category your practice is not built for is showing up on your client environments anyway. The FCC has approved AT&T's discontinuation of copper service across roughly 30% of its footprint, with a Nov 15, 2026 cutoff. The Feb 22, 2024 AT&T Mobility outage blocked more than 92 million voice calls in a single 12-hour event. Your master service agreement carves out third-party failures, but your brand does not. The brief sets out what the data says about each option (build, refer, or do nothing) and names the four criteria a well-handled partner-referral function meets.
- Voice and connectivity sit outside the OML rubric, the MSP 501 top revenue list, and Kaseya's top-five fastest-growing categories.
- AT&T copper sunset closes Nov 15, 2026; the affected systems are exactly the ones the MSP gets called about.
- Tier-1 carrier outages happen weekly; blame defaults to the MSP that recommended the carrier.
- A handled-well partner-referral function meets four criteria you can recognize before you sign anything.
Research-driven and vendor-neutral. The MSP is the reader, not the channel. The brief delivers standalone value: an MSP that downloads it and never engages Govcraft should still finish better-equipped to evaluate its own posture on voice and connectivity scope. The contact for those who want it run by an outside partner is on the back panel.