The New South Wales Rugby League (NSWRL) has retired its legacy Private Automatic Branch Exchange (PABX) telephony system in favor of a Microsoft Teams-native contact center, a move that slashed deployment time and modernized fan engagement. The organization tapped AnywhereNow’s Tendfor platform, which operates entirely within the Teams client on Windows and other devices, eliminating the need for separate telephony hardware or softphones.

The announcement, shared this week, signals a growing trend among mid-sized enterprises to abandon aging on-premise PBX infrastructure for cloud-based communication tools that integrate seamlessly with Microsoft 365. For Windows users—whether agents, administrators, or the rugby fans dialing in—the shift means a more cohesive, familiar experience that rides on top of the collaboration hub they already use daily.

From Clunky Hardware to Cloud-Native Calls

For decades, PABX systems have formed the backbone of business telephony. These boxy, on-site devices route calls to extensions, manage voicemail, and handle basic call queuing. But they come with steep upfront costs, require specialized maintenance, and choke on modern demands like remote work, omnichannel interactions, and deep application integrations. NSWRL’s previous PABX was no exception—an increasingly cumbersome relic that couldn’t keep pace with the league’s need to serve fans, sponsors, and partners quickly and flexibly.

“Maintaining a physical PABX in 2025 is like running a server room for email,” said an industry analyst familiar with the migration. “It ties an organization to a specific location, adds hardware refresh cycles, and often falls short on analytics and remote access.”

Enter AnywhereNow’s Tendfor. Unlike overlay contact center solutions that bolt onto Microsoft Teams via extra connectors or third-party apps, Tendfor is natively built inside Teams. It leverages the same telephony infrastructure that Teams already uses—whether that’s Microsoft Calling Plans, Direct Routing via a certified Session Border Controller, or Operator Connect—and adds advanced contact center features without requiring agents to leave the Teams interface. In fact, agents don’t install a separate app; they simply log into Teams and see a Tendfor-powered queue, wallboard, and customer interaction pane right within their familiar channels and chats.

Inside the NSWRL Deployment

NSWRL’s move was remarkably swift. While a typical PABX rip-and-replace can drag on for months—requiring new cabling, desk phones, and staff retraining—the league’s transition to Tendfor was measured in weeks, according to sources close to the project. The organization kept its existing Teams licenses and simply activated Tendfor as an integrated service. No new hardware was purchased; existing Windows laptops and desktops became the agent endpoints thanks to the full Teams client.

A key accelerant: Tendfor’s zero-footprint architecture. Because it lives inside Teams, it inherits all of Microsoft’s security, compliance, and identity posture. Conditional access policies, multi-factor authentication, and data residency controls apply to voice interactions just as they do to chat or meetings. For NSWRL, a sports body handling sensitive fan data and sponsorship negotiations, this compliance continuity was a critical factor.

The deployment encompassed a full contact center feature set: intelligent call routing based on skills and availability, real-time dashboards for supervisors, call recording with automatic transcription and sentiment analysis (powered by Azure Cognitive Services), and integrated CRM screen pops. If a fan calls about a membership renewal, the system can pull up the relevant Salesforce or Dynamics 365 record right inside Teams before the agent even answers.

A Seamless Windows Experience

For the Windows enthusiast, this story underscores how deeply Microsoft has embedded telephony into its operating system ecosystem. The Teams client on Windows 11 (and Windows 10) already ties into native notifications, the taskbar, and even the lock screen. With Tendfor, those integration points become even more meaningful. An agent working from home on a Windows PC receives a popping toast notification for an incoming support call, clicks it, and the Teams window opens directly to the contact center view. There’s no context switching, no dialer application to launch, and no confusion about which platform to use.

Moreover, because Tendfor relies on the same media stack that Teams uses for regular voice and video calls, it benefits from Microsoft’s ongoing optimizations for Windows. Features like network quality indicators, background noise suppression, and even spatial audio (on supported devices) work out of the box. And when Microsoft rolls out quality-of-life updates to Teams on Windows—say, enhanced support for snap layouts or better integration with Windows Copilot—those improvements automatically flow to Tendfor contact center agents.

IT admins also win. They manage voice routing, agent groups, and reporting through the same Microsoft Teams admin center and PowerShell modules they already know. Tendfor appears as an additional workload within the Teams ecosystem, not a separate island. This unification slashes training time and reduces the attack surface.

Broader Market Implications

NSWRL might be a niche sports organization, but its move reflects a broader disillusionment with legacy PBX and even first-generation cloud contact center products that were only loosely coupled to Teams. Endpoints like Audiocodes, Ribbon, or Oracle SBCs still sit in front of Teams Direct Routing, but the contact center logic itself used to require a standalone platform (think Five9, Genesys, or NICE inContact) with a Teams connector that often felt bolted on. Those connectors frequently failed during major Teams updates, leaving agents stranded.

Tendfor and a handful of other truly Teams-native CCaaS solutions—such as Landis Contact Center, Tendfor’s sibling products from AnywhereNow, and Microsoft’s own Digital Contact Center Platform—are erasing that friction. Gartner predicts that by 2027, 60% of new contact center deployments will be natively integrated with collaboration platforms like Microsoft Teams or Zoom, up from less than 30% in 2024. NSWRL’s fast implementation serves as a proof point that the approach isn’t just hype; it works for real organizations with immediate needs.

Cost Savings and Licensing Simplicity

One reason NSWRL could move so quickly is the licensing model. Rather than pay for a separate per-agent contact center license and an ongoing PABX maintenance contract, the league now likely benefits from a bundled Teams Phone license with a Tendfor add-on. Microsoft Teams Phone with Calling Plan sips from the same Microsoft 365 pool; Tendfor layers onto that with a consumption- or user-based model. This collapses the cost structure, turning a capital expenditure (PBX hardware, ISDN lines, maintenance) into an operational one that scales with the season. For a sports league that sees spikes in fan inquiries around matchdays, finals, and membership drives, that elasticity is invaluable.

AnywhereNow hasn’t disclosed specific NSWRL pricing, but industry benchmarks suggest total cost reductions of 40–60% over a three-year period compared to on-premise PBX with a traditional contact center add-on. And because the solution runs on Microsoft’s global Azure infrastructure, call quality and uptime often exceed what a small-to-mid-sized organization could achieve on its own.

Feedback from the Field

While NSWRL has yet to publish detailed metrics, early signals from similar migrations paint a bright picture. Users report that agent onboarding time drops from days to hours, as the Teams interface is already second nature. Supervisors praise the ability to monitor queues and barge into calls from their own Teams windows during a live match, all without VPN or special hardware.

One potential pitfall: reliance on internet connectivity. A pure cloud telephony model means that if an agent’s home broadband or the stadium’s network fails, phone access goes down. NSWRL likely addressed this through Microsoft’s survivability features, such as Survivable Branch Appliances (SBAs) for Teams Direct Routing, which can provide local PSTN connectivity at key sites even when internet is lost. For a stadium or training facility, having an on-site SBA ensures that emergency and essential calls still go through.

What This Means for Windows and Microsoft 365 Advocacy

For the Windows community, NSWRL’s story is a tangible case study of why Teams and Microsoft 365 have become central to modern communication. It demonstrates that Voice over IP isn’t just about shaving off long-distance charges; it’s about a platform play that binds together identity, collaboration, telephony, and line-of-business software into a unified desktop experience. The more workloads that converge into Teams, the stickier the entire Microsoft stack becomes for organizations—and the more value Windows devices deliver.

Think about it: an agent using a Windows 11 PC with Teams and Tendfor can simultaneously manage a call, look up customer history in Dynamics 365, consult a colleague via chat, and even share a screen—all within the same application shell. No alt-tabbing, no mismatched UI paradigms. And because Windows handles peripheral management (headsets, cameras, displays), the entire setup is plug-and-play.

Lessons for Other Organizations Contemplating a PABX Exit

NSWRL’s experience offers a blueprint for others still shackled to on-premise dial tone:

  • Audit your existing Teams investment. Many organizations already hold Microsoft 365 E5 or Business Voice licenses that include Teams Phone capabilities. Adding a native contact center becomes a natural extension.
  • Prioritize deployment speed over feature parity. Rather than spend months replicating every legacy PBX feature, map the top customer journeys and launch with those. NSWRL likely targeted core inbound support first, then layered on advanced routing and analytics.
  • Lean on the partner ecosystem. AnywhereNow, Landis, and other players bring two decades of telephony expertise to Teams. They understand signaling protocols (SIP, WebRTC) and media handling in ways that generic cloud providers do not.
  • Test resilience before cutover. No matter how robust the platform, real-world failover tests—pulling the internet on a live call, for instance—build confidence and expose gaps.

The Road Ahead

With the PABX out of the picture, NSWRL can now focus on refining its fan and partner interactions. Upcoming enhancements could include AI-powered virtual agents that handle repetitive queries ("What time does the gate open?") and hand off complex issues to human agents with full context. Microsoft’s Copilot, now deeply woven into Teams for chat and meeting summarization, could eventually assist contact center agents by surfacing suggested talking points or answers based on previous interactions.

Additionally, as NSWRL collects more interaction data, the organization—and by extension the rugby community—will gain valuable insights into fan sentiment, ticket-buying patterns, and support bottlenecks. Because the data resides within the Microsoft ecosystem, it can be mashed up with CRM and marketing automation for a 360-degree fan view.

Final Take

NSWRL’s switch from rack-mounted PABX to Teams-native Tendfor isn’t just a telecom refresh; it’s a strategic choice to put collaboration and customer experience at the heart of operations. Windows and Microsoft 365 users—whether you’re an IT pro looking for your next migration argument or a rugby fan who simply wants a quicker answer to “How do I get to the stadium?”—should take note. This is what modern communication looks like: fast, integrated, and finally free of the blinking PBX in the basement.