Skip to main content

Genesys Engage is ending. Put the AI agent in first

Published 8 min readThe Zowie Team
Genesys Engage is ending. Put the AI agent in first

Genesys ends support for Engage on-premises and subscription products on December 31, 2028, and full-year renewals stop after December 31, 2027. An AI voice agent connected over SIP in front of today's platform keeps working through the migration and after it, so most teams are better off adding it before the move.

Many banks, insurers and telcos run Genesys Engage (formerly PureEngage) and have years of routing, IVR and desktop work built on it. The notice gives them a clear window to plan the move, most likely to Genesys Cloud, which is the path Genesys recommends.

Planning the move off Engage?

We can walk through your call flows and draw the sequence for an AI voice agent with your team.

Book a demo

The same teams are choosing an AI voice agent in the same period. Both projects touch telephony, routing, context for human agents, recording and the security review. This piece is about the order.

1. The dates, from Genesys's own notice

Genesys published the end-of-life announcement for Engage Premises and Engage Subscription products in March 2024 and last updated it in June 2025. The dates that matter:

DateWhat happens
December 31, 2027End of full-year renewals of Engage Premises maintenance and subscription terms. Later renewals run for less than a year and end on or before December 31, 2028.
November 30, 2028End of all renewals.
December 31, 2028End of maintenance and support for all Engage Premises perpetual and subscription products. Subscription licenses stop working. Perpetual licenses keep running, without maintenance or support.

Until then, Genesys plans minimal releases: operating environment compatibility, critical security fixes and bug fixes where no workaround exists. Earlier product-specific end-of-life dates still apply, so some components reach their end sooner. CX Contact for Engage on-premises, for example, passed end of support on April 30, 2026.

Most organizations will aim to finish the move in 2027, before renewals get shorter. That leaves the coming months for the design work both projects need.

Already on Genesys Cloud with premises Edge devices?

That is a different product with nearer dates. Genesys ends support for the BYOC Premises Genesys Hardware Solution (Edge Standard v1 to v3, Edge Micro, Edge Mini v1 and v2) on December 1, 2026, and its end of life is June 1, 2027 (deprecation notice, Edges FAQ). After end of support, failing devices are not replaced and new deployments are not allowed. Genesys recommends moving to cloud media, BYOC Cloud or Genesys Cloud Voice, or, where media must stay on premises, to BYOC Premises on customer hardware. The Model field under Admin > Telephony > Edges shows which one you run.

If an AI voice agent is on your plan, choose the connection with the move in mind. An agent that takes the call over SIP works with either media option. Audio Connector, which many AI products rely on, is not supported on BYOC Premises.

2. Two projects, one team

A platform migration and an AI agent rollout draw on the same people: telephony engineers, the IVR team, desktop and CRM integrators, and security. They need the same test windows on the same phone lines.

Run both at once and three things tend to happen. Test results get harder to read, because a dropped context field could be the new platform, the AI vendor or the SBC. Security reviews double up. And the AI project waits for routing decisions the migration has not made yet.

One option is to finish the migration first and add AI afterwards. That works when the migration is close and the AI scope can wait a year or two. When it cannot, putting the AI agent in first, on a connection that survives the migration, is often the lower-risk order. The agent starts earning its keep in 2027 rather than 2029.

3. What the migration changes for an AI agent

The telephony path. On Engage, calls usually reach SIP Server through your own session border controller. On Genesys Cloud, Genesys documents several telephony options. BYOC Cloud runs SIP trunks between Genesys Cloud media in AWS and your systems over the internet. BYOC Premises runs SIP trunks between Edge devices on your premises and your systems. Genesys Cloud Voice uses Genesys as the carrier.

Where your SBC sits after the move decides where the AI agent's trunk terminates. Banks that keep media on premises for regulatory reasons will run Edge devices on Genesys Cloud, and the Genesys-supplied Edge hardware is reaching end of life (see the box above). Genesys's preferred path is cloud media; where premises media is required, it points to customer-supplied Edge hardware.

Which AI integrations work on premises media. Several AI and analytics features on Genesys Cloud stream audio out of the platform over a WebSocket. Audio Connector, the route many AI vendors use, is documented by Genesys as not supported under BYOC Premises or on premises-based Edge. Transcription Connector carries the same limit. An AI agent connected over SIP has no such dependency: the call reaches it through your SBC on either telephony option. If an AI or analytics product you are evaluating is built on Audio Connector, check it against the telephony option you plan to keep.

How context reaches the human agent. On Engage, context usually travels as attached data held by T-Server. On Genesys Cloud, it can travel as User to User Information (UUI) on SIP trunks. Genesys recommends keeping UUI to 128 characters or fewer, and UUI is not available on Genesys Cloud Voice calls.

A pattern that survives both platforms is a short session ID on the call. The receiving flow uses it to fetch the reason for the call, a summary and the verification status over an API. It keeps personal data out of SIP headers, too.

Recording. When the AI agent takes the call on its own SIP leg, the AI part and the human part are recorded in two systems. That meets compliance when both retention rules are set. Quality teams will want one view of the whole call, so it helps to decide where that view lives before the migration rather than after.

Data residency. Genesys runs a European Sovereign Region for public sector and highly regulated organizations. Genesys's own page says AppFoundry third-party integrations, other third-party systems, email and SMS operate outside the region's boundary, and that customers verify them. Whatever the connection method, the AI vendor's residency needs its own assessment.

4. A sequencing plan

Stage 0: inventory. Start with the first call reasons for the AI agent, the IVR flows that route them, and the data attached to each call today. Mark which parts of that setup the migration will change.

Stage 1: the AI agent on SIP, in front of Engage. Your SBC or IVR sends selected calls to the AI agent over a SIP trunk. The agent resolves the call or hands it back with a SIP REFER, passing a session ID the desktop uses to fetch context. Most teams start with a few call reasons and widen as results come in.

Stage 2: migrate the platform. During cutover, the AI agent keeps its SIP connection to your SBC. What changes is where the call goes after a handover and how the new desktop reads context. Retest those two points before each wave, and agree a short freeze on AI changes during cutover weeks.

Stage 3: widen on the new platform. Once the migration settles, add call reasons and channels. The agent, its flows and its decision logic stay the same. The trunk and the handover target are what moved.

5. Risks of doing both at once

RiskWhy it happensWhat helps
Unclear root cause in testingPlatform, SBC and AI change in the same weekSeparate test windows; change one layer at a time
Context lost on handoverAttached data, UUI and desktop scripts all changeSession ID plus API lookup; a handover test in every wave
Recording gapsAI and human legs recorded in different placesAgree retention and a combined view before cutover
Double security reviewTwo new vendors or services in one periodOne component map and data flow shared across both reviews
AI scope blockedRouting decisions wait for the new platform designStart the AI agent on call reasons the migration does not touch
AI integration tied to cloud mediaThe chosen connector needs Audio Connector or cloud EdgePick a connection that runs on both telephony options

6. Questions worth asking

Your platform partner or Genesys account team:

  • Which telephony option will we use on Genesys Cloud, and where will our SBC sit?
  • If we keep media on premises after the move, which Edge hardware will we run?
  • How will an external SIP endpoint receive calls and transfer them back, during and after cutover?
  • How does context reach the agent desktop on the new platform, and what are the size limits?
  • Where will calls be recorded, and can recordings from another system be linked?
  • Which product-specific end-of-life dates apply to the components we run today?

Your AI vendor:

  • Does the agent connect over standard SIP, and has it run behind both Genesys on-premises and Genesys Cloud?
  • Does any part of the integration depend on Audio Connector or cloud media?
  • How does it hand calls back, and how is context passed: SIP headers, an API, or both?
  • Which part of the call does it record, and how do we link that to the platform's recording?
  • What changes on its side when our trunk or SBC moves, and how long does a repointing take?
  • Where does it run, and does that fit our residency rules on the new platform?

How we approach Genesys migrations at Zowie

Zowie connects voice over plain SIP. Genesys or your SBC answers the call first and transfers it to Zowie. Zowie resolves it, returns it with a SIP REFER, or ends it, and passes context to the human agent through the Genesys API or SIP headers. We run this way with Genesys today, on voice, chat and email.

We chose SIP because it works on every Genesys telephony option, on premises and in the cloud, and because it keeps speech recognition, turn-taking and the decision logic on our side. The AI leg of the call is recorded with us, and the human leg stays with the platform.

If you are on Engage and planning both projects, we are happy to walk through your call flows and draw the sequence with your team.

New to Zowie?

Zowie builds voice and chat AI agents that work in production for large companies.

Book a demo

More from the blog

Stay ahead of the conversation

Get insights on the future of Customer AI, real-world use cases, and strategies for replacing clicks with seamless conversations - delivered straight to your inbox.

By submitting the form, you acknowledge our Privacy Policy and agree to receive email communications from us.