Avaya Agent for Desktop End of Sale: What the 2026 Notice Means for Your Organization

On July 20, 2026, Avaya discontinued new sales of Avaya Agent for Desktop, and existing customers lose the ability to buy additions or expansions on October 23, 2028. If you run an Avaya contact center, the useful question is not which product replaces it. The useful question is which customer tier you are in, because Avaya has publicly reorganized its business around its 1,500 largest global customers, and most organizations are not on that list.

This guide covers what Avaya announced, the end-of-life dates worth tracking, how to tell where your organization sits in Avaya’s priorities, and how to evaluate your options without either panicking or drifting.

What did Avaya announce about Agent for Desktop?

Avaya issued a customer notice discontinuing new sales of Avaya Agent for Desktop, both SIP and H.323 versions, effective July 20, 2026. The application is immediately unavailable for new system sales. Beginning October 23, 2028, existing customers can no longer purchase additions or expansions for systems already deployed.

Avaya’s stated migration path is that Agent for Desktop features are available in Avaya Workplace for SIP deployments, while H.323 customers can either move to SIP or migrate to J1xx H.323 endpoints. Avaya also said it will honor existing warranty and service contracts according to their terms, and that renewals of existing support agreements.

Worth noting, and often missed in the coverage: these paths do not force a move to public cloud. SIP deployments can continue on-premises or in private environments.

Taken alone, this is routine product consolidation. Vendors retire overlapping applications constantly. The context around it is what deserves your attention.

Avaya end-of-life dates worth tracking 

Always confirm dates for your specific release and components in writing. Lifecycle dates vary by version, and vendors reserve the right to revise support dates based on parts availability and technical expertise.

The real question: are you inside Avaya’s Global 1500?

Here is the piece that matters more than any single product notice.

After emerging from its second Chapter 11 bankruptcy in 2023, Avaya restructured under CEO Patrick Dennis, who took over in September 2024. The company refocused around what it calls the G1500, its top 1,500 global customers. Analysts have described it as a scaled-down version of the Broadcom playbook, concentrating support resources, engineering investment, and executive attention on the largest accounts while stepping back from broad-market coverage. The restructuring also included multiple rounds of cost reduction, including voluntary exit packages offered across the workforce.  

Avaya has historically served everyone from small businesses to organizations with hundreds of thousands of employees. The G1500 approach narrows that deliberately. Regions contributing little to the G1500 have seen minimal remaining presence.

Do the math on your own organization. Unless you are a very large enterprise or a major agency, you are unlikely to sit inside the top 1,500 accounts of a global communications vendor. Most mid-sized organizations sit well outside it, commercial and public alike. That is not a criticism of Avaya. It is a strategy working as designed, and it has a practical consequence: the level of attention you received in 2018 is not necessarily the level you will receive in 2028.

Avaya and its partners have disputed the harshest readings of this shift. Some partners say the company is not walking away from customers below the seat thresholds, and that workarounds exist through the channel, for example buying smaller license blocks through distributors or splitting requirements across a partner’s base. Read the other way, the fact that customers now need workarounds to stay served is itself the point. The seat minimums and the shrinking direct presence are real, and the reassurance is coming largely from the partners who would sell you the alternative. Ask your reseller directly what support looks like for an organization your size, and get the answer in writing.

Avaya does have a forward roadmap. Avaya Infinity launched in 2025, runs across cloud-native, hybrid, and on-premises deployments, and earned recognition in the Omdia Universe: Customer Engagement Platforms 2026 assessment. That is worth evaluating if it fits. The question to sit with is where a new platform lands in the priorities of a company that has publicly said its investment follows its largest accounts. A capable roadmap and a narrowed support model can be true at the same time, and the roadmap matters less if you are not the customer it is being built for. 

There is no single verdict on Avaya in 2026. There is only the verdict for your organization, and it depends almost entirely on which side of that 1,500 line you sit on.

How to tell where you actually sit

You will not get a letter telling you your tier. You infer it. Ask your team:

1.  Who owns your account? A named Avaya account executive who initiates contact, or a reseller who is your only real channel?
2. How fast do escalations move? Compare your last three severity-one tickets against what you experienced three years ago.
3. Do your seat counts clear the published thresholds? If you are meaningfully below them, factor that into renewal planning.
4. Has your reseller changed posture? Partners reposition ahead of vendors, and a partner quietly adding other lines to their portfolio is a signal.
5.  Are you being pushed toward long renewal terms? Longer commitments requested at renewal often precede lifecycle announcements.
6. Can you still buy what you need? If expansion capacity is constrained today, your timeline is shorter than the published dates suggest.

None of these individually proves anything. Three or four together tell you something useful.

Why the 2028 date is really a right-now decision

Most organizations do not buy on vendor timelines. They buy on budget and procurement cycles, and those move slower than product notices. Run the math backwards from October 2028:

Ranges reflect what we typically see across mid-sized and larger organizations. Timelines stretch further where board, council, or committee approval is required.

Total realistic runway is 12 to 20 months, and longer if funding is not already secured. Working backwards from a 2028 date puts your practical start point in the next one to two quarters. If you expect to add seats or open a location before then, the window is tighter still, because expansion capacity is the first thing that gets cut off.

The date on the notice is not your deadline. Your procurement calendar is.

Should you follow Avaya’s recommended migration path?

Evaluate it. Do not default to it.

A product retirement is one of the few natural moments to ask whether your platform still fits what your organization needs today rather than what it needed when the system went in. The strongest force working against that question is sunk cost, and there is usually a second version of it, because someone championed the current system and revisiting it can feel like second-guessing them.

Rafael Flores, Chief Product and Growth Officer at Treasure AI, put the counterargument well: look at the milestones you have not reached yet and ask whether they would happen faster elsewhere. His phrasing was to avoid letting one domino knock over the rest. 

That is not an argument for leaving Avaya. It is an argument for making the comparison deliberately, once, with real numbers.

Comparing your options

Your next 90 days

1. Inventory your Avaya environment. Releases, seat counts, sites, contract and renewal dates, integrations, and documented call flows.
2. Get lifecycle dates in writing for every component, covering end of sale, end of additions, and end of manufacturer support.
3. Run the tier test above and write down what you find.
4. Compare the numbers. Remaining maintenance and hardware spend against three years of subscription at the same seat count.
5. Map your calendar backwards from the earliest date that constrains you.
6. Define your own evaluation criteria built on reliability, administration, support responsiveness, and adoption rather than a market chart.

Where to start

Most communications teams facing this are small, already stretched, and now holding a decision with a long tail. The hard part is rarely the technology. It is comparing options fairly, moving through procurement without losing months, and making sure implementation does not land entirely on two people.

That coordination is what a supplier-neutral advisor takes off your plate. Discovery, evaluation, procurement support, project coordination, and continued help after go-live, without you managing a stack of suppliers on top of your day job. If Avaya turns out to be the right answer for you, that is a fine outcome. The goal is to choose it rather than default into it.

Have an Avaya notice in your inbox and a timeline you have not mapped yet? Talk to an expert, and we will help you work it backwards.