InflectionCX Market Analysis | February 2026

What Avaya Infinity Is and Why It Exists

Avaya Infinity is a cloud contact center platform that launched in April 2025 as the successor to the Avaya Experience Platform (AXP). The rebrand isn't cosmetic. Infinity incorporates technology from Avaya's May 2024 acquisition of Edify, a CCaaS/CPaaS company whose no-code workflow engine now sits at the core of the platform. Edify's founder became Avaya's SVP of Product; Edify's CTO became Avaya's CTO. That tells you how central the acquisition was.

The platform runs on Kubernetes. The same containerized services deploy to public cloud (AWS, Azure, GCP), private cloud, on-premises hardware, or hybrid configurations connecting legacy Avaya systems with new cloud capabilities. That deployment flexibility is the main reason Infinity exists. Avaya's customer base includes roughly 90% of the Fortune 100, many of them running on-premises Aura and Contact Center Elite systems that can't move to a multi-tenant cloud overnight. Infinity gives those organizations a path to modernize without tearing out infrastructure that works.

If you're evaluating contact center platforms right now, Infinity matters because it's the only enterprise-grade option that genuinely supports on-premises, cloud, and hybrid deployment from the same codebase. Whether that matters to you depends on your constraints.

Deployment Models

Public Cloud is multi-tenant SaaS with the fastest feature updates. One important detail: as of June 2025, the public cloud option requires a 200-seat minimum. That cuts out roughly 70% of contact centers. Avaya is explicitly positioning this as an enterprise product.

Private Cloud provides a dedicated instance managed by Avaya with compliance certifications including HIPAA, PCI-DSS, and SOC 2. You get more control over data residency and customization. Feature updates roll out slower. Cost is higher.

Hybrid connects on-premises Aura or Elite infrastructure with cloud capabilities through Avaya's Hybrid Cloud Gateway. Agents get a single desktop that handles legacy voice and Infinity's digital channels. This is the migration path for organizations with significant Avaya hardware investment that need to add digital channels and AI without a forklift upgrade.

On-Premises runs the full Infinity stack on your own infrastructure using Azure Local, AWS Outposts, or Google Distributed Cloud. Same containerized platform, your datacenter. This matters for government, defense, and financial institutions with strict data sovereignty requirements.

Unified Routing Across Legacy and Cloud

In hybrid deployments, Infinity maintains state awareness of all agents across both the legacy ACD and the cloud routing engine. An agent logged into the hybrid desktop appears available in both systems. A customer who starts a web chat and escalates to voice stays with the same agent, with full context.

This is architecturally different from what competitors offer. Genesys Cloud requires a complete migration for unified routing. Cisco Webex CC can integrate with Unified Communications Manager but assumes a new deployment for full capability. Avaya is the one explicitly enabling gradual migration, keeping existing voice routing untouched while adding new capabilities on top.

What we can't independently verify is how this performs under production load. What happens when the Hybrid Cloud Gateway loses sync? What are the failure modes? How does latency behave across the on-prem/cloud boundary? Your proof-of-concept needs to answer those questions before you sign.

AI Strategy

Avaya has taken an AI-agnostic approach. Rather than building proprietary models, Infinity supports the Model Context Protocol (MCP), an open standard that lets AI systems connect to external tools and data through a common interface. MCP support was announced in July 2025.

Infinity operates as both MCP server and client. As a server, the platform exposes contact center data (agent availability, interaction history, routing rules) to external AI models in a structured format. As a client, it consumes data from external systems. The orchestration layer can route to different LLMs based on intent or customer segment: a simple FAQ gets a cheaper model; a complex complaint escalates to a more capable one.

The practical reality is that MCP adoption is still early. Most enterprises are trying to get one model working reliably, not orchestrating across three. The AI-agnostic positioning is a reasonable hedge against an uncertain landscape, but it's a future-proofing play, not an immediate operational advantage. If you need AI capabilities working in production today, NICE CXone and Genesys Cloud have more mature native offerings.

Avaya's broader AI approach relies on partners: Cognigy for conversational AI, Verint for CX automation, and an enterprise data governance partnership with Databricks. This gives you best-of-breed flexibility but means Avaya's AI roadmap depends on partners it doesn't control.

The API Ecosystem

Infinity is API-first. Every capability in the platform is exposed through REST APIs, and the agent desktop, admin console, and analytics dashboards all consume the same APIs available to your developers. Real-time events come through WebSocket streams or webhooks. Authentication uses OAuth 2.0 with JWT tokens scoped per capability.

The API categories cover communication (call control, SIP header manipulation, unified messaging), routing and orchestration (attribute-based routing, skill matching, workflow triggers), agent workspace (state control, CRM screen pops, custom panels), analytics (real-time queue stats, historical records, AI sentiment scoring), and administration (user provisioning, skill assignment, IVR deployment).

Rate Limits

Enterprise customers can negotiate higher limits. Design batch operations and caching from the start.

CRM Integration

Native connectors exist for Salesforce, Microsoft Dynamics 365, and ServiceNow. The Salesforce integration uses an APEX package and Lightning component for native in-platform call handling with automatic screen pops and interaction logging. For unsupported CRMs, a Custom CRM Service framework provides equivalent integration capability. Pre-built connectors save four to six weeks of integration work; custom CRM integration requires backend development but uses the same underlying APIs.

Vendor Stability

Any serious evaluation of Avaya needs to address the financial picture. Avaya has been through two Chapter 11 bankruptcies in six years (2017 and 2023). The signals since the second emergence are mixed.

What's Improving

Avaya emerged from the 2023 bankruptcy in 76 days, shedding $3.75 billion in debt. Fitch upgraded the credit rating from CCC+ to B- Stable in November 2025. The company has met or exceeded forecasts for five consecutive quarters. About 76% of revenue comes from recurring contracts. Enterprise retention is 97% among large customers. The debt-to-revenue ratio is now among the best in the industry, and the installed base is still massive: roughly 90,000 customers and six million contact center agents globally.

What's Concerning

Revenue is still declining through the cloud transition. Fitch projected high single-digit to low double-digit revenue decline in FY25 from UC customer attrition, regional exits, and subscription transition effects. Cost-cutting has been deep and sustained: 180 positions cut in July 2024, more in November 2024, continued cuts in early 2025, and then voluntary exit packages offered to the entire workforce in mid-2025. In October 2025, Avaya moved to close US billing and customer service operations and offshore them, which triggered a CWA union dispute.

Under CEO Patrick Dennis (who replaced Alan Masarek in September 2024), Avaya adopted a "G1500" strategy: focus on the top roughly 1,500 global enterprise and public sector customers. Think of it as the Broadcom model applied to contact center. Protect wallet share in the installed base, reduce investment in acquiring new customers.

What This Means for You

If you're already a large Avaya enterprise customer, you're the priority. The financial trajectory is genuinely improving, and the G1500 strategy means resources are focused on keeping you.

If you're evaluating Avaya as a new customer, understand that you're not the focus of their go-to-market investment. That doesn't mean they won't sell to you, but your negotiating position and support experience may reflect that priority. Build contractual protections around support SLAs, source code escrow, and data portability.

Competitive Comparison

Avaya Infinity vs. Genesys Cloud CX

Genesys Cloud is probably the most complete all-in-one CCaaS on the market. Over 3,000 REST APIs, a large AppFoundry marketplace, $1.9 to $2.2 billion in ARR, and net revenue retention above 120%. Its AI is native and deeply integrated: predictive engagement, workforce optimization, and journey analytics all built in.

Genesys assumes cloud-first. Multi-tenant SaaS with a private edition for large deployments, but no genuine on-premises option. If you can operate entirely in the cloud and want mature, built-in AI with a large developer ecosystem, Genesys is the benchmark. If you need hybrid or on-prem deployment, or you want to avoid locking into a single AI vendor, Infinity has the architectural edge.

Avaya Infinity vs. NICE CXone

NICE holds the strongest analyst position in the market. Gartner's only Customers' Choice designation, Leader in every major evaluation for a decade, and the broadest native capability set including workforce engagement management. Over 25,000 customer organizations, 91% recommendation rate on Gartner Peer Insights.

NICE uses purpose-built, proprietary AI models trained specifically for CX. That means faster time to value, but less flexibility if you want to bring your own models or fine-tune for specific scenarios. NICE is the right choice when feature breadth and native WEM matter most. Infinity is the right choice when deployment flexibility matters more than feature breadth.

Avaya Infinity vs. Amazon Connect

Amazon Connect is the pricing disruptor. Pay-per-use (per minute of voice, per message) means no seat licenses, and customers consistently report 30% to 50% lower total cost of ownership. AWS made Leader in the 2024 Gartner MQ, which tells you how fast enterprise adoption has moved.

The tradeoff is that Connect requires more assembly. It integrates deeply with the AWS AI stack (Lex, Q, Bedrock), but the platform assumes you're comfortable building on AWS. If you're already invested in AWS and have technical resources, Connect's TCO advantage is real. If you need a more complete out-of-the-box experience or on-prem capability, Infinity is the better fit.

Avaya Infinity vs. Five9

Five9 has built a strong position in the mid-market and is pushing upmarket with its Genius AI engine. The platform is straightforward to deploy, and its IVA capabilities are solid. For organizations between 100 and 1,000 agents who want AI-powered CX with lower implementation complexity, Five9 is a serious contender.

The limitations show at scale. Workforce management isn't as mature as NICE or Genesys, and the developer ecosystem is smaller. Five9 makes sense for mid-market to early enterprise. If you're running 2,000+ agents with complex routing, Infinity or Genesys is more likely to meet your requirements.

Avaya Infinity vs. Twilio Flex

Twilio Flex is a toolkit, not a finished product. You get voice APIs, messaging APIs, TaskRouter, and a React-based agent desktop you're expected to customize heavily. If you have strong engineering resources and want complete control over every aspect of the contact center UI and logic, Flex gives you that. If you want cloud capabilities with a working agent desktop out of the box, Infinity is the more practical choice.

Avaya Infinity vs. Cisco Webex Contact Center

Cisco Webex CC integrates tightly with Cisco's broader infrastructure: Unified Communications Manager, networking equipment, and the Webex collaboration suite. If you're already deep in the Cisco ecosystem, Webex keeps everything under one vendor umbrella. If you're in the Avaya ecosystem, the migration path to Infinity is simpler than cross-vendor migration to Webex. If you're choosing between the two without existing infrastructure commitment, evaluate based on which ecosystem aligns with your broader IT stack.

Analyst Positioning

Avaya is not included in the 2024 Gartner Magic Quadrant for CCaaS or the 2025 Forrester Wave for CCaaS. Those are the two most influential analyst benchmarks for enterprise contact center buyers.

The reason, according to analysts, is revenue qualification rather than product deficiency. Avaya's pure CCaaS revenue doesn't meet the inclusion thresholds. The company does appear in Constellation Research's ShortLists for both CCaaS and UCaaS, and received a CRN 5-star Partner Program rating in 2025.

For buyers who use Gartner and Forrester as part of their evaluation framework, Avaya's absence creates a gap. There's no independent analyst scoring to benchmark against. That puts more weight on your own proof-of-concept testing and reference customer conversations.

Implementation Timelines

Where Implementations Go Wrong

WebSocket management is harder than it looks. Connection recovery, event ordering, and reconnection state management during peak volume require careful architecture. This isn't request-response. Budget time for edge cases.

Rate limits bite in production. If your architecture assumes unlimited API calls, you'll hit 429 errors under real traffic. Design batch operations and caching from the start.

Sandbox environments don't reveal production behavior. Real telephony has latency, failover, and concurrency dynamics that sandboxes can't replicate. Test with real call volume before go-live.

Agent desktop projects expand. Every stakeholder adds requirements. Define the MVP and protect it. The teams that deliver on time are the ones that say no during the build.

New technology with old processes delivers old results. Platform migrations that don't redesign agent training, supervisor workflows, and quality assurance processes alongside the technology investment underperform. The operations layer matters as much as the platform layer.

Pricing

Avaya doesn't publish transparent pricing for Infinity, and the lack of self-service pricing is a consistent complaint across review platforms.

For the predecessor AXP Public Cloud, approximate per-agent pricing was: Digital Plan at roughly $35/user/month (messaging and email only), Voice Plan at roughly $60/user/month, and All Media at roughly $89/user/month for full omnichannel. One publicly referenced figure puts AXP Advanced at $169/user/month. Infinity pricing is expected to follow a similar structure. Custom quotes are required.

Questions to Ask Before Signing

• What API calls are included in base licensing versus usage-based charges?

• Are webhook deliveries and real-time event subscriptions charged separately?

• How are AI API calls priced (transcription, sentiment, summarization)?

• What support tier covers API-related issues?

• What are the contractual protections if Avaya undergoes another financial restructuring?

• What are the data export capabilities and portability guarantees at contract termination?

Migration Path for Existing Avaya Customers

The Upgrade Advantage (UA) subscription enables step-by-step migration to Infinity without complete system replacement. UA preserves previous licensing value and lets you adopt modularly: add digital channels and AI workflows now, migrate voice later. For many large enterprises, this is the deciding factor.

The caveat is that "seamless migration" depends entirely on your specific Aura or Elite configuration, your integration complexity, and the state of your current deployment. Get a detailed migration assessment from Avaya before committing. Then get a competing assessment from at least one cloud-native vendor (NICE, Genesys, Five9, and Amazon Connect all run dedicated Avaya migration programs). Compare them honestly.

Recommendations

Strong Fit

Large enterprises on existing Avaya infrastructure. If you're running Aura or Elite with 500+ agents and deep integrations, Infinity provides the lowest-risk modernization path. The hybrid bridge is genuinely differentiated. Validate it in a proof-of-concept with your specific configuration.

Regulated industries that need deployment flexibility. Private cloud, on-premises, and hybrid options with compliance certifications (HIPAA, PCI-DSS, SOC 2) address requirements that cloud-only platforms cannot. If on-prem is a regulatory mandate, Avaya is one of very few enterprise-grade options.

Worth Evaluating, But Compare Hard

Greenfield cloud deployments. Without existing Avaya investment, the hybrid strengths are irrelevant. Evaluate against Genesys, NICE, Amazon Connect, and Five9 on feature parity, ecosystem size, TCO, and team expertise.

Probably Not

Organizations under 200 agents. The 200-seat cloud minimum and G1500 enterprise focus mean smaller organizations are not the target market. Five9, Amazon Connect, or Dialpad will serve you better.

Buyers who need long-term vendor certainty above all else. The financial trajectory is improving, but two bankruptcies in six years and ongoing workforce reductions require contractual protections that wouldn't be necessary with Genesys, NICE, or AWS.

Platform vs. Operations

Most of what's published about CCaaS evaluation assumes you have an internal team that will run the platform. The implementation tables assume you have integration architects, backend developers, and QA engineers on staff. Maybe you do.

But an increasing number of enterprises are recognizing that the platform is only half the equation. The other half is agent operations: recruitment, training, quality assurance, workforce management, coaching, and the continuous optimization that turns a technology investment into measurable business outcomes.

Unified CX operations combines platform management with human and AI agent operations under a single accountability framework. Instead of buying a platform, hiring a systems integrator, and then hiring a BPO and hoping they coordinate, you get one partner accountable for results.

Whether you choose Avaya Infinity, Genesys Cloud, NICE CXone, or another platform, the question worth asking alongside "which technology?" is "do we have the operational capability to extract the value we're paying for?" If the answer is uncertain, the operations model decision may matter more than the platform decision.

Due Diligence Checklist

Before committing to any enterprise CCaaS platform:

• Review API documentation for every required integration. Not the demo. The docs.

• Get sandbox access and test actual API calls against your use cases.

• Talk to reference customers of similar size, industry, and complexity.

• Understand the roadmap and timelines for capabilities you need but don't have today.

• Clarify support escalation paths and SLA guarantees for technical issues.

• Review contract terms: usage commitments, overage pricing, source code escrow, data portability.

• Understand your exit. Data export formats, timeline, costs.

• Identify certified implementation partners. Avaya's partner ecosystem is smaller than Genesys or NICE.

• For Avaya specifically: review the latest Fitch rating, quarterly earnings, and workforce announcements.

• Determine whether you have internal capability to operate the platform or need an operations partner.

Frequently Asked Questions

What is the difference between Avaya AXP and Avaya Infinity?

Infinity launched in April 2025 as the evolution of AXP. It incorporates technology from Avaya's 2024 acquisition of Edify, including a no-code orchestration engine, MCP support for AI model integration, and enhanced hybrid deployment. If you were evaluating AXP, Infinity is the current product.

Is Avaya Infinity in the Gartner Magic Quadrant?

No. Avaya is not in the 2024 Gartner Magic Quadrant for CCaaS or the 2025 Forrester Wave. Analysts point to revenue qualification thresholds rather than product issues. Avaya appears in Constellation Research's ShortLists.

Can Avaya Infinity run on-premises?

Yes. Infinity is the only major enterprise contact center platform offering on-premises deployment alongside public cloud, private cloud, and hybrid options, all from the same Kubernetes-based codebase.

How much does Avaya Infinity cost?

No public pricing exists. Predecessor AXP pricing was approximately $35/user/month (digital), $60/user/month (voice), $89/user/month (all media), with AXP Advanced at $169/user/month. Custom quotes are required. The 200-seat minimum applies to public cloud.

Is Avaya financially stable?

Improving. Fitch upgraded the credit rating to B- Stable in November 2025, enterprise retention is 97%, and the debt-to-revenue ratio is healthy. But two bankruptcies in six years, ongoing workforce cuts, and declining revenue are real risks. Build contractual protections accordingly.

Should I stay on Avaya or migrate to another platform?

If you have significant Avaya infrastructure, need hybrid/on-prem deployment, and are a large enterprise customer, Infinity offers the lowest-risk modernization path. If you're greenfield, under 200 agents, or prioritize innovation velocity, evaluate Genesys, NICE, Amazon Connect, and Five9 on their merits.

About InflectionCX

InflectionCX is a unified customer experience operations company combining AI agents with human agents to deliver measurable outcomes across industries. Our Atlas (quality assurance) and Encore (coaching) systems were built inside production contact centers before being offered as standalone solutions.

inflectioncx.com