Expected: Zendesk Legacy AI Agents Enter Maintenance Mode August 31
Customers using Essential and older bot tooling have a migration deadline before technical development narrows and a later service shutdown.
Zendesk has scheduled its Essential and legacy AI-agent functionality to enter maintenance mode on August 31, 2026, beginning a staged retirement that is expected to end with service removal on December 10. The company's official support notice, originally announced June 23 and edited July 30, tells affected customers to move to its upgraded AI-agent experience.
What is known
The timetable applies to customers using AI agents - Essential or older functions such as bot builder and article-based autoreplies. Zendesk says it does not apply to customers that previously bought the AI agents - Advanced add-on.
Under the published plan, technical development for the legacy experience is expected to stop on August 31. Zendesk says it will then limit work to critical bug fixes and support for breaking changes. On December 10, Essential and legacy functionality is scheduled to reach end of service, and agents still running on that technology are expected to stop functioning.
The company is retiring the older bot builder, answers and intents tooling in favor of an upgraded experience that includes capabilities previously associated with the Advanced add-on. Its notice says affected customers must migrate before the December shutdown and recommends completing the move before the August maintenance transition.
Who is affected
The immediate audience is Zendesk administrators and support teams that still operate Essential or legacy AI agents. They need to identify which bots depend on the retiring experience, move their configurations to the newer system and test those replacements before the old technology loses active development.
This is more than a naming change. A maintenance-only period narrows the window for ordinary product fixes, while the December cutoff creates a hard operational risk for any workflow left behind. Teams should treat the August date as the safer internal migration target, leaving time to validate routing, automation and escalation behavior before the final service date.
What would confirm it
The August milestone will be confirmed when Zendesk places the legacy experience into maintenance mode and stops routine technical development as scheduled. The December milestone requires the company to complete the stated end of service. Until each transition occurs, both dates remain vendor-announced expectations and could still change.
Status
Expectation. The schedule comes from one official Zendesk source and has not yet taken effect, so internal confidence is medium.
Sources
Update note: Last reviewed 2026-08-03. We will revise this post if Zendesk changes the migration timetable or confirms either transition.
Sources
Drafted with AI assistance from source briefs; reviewed for citation completeness and label accuracy.