Avaya

Avaya is a multinational technology company specializing in business communications, contact center, and unified communications solutions. Headquartered in Morristown, New Jersey, Avaya is one of the oldest and largest vendors in the contact center industry, with an installed base estimated at over 100,000 customer locations globally. The company has undergone significant financial restructuring and strategic pivots, including two Chapter 11 bankruptcy filings, while maintaining one of the largest contact center deployments in the world. Avaya's current strategy centers on the Avaya Experience Platform (AXP), a cloud-based CCaaS offering, while continuing to support its massive on-premises installed base.

Company History

Avaya's roots extend back to the original Bell System. The company's lineage traces through Western Electric, AT&T Technologies, and Lucent Technologies before Avaya was spun off as an independent company in 2000.

Key milestones:

• 2000: Avaya spun off from Lucent Technologies as an independent company focused on enterprise communications. Inherits a massive global installed base of PBX and ACD systems, including the industry-dominant Definity/Communication Manager platform.
• 2001-2006: Establishes market leadership in enterprise contact center with Avaya Aura and the Avaya Communication Manager (ACM) platform. Acquires several companies to expand capabilities.
• 2007: Acquired by private equity firms Silver Lake Partners and TPG Capital for approximately $8.2 billion in a leveraged buyout that loads the company with significant debt — a financial burden that would shape Avaya's trajectory for years.
• 2009: Acquires Nortel Networks' enterprise solutions division for $900 million, adding the Nortel CS1000 and Symposium/AACC contact center product lines and significantly expanding the installed base.
• 2014: Launches Avaya Breeze, an application development platform for customizing communications solutions. Continues on-premises dominance but faces growing cloud competition.
• 2017: Files for Chapter 11 bankruptcy protection, citing $6.3 billion in debt from the 2007 leveraged buyout. Emerges from bankruptcy later that year with reduced debt and a stated commitment to cloud transformation.
• 2018-2019: Acquires Spoken Communications, a cloud contact center provider, as the foundation for its CCaaS offering. Partners with RingCentral in a strategic arrangement (Avaya Cloud Office) for UCaaS, acknowledging the cloud transition challenge.
• 2020: Avaya OneCloud CCaaS launched, built on the Spoken Communications acquisition. COVID-19 pandemic creates urgency among Avaya's installed base to consider cloud migration or remote enablement.
• 2021: Rebrands cloud offerings under Avaya OneCloud umbrella. Reports growing cloud revenue but overall revenue continues to decline as on-premises maintenance contracts shrink.
• 2023: Files for Chapter 11 bankruptcy protection for the second time, citing continued debt challenges and the ongoing difficulty of transitioning a large on-premises business to cloud revenue models. Emerges from bankruptcy with a restructured balance sheet and new leadership.
• 2024: Launches the Avaya Experience Platform (AXP) as the primary cloud contact center offering. Articulates an "innovation without disruption" strategy, emphasizing that existing on-premises customers can adopt cloud capabilities incrementally without forced migration.
• 2025: Continues executing the AXP strategy. Partners with third-party AI providers to accelerate AI capability delivery. Focuses on hybrid deployment models that bridge on-premises and cloud.

Platform Overview

Architecture

Avaya's contact center portfolio spans multiple architectural generations:

Avaya Experience Platform (AXP): The current-generation cloud CCaaS platform, available in both public cloud (AXP Public Cloud) and on-premises/private cloud (AXP On-Prem) variants. AXP Public Cloud is a multi-tenant SaaS offering. AXP On-Prem enables organizations to run cloud-equivalent capabilities in their own data centers, addressing regulatory, security, or hybrid deployment requirements.

Avaya Aura (Communication Manager + Contact Center): The legacy on-premises platform still running in thousands of enterprise environments. Built on a SIP-based architecture with the Avaya Aura Communication Manager as the core telephony engine and various contact center applications layered on top (Elite Multichannel, Oceana, Proactive Outreach Manager).

Avaya Aura Contact Center (AACC): Inherited from the Nortel acquisition, this is a separate contact center platform with its own architecture and customer base, primarily in government and Canadian enterprise markets.

Deployment Model

Avaya offers the broadest deployment flexibility among major contact center vendors:

• AXP Public Cloud: Multi-tenant SaaS, subscription licensing.
• AXP On-Prem: Cloud software running in customer-managed infrastructure (on-premises or private cloud).
• Hybrid: Combinations where some capabilities run in the cloud while voice processing or specific functions remain on-premises.
• Legacy on-premises: Continued support and enhancement of Avaya Aura-based deployments.

Pricing: Varies by deployment model. AXP Public Cloud uses per-agent subscription licensing. On-premises deployments use traditional perpetual licensing with maintenance contracts. Hybrid models combine elements of both.

Core Capabilities

Routing

Avaya's routing heritage is one of its strongest assets. Avaya Elite (formerly Expert Agent Selection) is widely regarded as one of the most sophisticated ACD routing engines in the industry:

• Skills-based routing with conditional logic and complex routing scripts (vectors and VDNs in Elite terminology).
• Best Service Routing (BSR) across multiple sites and platforms.
• Expected Wait Time (EWT) calculations integrated into routing decisions.
• In AXP, workflow-based routing using visual designers with AI-powered intent-based routing capabilities.
• Support for complex routing logic that can consider dozens of variables simultaneously — a capability that mature Avaya operations have refined over decades.

Omnichannel Support

• Voice: Deep telephony capabilities including SIP, ISDN, T1/E1 connectivity, and extensive interoperability with carrier networks.
• Digital channels: Email, web chat, SMS, social media, and messaging channels available through AXP and the legacy Oceana platform.
• Outbound: Predictive, preview, and progressive dialing with campaign management through Proactive Outreach Manager and AXP outbound.
• Video: Video-capable through AXP and integration with Avaya's broader communications portfolio.
• Self-service: IVR through Avaya Experience Portal (formerly Avaya Aura Experience Portal/Voice Portal) and Avaya Conversational Intelligence for AI-powered self-service.

Artificial Intelligence and Automation

Avaya's AI strategy has evolved to leverage partnerships alongside native development:

• Avaya AI Agent: Virtual agent capabilities for voice and digital self-service.
• Agent assist: Real-time transcription, sentiment analysis, and knowledge suggestions during live interactions.
• Analytics: Speech and text analytics, with capabilities delivered through both native features and technology partnerships.
• AI integrations: Open architecture supporting integration with third-party AI platforms (Google CCAI, Microsoft, and others).
• Noise removal: AI-powered background noise cancellation for agent and customer audio.

Avaya's AI capabilities are generally less mature than those of cloud-native competitors like NICE, Genesys, or Talkdesk. The company has focused on partnership-based AI delivery rather than building all capabilities natively, which provides flexibility but can result in less seamless integration.

WFM Integration

Historical Context

Avaya has a long and deep relationship with the WFM industry. For decades, Avaya's ACD platforms (Definity, Communication Manager, Elite) were the most widely integrated contact center platforms in the WFM market. Virtually every major WFM vendor — NICE (IEX), Verint (Blue Pumpkin), Aspect (TCS/eWFM), Calabrio, and others — built their earliest and most mature ACD integrations against Avaya's data interfaces.

Data Interfaces for WFM

Avaya provides several data feeds critical for WFM integration:

• CMS (Call Management System): Avaya's historical reporting database is one of the most established ACD reporting systems in the industry. CMS provides interval-level data (agent, skill, VDN, trunk group statistics) that WFM platforms use for forecast model building. Available in CMS Supervisor (client application) and CMS Web reporting interfaces.
• Real-Time Transport: JTAPI and TSAPI interfaces provide real-time agent state data critical for WFM adherence monitoring.
• AES (Application Enablement Services): Middleware providing CTI, device control, and event notification used by WFM platforms for real-time data feeds.
• DMCC (Device, Media, and Call Control): API for programmatic control and monitoring of telephony resources.

AXP WFM Integration

The Avaya Experience Platform provides updated integration mechanisms:

• APIs: RESTful APIs for agent state, queue metrics, and interaction data suitable for WFM platform integration.
• Webhooks and event streams: Real-time event notification for agent state changes and contact events.
• Partner ecosystem: AXP maintains integrations with major WFM vendors, though the depth of these cloud-based integrations is still maturing compared to the decades-old on-premises interfaces.

WFM Practitioner Considerations

• Legacy integration maturity: The on-premises Avaya + WFM integration is the most battle-tested combination in the industry. WFM practitioners managing Avaya Elite environments benefit from mature, well-documented integration patterns.
• Migration impact on WFM: Moving from Avaya on-premises to AXP (or any cloud platform) fundamentally changes WFM integration. Historical CMS data, real-time feed architectures, and agent state mappings all require reconfiguration. WFM teams should be involved early in any Avaya migration planning.
• Dual-platform operations: Organizations running hybrid Avaya environments (some sites on Elite, some on AXP) may need to manage WFM integration across two different data architectures simultaneously.
• CMS data continuity: Long-running CMS databases contain years of historical data critical for WFM forecasting. Migration planning must address how this historical data will be preserved or transitioned.
• Agent state complexity: Avaya's AUX (auxiliary) work state model is more granular than many cloud platforms. WFM systems built around Avaya's detailed AUX state taxonomy may need remapping when transitioning to AXP or a competing platform.

Target Market

• Large enterprises with existing Avaya deployments: The primary market. Organizations running Avaya on-premises that need cloud capabilities but want to avoid disruptive rip-and-replace migrations.
• Regulated industries: Financial services, healthcare, and government organizations that require on-premises or hybrid deployment options for compliance reasons.
• Global enterprises: Organizations with extensive multi-site, multinational deployments where Avaya's global presence and established local support infrastructure provide value.
• Contact centers with complex routing requirements: Operations that have built sophisticated routing logic on Avaya Elite that would be difficult or impossible to replicate on less flexible platforms.

Avaya is not typically chosen for new, greenfield contact center deployments. The company's value proposition is strongest with organizations that already have Avaya infrastructure and want a modernization path that does not require wholesale platform replacement.

Key Differentiators

• Installed base and ecosystem: The largest enterprise contact center installed base in the world, with deep integration into enterprise communication infrastructure and an extensive partner ecosystem.
• Deployment flexibility: Unique ability to offer public cloud, private cloud, on-premises, and hybrid deployment models from a single vendor — critical for organizations with regulatory constraints or complex migration requirements.
• Routing sophistication: Avaya Elite's routing engine remains one of the most capable in the industry for complex, multi-variable routing scenarios.
• "Innovation without disruption" strategy: The ability to adopt new capabilities incrementally without forced platform migration resonates with large enterprises that cannot afford operational disruption.
• Telephony heritage: Deep telephony expertise and carrier-grade voice infrastructure built over decades.

Limitations and Considerations

• Financial history: Two Chapter 11 bankruptcies create legitimate vendor viability concerns. While the restructured company has reduced debt and new leadership, the financial history is a risk factor that procurement and IT leadership must evaluate.
• Cloud maturity: AXP Public Cloud is less mature than competing CCaaS platforms from vendors born in the cloud (Genesys Cloud, NICE CXone, Five9, Talkdesk). Feature parity with leading cloud platforms has not been fully achieved.
• Innovation velocity: The burden of maintaining legacy platforms while simultaneously building cloud capabilities means Avaya's pace of innovation on AXP may lag behind cloud-native competitors who can focus resources entirely on a single platform.
• AI capabilities: Avaya's native AI features are less comprehensive than those of competitors who have invested heavily in proprietary AI development. The partnership-based approach provides capability but may result in less seamless experiences.
• Migration complexity: Despite the "innovation without disruption" message, actual migration from legacy Avaya to AXP is not trivial. Complex routing scripts, CTI integrations, reporting customizations, and WFM configurations all require rework.
• Talent pool: As the Avaya-specialized workforce ages and cloud-native skills become predominant, finding experienced Avaya administrators and developers is increasingly difficult.
• Market perception: The bankruptcy history and competitive narrative from cloud-native vendors have created a perception challenge that affects Avaya's ability to win new customers, even when the technology meets requirements.

See Also

• Contact Center Technology Landscape
• Contact Center as a Service
• Workforce Management Software
• Automatic Call Distribution
• Cloud Migration in Contact Centers
• On-Premises Contact Center Systems
• Interactive Voice Response