CallTower and its President and CEO, Bret England, have announced recognition through the Innovation Excellence Award 2026, a distinction positioned around the company’s work in Unified Communications, Contact Center and Customer Experience platforms, managed voice, AI-enabled engagement, and professional services. For Windows-centric organizations, the announcement matters less as a standalone trophy than as a signal of where enterprise communications providers are concentrating their investments: deeper integration across Microsoft Teams, cloud telephony, customer-service tooling, and global operational support.
The recognition arrives at a point when business communications are no longer confined to a PBX replacement project or a video-meeting license. Enterprises increasingly expect a coherent strategy for employee calling, messaging, meetings, customer interactions, security, reporting, onboarding, and support. CallTower’s pitch is that it can act as the connective layer across these systems rather than require customers to standardize exclusively on one collaboration vendor.
That proposition is attractive, particularly to large organizations whose communications estates have grown organically through acquisitions, regional deployments, legacy carrier agreements, and line-of-business contact centers. Yet the same breadth that can differentiate a managed communications provider also creates a demanding execution challenge. Supporting multiple platforms, voice infrastructures, AI capabilities, and compliance requirements is valuable only when the resulting service feels simpler to the customer than operating the components independently.

Futuristic global call center with cloud communications, analytics dashboards, security icons, and headset agents.Overview: Recognition Built Around Communications Convergence​

The Innovation Excellence Award 2026 recognizes CallTower and Bret England for the company’s stated focus on simplifying enterprise communications and modernizing customer engagement. CallTower describes its portfolio as spanning Unified Communications, Contact Center/Customer Experience, global enterprise voice, managed services, and professional services.
At the center of that message is a familiar enterprise IT problem: collaboration platforms are widespread, but communications operations remain fragmented. A business may use Microsoft Teams for internal collaboration, maintain a separate contact center platform for customer support, buy PSTN connectivity through regional carriers, and rely on multiple partners for deployment, device management, network readiness, and support.
This is where a communications managed service provider can make its case. Rather than asking IT teams to maintain distinct relationships and processes for every layer, a provider such as CallTower aims to unify technology selection, deployment, administration, voice connectivity, user adoption, and ongoing management.
For WindowsForum readers, the most immediately relevant component is CallTower’s relationship with the Microsoft Teams calling ecosystem. Teams remains a central collaboration environment for organizations standardized on Microsoft 365, but enterprise voice introduces requirements that go beyond chats and meetings. Number management, emergency calling, call routing, survivability, carrier services, session border control, compliance, analytics, and service assurance all require careful planning.
CallTower’s recognition should therefore be read as an endorsement of its broader managed communications strategy, not as proof that every promised capability will fit every deployment. Awards can highlight momentum and brand positioning, but organizations still need to measure technical compatibility, support quality, geographic availability, commercial terms, and operational accountability against their own requirements.

Why Unified Communications Has Become an Enterprise Architecture Issue​

Unified Communications, often shortened to UC or UCaaS, initially gained traction as a way to bring voice, video, messaging, presence, and conferencing closer together. In practice, the modern UC environment is now deeply tied to endpoint management, identity, network design, security policy, and business continuity.
A Microsoft 365 organization may already have the collaboration foundation in place through Teams. The next decision is often whether to use native calling options, direct routing, operator connectivity, third-party voice services, or a managed hybrid model. That choice can affect every employee who makes or receives external calls.

Teams Calling Is More Than a License Assignment​

Turning on Teams Phone is often straightforward at a basic level. Delivering a resilient enterprise calling service across multiple regions is more complicated. Businesses need to account for number porting, local regulatory obligations, emergency-services requirements, call-quality monitoring, routing policies, user provisioning, and support escalation.
These are the areas where an experienced provider can contribute real value:
  • PSTN connectivity for Teams calling across supported regions
  • Direct Routing or operator-based connectivity options
  • Number procurement and porting coordination
  • Call routing and survivability planning
  • Emergency calling configuration
  • Service monitoring and incident management
  • Voice policy administration
  • Integration with legacy phone systems or analog devices
  • Migration planning for acquired companies and remote sites
CallTower’s model emphasizes managed communications across Teams as well as other collaboration and contact center platforms. That multi-platform approach is particularly relevant for enterprises that cannot realistically force every department, partner, or acquired subsidiary onto one technology stack overnight.

The Real Goal: Reducing Operational Complexity​

The strongest idea in CallTower’s announcement is not the promise of another communications platform. It is the promise to make a complicated estate more manageable.
Modern IT teams are under pressure to reduce the number of isolated systems they operate. They want repeatable provisioning, consolidated operational visibility, predictable escalation paths, and a partner that understands the interaction among carriers, cloud providers, contact center platforms, identity services, endpoints, and networks.
A single accountable provider can reduce coordination overhead. It can also create a more standardized operating model for onboarding, moves, adds, changes, and troubleshooting. For companies with distributed locations, this can make a measurable difference in how quickly IT responds to communications needs.
However, consolidation also increases dependence on the chosen provider. If one partner becomes responsible for multiple critical functions, that partner’s service quality, transparency, financial stability, support coverage, and technical competence become more important than ever.

CallTower’s Platform-Agnostic Strategy​

CallTower describes itself as platform-agnostic, with services associated with Microsoft Teams, Webex by Cisco, Zoom, Five9, Genesys, AI technologies, and additional enterprise-grade capabilities. The strategic appeal is clear: many customers do not want to be pressured into abandoning a collaboration or customer engagement platform that already works for them.
The company’s approach is based on the idea that customers should select the tools best aligned to their requirements while using CallTower as a unifying service partner. In theory, this avoids a common problem in cloud communications: a vendor’s portfolio can dictate the architecture before business needs have been fully assessed.

Choice Can Be an Advantage​

Organizations have good reasons to use more than one communications platform. Microsoft Teams may be the standard productivity client, while a customer-support operation may require the routing, workforce management, analytics, digital channels, or AI features available through a specialized Contact Center as a Service platform.
Likewise, a business may have regional teams committed to Webex or Zoom, perhaps because of prior investments, external partner workflows, industry preferences, or merger activity. A managed service provider that can support these variations gives IT leadership a path toward gradual rationalization rather than abrupt replacement.
The potential benefits include:
  • Preserving existing investment in familiar platforms
  • Supporting phased migrations instead of disruptive cutovers
  • Matching contact center technology to business requirements
  • Maintaining flexibility after acquisitions
  • Avoiding unnecessary vendor lock-in
  • Building a global voice strategy around diverse collaboration environments
  • Centralizing support and professional services despite platform variety
This model aligns well with the reality of enterprise IT. Standardization is valuable, but total uniformity is often unrealistic.

Choice Also Creates Complexity​

The counterargument is just as important. A multi-platform communications environment can create significant administrative and security overhead. Every additional platform brings its own licensing rules, feature boundaries, identity integration methods, analytics model, support process, and change cadence.
A platform-agnostic partner must prove that it is genuinely simplifying these differences rather than merely reselling a collection of products. The key test is whether the customer receives integrated operations and clear accountability.
Organizations evaluating this type of offering should look closely at:
  1. Administration experience
    Can IT teams complete common tasks through a consistent operational process, or must they navigate multiple vendor consoles and support channels?
  2. Identity and lifecycle management
    How well does the solution integrate with Microsoft Entra ID, Microsoft 365 groups, HR-driven provisioning, and existing identity governance processes?
  3. Security boundaries
    Are access controls, logging, data retention, and third-party integrations governed consistently across each platform?
  4. Reporting and analytics
    Can leaders see a meaningful cross-platform view of calling quality, adoption, customer-service performance, and incident trends?
  5. Support ownership
    When a user’s call fails or a contact center integration breaks, is there one clear escalation path?
  6. Commercial clarity
    Are licensing, carrier charges, service fees, consumption costs, and professional-services engagements easy to understand before signing?
The award announcement speaks to CallTower’s vision and market direction. The real proof will be found in the customer experience of operating that vision at scale.

The Expanding Role of Contact Center and Customer Experience​

CallTower’s announcement gives prominent attention to CC/CX, an important indicator of how business communications are changing. Unified Communications historically focused on employees. Contact center technology focuses on how organizations interact with customers, patients, citizens, students, members, and partners.
The line between the two is increasingly blurred. A customer-service agent may need to consult a product expert through Teams, elevate a conversation to video, access CRM data, trigger workflow automation, use AI-driven summaries, and hand off work across departments. Those interactions cannot be optimized effectively when UC and customer engagement systems operate in complete isolation.

Integrating Internal Collaboration with External Engagement​

The promise of linking UC and CCaaS is compelling. It allows organizations to reduce the friction between frontline service teams and internal subject-matter experts.
Consider a support agent who receives a complex customer request. In a fragmented environment, the agent might place the customer on hold, send messages through a separate collaboration tool, search for an available specialist, and manually document the interaction. Integrated communications can make that workflow faster and more visible.
A well-designed UC and CC/CX environment can support:
  • Expert consultation through presence and collaboration tools
  • Customer interaction routing across voice and digital channels
  • Context sharing between CRM, contact center, and collaboration systems
  • Transcription, summaries, and knowledge retrieval
  • Faster escalation to technical or supervisory staff
  • More complete reporting on customer journeys
  • Improved support for remote and hybrid agents
For Windows-based business environments, the endpoint experience remains crucial. Agents and knowledge workers often use Teams, Outlook, Microsoft 365 applications, browsers, headsets, softphones, and business applications on managed Windows devices. Any communications strategy must work cleanly within that daily workflow rather than introduce another disconnected desktop experience.

Professional Services Are Not a Side Offering​

CallTower also emphasizes professional services, which may be one of the most consequential parts of its portfolio. Collaboration and contact center projects fail less often because a platform lacks features and more often because implementation details are underestimated.
A successful project needs thoughtful design around call flows, number migration, CRM integration, agent workflows, endpoint readiness, network performance, security controls, testing, training, and adoption. Businesses also need to plan for what happens after go-live: optimization, governance, support ownership, performance monitoring, and new feature adoption.
Professional services can be especially valuable in complex scenarios such as:
  • Moving a legacy PBX estate to Teams Phone
  • Consolidating multiple contact centers after an acquisition
  • Deploying global voice services across regions
  • Integrating CRM records with agent workflows
  • Creating resilient routing and disaster-recovery plans
  • Reworking customer journeys around AI assistance
  • Bringing legacy analog, paging, fax, or specialized devices into a modern architecture
The risk is that professional services can become a costly dependency if the platform is not designed for manageable day-two operations. Buyers should ensure that documentation, administrator training, change management, and internal ownership are built into the engagement from the beginning.

AI in Business Communications: Promise, Practicality, and Governance​

AI-enabled customer engagement is another central element of CallTower’s positioning. This is unsurprising. AI has moved quickly from a specialized capability to a major buying criterion across contact center and collaboration markets.
In practical terms, AI can support transcriptions, summaries, agent assistance, knowledge retrieval, sentiment indicators, quality management, conversation analysis, workflow automation, and customer self-service. The value proposition is not simply to automate more interactions, but to help employees and agents make better decisions with less administrative burden.

Where AI Can Deliver Value​

The most immediate AI use cases tend to be operational. An agent may receive a live suggestion based on the conversation, a supervisor may identify recurring issues from interaction analysis, and a support worker may receive an automatically generated summary at the end of a call.
Potential gains include:
  • Reduced after-call documentation time
  • Faster retrieval of internal knowledge
  • More consistent interaction summaries
  • Improved coaching and quality-management workflows
  • Better visibility into recurring customer issues
  • More efficient case routing
  • Assistance for multilingual or distributed teams
  • Increased access to self-service for routine requests
For organizations already invested in Microsoft’s ecosystem, the intersection between Teams, Microsoft 365, Copilot capabilities, business applications, and third-party CCaaS platforms will be a major architectural consideration. The important question is not whether AI can be added, but whether it can be introduced in a controlled, supportable, and measurable way.

AI Raises New Risks​

The AI narrative should be treated with appropriate caution. Automated summaries can omit nuance. Suggested responses can be wrong. Sentiment classifications can be unreliable in context. Knowledge tools can expose inappropriate data if permissions are poorly designed.
Customer-facing automation introduces additional risks. A conversational system that cannot identify its own limitations may frustrate customers, misstate policy, mishandle sensitive requests, or route issues incorrectly. In regulated industries, those problems can become operational or compliance concerns.
A responsible AI deployment should include:
  • Clear data classification and retention policies
  • Role-based access controls
  • Human review for high-impact decisions
  • Monitoring for inaccurate or harmful outputs
  • Clear escalation routes to human support
  • Testing across languages, accents, and customer scenarios
  • Defined ownership for knowledge sources
  • Transparent reporting on AI effectiveness and failure patterns
CallTower’s broad portfolio could help customers navigate the integration side of this work. But the organization deploying the tools remains accountable for governance, customer treatment, and regulatory obligations.

Bret England’s Role in the Company’s Direction​

The recognition also singles out Bret England, CallTower’s President and CEO. England has led the company’s strategic and operational direction as it has expanded from core Unified Communications into cloud collaboration, contact center, customer experience, and managed services.
Leadership recognition in this sector generally reflects more than individual visibility. It is tied to the company’s ability to identify market shifts, build partnerships, invest in service capacity, and translate a complex technology portfolio into a coherent customer proposition.
CallTower’s recent messaging strongly suggests that England’s strategy is centered on three themes:
  • Platform flexibility rather than a single-vendor mandate
  • Service depth across deployment, support, management, and professional services
  • Global communications enablement for organizations operating across multiple locations and regions
These priorities make sense in a market where enterprise customers want cloud flexibility but still need predictable accountability. The managed service provider occupies a critical middle ground between software vendors that supply platforms and IT departments that must make those platforms work in real environments.
The challenge for any CEO in this space is maintaining service quality while expanding the portfolio. Growth through new partnerships, geographic reach, or contact center capabilities can strengthen the business, but it can also expose inconsistencies in support processes and technical specialization. A multi-service provider must remain disciplined about operational maturity.

What the Award Does—and Does Not—Validate​

Industry awards can provide useful visibility. They can reinforce a company’s positioning, give sales teams a credible message, and recognize the work of employees who deliver complex services behind the scenes. For CallTower, the Innovation Excellence Award 2026 supports its claim that its strategy is aligned with the direction of enterprise communications.
Still, IT decision-makers should avoid treating an award as a substitute for technical due diligence.
The announcement identifies the award as recognizing vision, growth, and innovation, but it does not by itself provide detailed evaluation criteria, competitive benchmarking, service-level performance data, or a customer-by-customer assessment of deployment outcomes. That does not invalidate the recognition; it simply defines its limits.
A thoughtful evaluation should focus on evidence that directly affects the customer:
  • Demonstrated experience in the target countries and regions
  • Clear support coverage and escalation commitments
  • Proven Teams Phone and voice migration expertise
  • Contact center integration experience relevant to the chosen platform
  • Security, privacy, and compliance documentation
  • Implementation methodology and migration testing
  • References from organizations of comparable size and complexity
  • Transparent pricing and contractual accountability
  • Exit planning and portability of numbers, data, and configurations
In other words, recognition can open the door to a vendor conversation. It should not close the procurement process.

Why This Matters for Windows and Microsoft 365 Organizations​

For the Windows ecosystem, CallTower’s award announcement is significant because it reflects the growing importance of communications infrastructure around Microsoft Teams. Teams is not merely a meeting application in many organizations; it has become a workspace that touches voice, collaboration, scheduling, files, identity, endpoint policy, and increasingly, AI-assisted workflows.
Adding enterprise calling or customer-service integrations to Teams changes the operational stakes. A Teams outage, a routing fault, or a voice-quality problem can affect front-office revenue, customer support, emergency communications, and executive productivity. IT teams need partners that understand not only the platform but also the operational consequences of failure.
A managed service provider can bring expertise that is difficult to maintain internally, particularly for global deployments. But the provider relationship must be engineered as carefully as the technology itself.
The strongest fit for CallTower’s model may be organizations that need to modernize communications without forcing a total, immediate technology reset. Companies that operate Teams alongside other collaboration platforms, have complex voice requirements, run specialized contact centers, or require extensive professional-services support may see particular value in a provider designed around choice and integration.
Smaller organizations with simple domestic calling needs may find that a fully managed, multi-platform approach exceeds their actual requirements. The right answer depends on complexity, internal skills, regulatory exposure, geographic footprint, and the importance of customer interaction to the business.

The Bottom Line​

CallTower and Bret England’s Innovation Excellence Award 2026 recognition highlights a company pursuing one of the most important themes in enterprise technology: bringing together collaboration, cloud voice, contact center operations, AI-enabled customer engagement, and managed services without forcing customers into a single communications platform.
That strategy is relevant to Windows and Microsoft 365 environments, where Teams calling, identity integration, endpoint management, and customer-service workflows increasingly intersect. The potential upside is meaningful: fewer operational handoffs, better support for global voice, more flexible platform choices, and a stronger link between internal collaboration and customer experience.
The central test, however, remains execution. Innovation in business communications is not defined by how many platforms appear on a partner list. It is defined by whether the provider can make a complex environment easier to deploy, safer to operate, simpler to support, and more effective for employees and customers.
CallTower’s recognition strengthens its visibility in that competitive market. For enterprise IT leaders, it also underscores a broader reality: communications has become a strategic service layer, and the partners chosen to manage it now have a direct influence on productivity, customer engagement, resilience, and the long-term flexibility of the organization’s technology stack.

References​

  1. Primary source: Telecom Reseller / Technology Reseller News
    Published: 2026-07-22T15:58:28+00:00
  2. Related coverage: calltower.com