Avaya Contact Center

From WFM Labs

Avaya is a multinational technology company headquartered in Morristown, New Jersey, that has been a dominant force in enterprise communications and contact center technology for over two decades. Spun off from Lucent Technologies in October 2000,[1] Avaya built the largest installed base of on-premises contact center systems in the world — serving 90% of the US Fortune 100 and over 220,000 customer locations across 190 countries. The company has undergone two Chapter 11 bankruptcies (2017 and 2023) and is now executing a cloud pivot through its Avaya Experience Platform (AXP) while maintaining its massive on-premises install base.

Overview

Avaya Contact Center

Avaya's story is inseparable from the history of enterprise telephony. The company inherited Lucent's enterprise communications division, which itself descended from AT&T's legendary PBX business. For decades, Avaya's Aura platform and predecessor systems were the default contact center infrastructure for large enterprises, government agencies, and regulated industries.

The transition from on-premises dominance to cloud relevance has been turbulent:

  • 2000: Spun off from Lucent Technologies; IPO on NYSE
  • 2007: Taken private by Silver Lake Partners and TPG Capital in an $8.2 billion leveraged buyout — the debt from this deal haunted the company for over a decade
  • 2017: First Chapter 11 bankruptcy filing; emerged later that year with restructured debt
  • 2020-2022: Attempted cloud transformation with OneCloud brand; execution fell short of promises
  • 2023: Second Chapter 11 bankruptcy filing; emerged May 2023 as a private company with restructured debt and new leadership
  • 2024-2025: Relaunched cloud strategy around Avaya Experience Platform (AXP); announced minimum 200-seat requirement for AXP Public Cloud[2]
  • 2025-2026: Launched Avaya Infinity hybrid platform targeting large enterprise and public sector

Avaya matters to WFM practitioners not because of technology leadership — it has ceded that to NICE, Genesys, and Amazon — but because of the sheer scale of its installed base. Migration decisions from Avaya affect tens of thousands of contact center operations globally, and these migrations are among the most complex, high-risk projects a WFM team will face.

Core Capabilities

On-Premises Legacy

Avaya's on-premises contact center products remain in production at thousands of organizations:

  • Avaya Aura Contact Center: The flagship on-premises ACD with skills-based routing, IVR, and multimedia contact handling
  • Avaya Call Management System (CMS): Historical and real-time reporting — still the primary reporting platform for many Avaya contact centers
  • Avaya Workforce Optimization (WFO): Quality monitoring, recording, and basic WFM (though most Avaya customers use NICE WFM or Verint for WFM)
  • Avaya Communication Manager: The underlying PBX/ACD engine

Avaya Experience Platform (AXP)

AXP is Avaya's cloud contact center platform, available in three deployment models:

  • AXP Public Cloud: Multi-tenant cloud CCaaS (minimum 200 seats as of June 2025)
  • AXP Private Cloud: Dedicated cloud infrastructure for organizations requiring isolation
  • AXP On-Premises: Modernized on-premises deployment with cloud-connected AI and management

AXP capabilities include:

  • Omnichannel routing (voice, chat, email, messaging, social)
  • AI-powered virtual agents and agent assistance
  • Workflow automation
  • Real-time and historical analytics
  • Journey orchestration

Avaya Infinity

Launched in 2025-2026, Infinity is Avaya's hybrid architecture designed for organizations that want cloud benefits without full migration:

  • Combines on-premises call handling with cloud-based AI, analytics, and workflow automation
  • Targets large enterprise and public sector customers
  • Positions as "innovation without disruption" — acknowledging that many Avaya customers cannot or will not do a full cloud migration

Target Market and Deployment Model

Target Market

  • Large enterprise (1,000+ agents): Organizations with deep Avaya investment, complex integrations, and regulatory constraints
  • Government and public sector: Federal, state, and local agencies with security requirements and procurement constraints
  • Financial services: Banks and insurance companies with extensive Avaya PBX infrastructure
  • Healthcare: Hospital systems and health plans with Avaya telephony

Avaya has effectively conceded the sub-200 seat market with its AXP minimum requirement. Mid-market prospects are being directed to partners or alternative platforms.

Pricing Model

Avaya pricing is heavily customized based on deployment model:

  • AXP Public Cloud: Per-seat subscription pricing comparable to NICE CXone and Genesys Cloud
  • AXP Private Cloud: Higher per-seat costs reflecting dedicated infrastructure
  • On-premises: Perpetual licensing with annual maintenance (legacy model)
  • Hybrid (Infinity): Blended pricing combining on-premises maintenance with cloud service fees

Deployment Model

Avaya uniquely offers on-premises, private cloud, public cloud, and hybrid deployment options. This flexibility is simultaneously a strength (meets customer requirements) and a weakness (splits engineering investment across multiple architectures).

Key Differentiators

Installed base. No vendor in the contact center industry has Avaya's existing customer footprint. The 90% Fortune 100 statistic is from peak years, but the current install base remains massive and creates switching costs that sustain the business.

Hybrid flexibility. Avaya is the only major vendor genuinely supporting on-premises, private cloud, public cloud, and hybrid deployments. Organizations with regulatory, security, or political constraints preventing cloud migration have limited alternatives.

Enterprise telephony depth. Decades of PBX and ACD engineering created capabilities (failover, redundancy, carrier integrations, custom CTI) that cloud-native platforms are still catching up to in specific edge cases.

Government and defense. Avaya holds security certifications and has established relationships in government and defense sectors that cloud-native competitors struggle to replicate.

WFM Practitioner Perspective

What It Does Well

  • Stability for existing operations: Avaya on-premises systems are mature and reliable. WFM teams running Avaya ACD with NICE WFM or Verint have well-understood data flows, proven forecasting models, and stable historical data.
  • CMS reporting: Despite its age, Avaya CMS provides granular interval-level data that is well-understood by WFM analysts. The data model is documented, stable, and predictable.
  • Carrier-grade reliability: For organizations where downtime has direct financial or safety implications (emergency services, financial trading desks), Avaya's on-premises reliability remains a genuine advantage.

Where It Falls Short

  • Cloud WFM immaturity: AXP's workforce management capabilities are nascent compared to NICE CXone, Genesys Cloud, or even Talkdesk. Most Avaya cloud customers still need third-party WFM.
  • Innovation pace: Avaya's product development velocity has slowed significantly due to financial distress, leadership changes, and engineering investment spread across multiple architectures. Features that competitors ship quarterly take Avaya years.
  • Migration complexity: Moving from Avaya on-premises to any cloud platform (including AXP) requires rethinking routing logic, reporting, WFM data feeds, QA processes, and agent desktop configurations. These migrations routinely take 12-24 months for large operations.
  • Data continuity risk: Migrating away from Avaya often means losing years of historical CMS data that WFM forecasting models depend on. Data migration and translation is a significant workstream.
  • Ecosystem uncertainty: Avaya's financial history creates legitimate uncertainty about long-term platform viability. WFM practitioners must factor vendor risk into technology strategy.
  • Analyst positioning: Avaya has fallen in Gartner and Forrester assessments, reflecting capability gaps relative to cloud-native competitors. This affects procurement team confidence.

Migration Guidance for WFM Teams

Avaya migrations are among the highest-stakes projects a WFM team will face. Key considerations:

  1. Data preservation: Extract and warehouse historical CMS data (minimum 24 months at interval level) before decommissioning. This data feeds forecasting models on whatever platform replaces Avaya.
  2. Routing logic translation: Avaya routing vectors do not translate directly to cloud routing logic. Document current routing intent (not just configuration) before migration.
  3. WFM platform decision: If currently running NICE WFM or Verint with Avaya ACD, the CCaaS migration is an opportunity to re-evaluate WFM platforms — but do not change both simultaneously.
  4. Parallel running: Plan for 30-60 days of parallel operation with both Avaya and the target platform running simultaneously. This protects forecast accuracy during transition.
  5. Agent scheduling continuity: Ensure agents' schedules, preferences, seniority data, and accrual balances transfer cleanly to the new system.

Net Assessment

Avaya is a legacy platform in managed decline for new deployments but remains relevant because of its enormous installed base. WFM practitioners in Avaya shops should be planning migration strategies — the question is when and to what, not whether. For new deployments, no WFM practitioner should recommend Avaya over NICE CXone, Genesys Cloud CX, or Amazon Connect. For existing Avaya operations, the priority is building a migration roadmap that preserves data continuity, operational stability, and WFM capability maturity during transition.

Integration Ecosystem

WFM: NICE WFM (most common pairing), Verint, Calabrio WFM — Avaya customers almost universally use third-party WFM

Quality: NICE Nexidia, Verint QA, Calabrio QM

CRM: Salesforce, Microsoft Dynamics 365, ServiceNow

UCaaS: Avaya Aura (native), integration with Microsoft Teams

Analytics: Avaya CMS (native), third-party BI tools via data export

Migration targets: Genesys Cloud CX (most common), NICE CXone, Amazon Connect, Cisco Webex Contact Center

Maturity Model Position

Avaya's position in the maturity model depends heavily on deployment type:

  • On-premises (with third-party WFM): Supports Levels 2-4 when paired with NICE WFM or Verint. The ACD itself is not a constraint — the WFM platform and organizational maturity determine achievable level.
  • AXP Cloud: Currently supports Levels 2-3. Cloud WFM and analytics capabilities are developing but not yet mature enough for advanced optimization.
  • Hybrid (Infinity): Potentially Levels 2-4, depending on which cloud capabilities are activated alongside on-premises infrastructure.

The ceiling for Avaya-based operations is typically set by the third-party WFM and analytics platforms layered on top, not by Avaya's ACD itself.

See Also

References

  1. ↑ Avaya company history. Wikipedia, 2026.
  2. ↑ Avaya to Stop Supporting Public Cloud Contact Centers with Fewer Than 200 Seats. CX Today, February 2025.
Retrieved from "https://wiki.wfmlabs.org/w/index.php?title=Avaya_Contact_Center&oldid=2998"