Introduction
If you run an ILEC, you’re living in two worlds at once.
In one world, voice is still “the phone company”: customers expect dial tone reliability, regulators still care deeply about bad actors, and interconnect partners still behave like they’re one paperwork revision away from 1998. In the other world, your strategic oxygen is getting pulled toward broadband execution – fiber builds, take rates, construction capacity, customer migrations, and the operational maturity required to behave like a modern ISP at scale.
This “two worlds” reality is the theme of our 2026 State of the Union:
- Voice still matters – but for most ILECs it should not be the strategic focus of the year.
- The winning move is to keep voice stable, compliant, and low-drama while leadership focuses on fiber deployment and ISP growth.
Think of it like the electrical panel in your house. You definitely want it to be safe, labeled, and up to code. But you probably don’t want your family’s weekly planning meeting to revolve around the electrical panel – unless it keeps tripping breakers. Our goal (and, ideally, yours) is to make sure voice never becomes “the breaker that trips” while you’re busy building the network that actually defines the next decade.
Below is a practical, operator-focused briefing of what we see shaping 2026 for ILECs – plus what we recommend you do about it.
The 2026 scoreboard: why the center of gravity is broadband execution
The last few years have been all about building fiber – thanks to a series of government grants to encourage nationwide fiber coverage, even in rural areas. The BEAD program’s state-by-state progress is visible in public dashboards, and milestones are steadily marching forward.
What that means in plain English:
- Your organization will be judged (internally and externally) by its ability to build, light, and operate fiber networks.
- You’ll be making high-stakes decisions around construction sequencing, vendor management, installation quality, customer migration, and support operations.
- You do not have infinite executive attention available. (Nobody does.)
So if voice pulls senior leadership into a multi-quarter platform migration, a vendor re-evaluation, or a “grand vision” project that doesn’t materially increase broadband execution capacity, it’s not just expensive – it’s an opportunity cost that shows up as delayed passes, missed seasonal windows, stressed field ops, and slower revenue conversion.
That’s the backdrop for everything else in this article.
Pillar 1: Voice should be smooth, not the focus
Let’s say the quiet part out loud: for most ILECs in 2026, voice is a legacy product that must remain excellent – but it is not where competitive differentiation is likely to come from this year.
What “excellent” voice looks like in 2026
“Excellent” doesn’t mean “new.” It means:
- Service reliability: fewer outages, shorter outages, cleaner recovery. Or better yet, no outages.
- Predictable change management: clear MOPs for any maintenance activity, simple changes with minimal impact, and easy rollback.
- Healthy interconnect behavior: fewer one-way audio mysteries, fewer routing surprises, fewer call completion issues.
- Regulatory and anti-fraud posture that doesn’t require heroics (more on that later).
In other words: voice should behave like a well-run utility.
What “not the focus” looks like in practice
For most ILECs, we believe 2026 is not the year for:
- Big-bang “move everything to a brand-new voice platform” migrations.
- Feature-frenzy projects intended to “modernize” residential voice.
- Re-architecting your core voice network in ways that require constant executive decision-making.
This is not an anti-innovation stance. It’s a recognition that the strategic prize for most operators is broadband execution, and that voice modernization projects often consume outsized attention relative to the payoff – especially when the existing platform is already meeting customer needs.
The win condition
The win condition is simple:
If leadership can go an entire quarter without thinking about voice, you’re doing it right.
That doesn’t happen by accident. It happens when voice operations are engineered to be calm: stable platforms, clean runbooks, proactive monitoring, and a compliance posture that’s baked in rather than bolted on.
Pillar 2: Metaswitch + Alianza – stability now, roadmap questions later
In 2025, Alianza completed its acquisition of Metaswitch from Microsoft.
From our perspective, Alianza has done several important things right for the existing Metaswitch customer base:
- They’ve communicated proactively.
- They’ve heard the clear message from operators: “We like the platform we have. We need continuity.”
- They’ve expressed commitment to continued support.
That’s all good news – and is entirely in line with our philosophy to “keep voice boring” in 2026.
The real strategic question: where does roadmap investment go?
The questions that mattered on day one of the acquisition still matter now:
- What is the long-term platform strategy?
- How will Alianza invest across multiple product lines?
- What does the “future of features” look like?
When one company operates multiple platforms, the real constraint isn’t ideas. It’s engineering focus. If investment is split across two platforms, feature velocity can slow. If we add Alianza Fusion (a cloud-hosted Metaswitch) to the mix then we have three platforms, which dilutes resources even further.
The abstraction dream: unified APIs
The big announcement at the Navigate conference back in September, was the “Intelligent Communications Fabric” – the concept of splitting Alianza’s products/service into three layers:
- Infrastructure: Alianza One, Core (Metaswitch) or Fusion (Cloud-Metaswitch)
- Orchestration: Management and APIs
- Experience: End-user products.
There is an appealing architectural idea here: if multiple platforms expose a unified interface, you can build tools and features once and drive them through common APIs. In telecom terms, that’s the difference between “we have three products” and “we have one ecosystem with multiple engines.”
Will the Intelligent Communications Fabric allow rapid development of new features that will work regardless of the underlying infrastructure? Maybe, but unfortunately developing this abstraction layer introduces a further delay before work on any new infrastructure-independent features, so right now it’s a waiting game.
The 2026 takeaway for most ILECs
For residential voice, small business, and basic Class 5 use cases:
- Stability beats novelty.
- The Metaswitch platform already delivers the features most of those customers expect, so as long as the core platform continues to operate well, these questions about the roadmap may not be a big deal.
- In the “fiber first” year, the smartest move is often to keep running what works and avoid unnecessary churn.
However, if Alianza wants to compete against Ring Central for the premium business services market, then we’ll need to see some truly exciting feature development in the near future – which brings us to Pillar 3.
Pillar 3: UCaaS is the place where “features” actually matter
There is one major exception to “features don’t matter much right now,” and it’s business communications.
If you are competing for business voice in a market where customers compare you to cloud UCaaS giants, then feature expectations are real and non-negotiable. The baseline set by major UCaaS providers is broad: mobility, integrations, analytics, contact center adjacency, and “it just works” admin UX.
So we separate voice into two lanes:
Lane A: Class 5 foundation (residential + straightforward business)
This lane is about:
- reliability
- affordability
- easy interconnectivity with the PSTN
- clean translations and accurate billing
- regulatory compliance
- minimal drama.
Here, the best practice is often to keep the existing Class 5 platform strong.
Lane B: Competitive UCaaS (business growth)
This lane is about:
- feature velocity
- user experience
- integration ecosystems
- rapid iteration.
Here, a cloud-native UCaaS platform is often the right tool, as it easily allows the rapid iteration of new features – and it doesn’t need to “replace” Class 5 to be valuable. In fact, running a UCaaS platform alongside a stable Class 5 core can be the most pragmatic way to compete: use the right product for the right job.
This is why we’re comfortable with a “two-platform” strategy for many operators: keep the proven Class 5 base for foundational services, and use a separate cloud UCaaS platform when you need to compete head-to-head in the business market.
Pillar 4: Compliance isn’t paperwork anymore – it’s systems engineering
If broadband execution is the strategic center of gravity in 2026, then robocall mitigation is the compliance gravity. The FCC continues to refine requirements and tighten expectations around caller ID authentication (STIR/SHAKEN), robocall mitigation, and provider obligations.
The DNO requirement: a concrete example of the direction of travel
A major late-2025 milestone was the FCC requiring providers in the call path to block calls using a reasonable Do-Not-Originate (DNO) list, with an effective date set for December 15, 2025.
This matters for two reasons:
- It reflects a continued push toward upstream blocking – stopping bad traffic earlier, before it propagates.
- It further pushes “robocall mitigation” as an automatic, ongoing process rather than a paperwork exercise.
Award’s approach: simplify the complex, once – then repeat it safely
One of the things we’re most proud of in 2025 was our DNO rollout approach, because it captures how we think about our role in the ILEC market:
- We saw the requirement coming.
- We recognized it would be burdensome for each provider to solve independently.
- We combined the necessary ingredients (data licensing, implementation design, and operational roll-out) into a “done-for-you” service that providers could adopt without building a mini product team internally.
That’s the model we intend to keep applying: when there’s a new industry requirement, we want to help you implement it in a way that is simple, correct, and sustainable.
Pillar 5: Cloud voice – good destination, bad “right now” trade for most ILECs
We are regularly asked about moving voice to the cloud. It’s a popular conference topic, and for good reason: on a whiteboard, it looks clean.
But in the field, the “move voice to the cloud” story often collides with reality.
The short version of our cloud voice talk
- Long-term, cloud voice makes a lot of architectural sense.
- Short-term, for many ILECs, it’s not worth the cost, risk, and distraction.
Why the near-term economics are often disappointing
In theory, you move to the cloud and win:
- simplified infrastructure,
- elastic scaling,
- easier upgrades,
- modern tooling.
In practice, ILECs often discover that many parts of the ecosystem still behave as if the world is TDM-shaped:
- billing and regulatory processes that assume TDM and traditional tandem interconnect,
- interconnect relationships and agreements built around older assumptions,
- and an operational environment where “the last 2%” of edge cases is where 80% of the pain lives.
Add another issue: many cloud voice products were born as UCaaS platforms. They’re excellent at what they were built for. But they may not have every feature and behavioral expectation required of a regulated Class 5 replacement (LNP, LD carrier routing, full billing capabilities) – especially in the nuances ILECs and their customers take for granted.
The result we see too often
When ILECs attempt this today, the project can become:
- larger than expected,
- riskier than expected,
- and, at the end, less satisfying than hoped.
Our 2026 recommendation
Unless you have a very specific driver that changes the equation, we generally recommend:
- There’s no need to be on the bleeding edge.
- Defer big platform migrations.
- Keep voice stable and compliant with minimal executive attention.
- Put the strategic energy into broadband expansion and ISP operations maturity.
Cloud voice may absolutely be part of the future. There are ongoing discussions at the FCC which could remove some of the technical and financial barriers to cloud adoption – but we simply don’t see a strong advantage to being among the earliest movers while the ecosystem still contains so much “legacy gravity.”
What Award Consulting is building for 2026: beyond Metaswitch, toward “voice operations without the headaches”
Our heritage is Metaswitch expertise – and it remains a strong foundation for our client engagements.
But as we look at what ILECs actually need in 2026, we’re expanding in two directions:
- Broader platform coverage
- More done-for-you operational services
Broader platform coverage
Voice networks do not live in a vacuum. They rely on SBCs, gateways, IP networks, analytics, and UCaaS layers. We’ve been investing heavily in hands-on capability across the platforms that most commonly show up in real-world ILEC environments, including:
- TelcoBridges Tmedia media gateways
- TelcoBridges ProSBC
- NetSapiens UCaaS deployments (helping providers launch competitive business offerings)
- TransNexus ClearIP and related analytics/mitigation tooling (including robocall mitigation and fraud-focused analytics)
The goal is not to chase every shiny tool. The goal is to be able to help you stabilize and operate the real network you have – not the network in a vendor slide deck.
Done-for-you operational services
Our DNO work is one example of a pattern we want to repeat: simplify, package, maintain, and keep you out of the weeds.
In 2026, we’re also working on services that remove recurring operational burdens, like:
Lightweight translations updates (quarterly)
Numbering changes happen continuously. If your translations don’t keep up with new NPA-NXX assignments, the outcomes are predictable: misroutes, failed calls, billing errors, and customer complaints that feel “random” until you spend half a day chasing them.
We’re developing a lightweight quarterly translations update service focused on keeping local and regional routing and billing behavior correct – more right-sized and affordable than a full LERG update process, while still protecting you from avoidable mistakes.
Stronger IP-network support
Whether you’re troubleshooting firewalls, routers, VPNs, or SIGTRAN paths that traverse your IP network, voice increasingly depends on IP fundamentals being solid. We’re investing more deeply in helping operators run the IP substrate that both voice and broadband services rely on.
Award Aware: a single dashboard for proactive network confidence
We’re also developing a monitoring dashboard concept we call Award Aware: a single pane of glass that can observe key elements of the voice core and critical IP edge devices. The purpose is simple: spot unusual patterns and emerging problems early, so issues get addressed before they become outages and escalation spirals.
The operating philosophy that ties this all together
Everything in this 2026 State of the Union boils down to a philosophy we apply repeatedly:
- Prioritize what wins the decade (fiber execution and ISP maturity).
- Stabilize what still pays the bills (voice).
- Engineer compliance as a system (not a scramble).
- Avoid distraction migrations unless the business case is overwhelming.
- Package complexity into repeatable services so your team can focus.
If you’d like a one-line summary, it’s this:
Make voice calm – so you can build broadband fast.
A practical call to action
If any of the following sound familiar…
- “Voice takes too much attention.”
- “We don’t have the right in-house expertise to maintain our voice platform.”
- “We need help to stay compliant with robocall mitigation, DNO and STIR/SHAKEN – as affordably as possible.”
- “We’re tempted by cloud voice, but don’t want to be a cautionary tale.”
- “We need a UCaaS plan but don’t know which vendors to consider.”
…then we should talk.
Award Consulting’s job is to help ILECs keep voice stable, compliant, and easy – so leadership can stay focused on the fiber/ISP business that defines 2026.
Contact us, and tell us which pillar is most urgent for your team – and we’ll be very happy to help.
