Zendesk's help-desk bot has already outlived one name

The conversation

Zendesk's automated reply product has changed names and architecture more than once, and its own support site now documents the transition directly. A Zendesk help center article, retrieved 16 September 2026, opens with a notice that Answer Bot resolutions will be replaced with automated resolutions, pointing readers to a separate article on automated resolutions for AI agents. The same page still explains how the older product counted its work: a resolution is counted when an end user takes a specific action in response to a suggested article, such as clicking a button confirming the problem was solved.

What the documents show

Zendesk's current marketing page for the successor product, zendesk.com's AI agents page, states that these agents ground answers in unified knowledge by connecting to a company's help center and external sources like Google Drive or PDFs, and that they intelligently route issues to the right team at the right time when a handoff is needed. A separate Zendesk help center article, Understanding everywhere you can use AI agents, lists the actual surfaces this covers: messaging and email channels, mobile SDKs, a Slack integration, a Microsoft Teams integration, and a separately branded line the article calls Forethought AI agents by Zendesk, described as an independent suite of omnichannel AI tools that can serve organizations even if they do not use the Zendesk platform.

The system boundary

The legacy Answer Bot's documented behavior is a clean illustration of a narrow, well-defined system boundary: it suggested help-center articles and counted a resolution only when a customer explicitly said the suggestion solved their problem, with no claim of understanding or reasoning beyond article matching. The newer AI agents described in Zendesk's marketing and mobile documentation extend that boundary, adding the ability to cover all levels of automation, from quick self-service workflows to more complex workflows integrated with other platforms, while the mobile documentation notes that a user can mark an article as solving their issue, or indicate they still need help and want to escalate to a support ticket, the same confirm-or-escalate path carried into a more capable product.

Where it fails

The transition itself is the main thing a builder needs to watch: Zendesk's own documentation now describes Answer Bot as a legacy product being replaced, which means any article, integration guide or contract referencing Answer Bot resolutions by name may already describe billing and behavior Zendesk is phasing out.

• Does the account in question still run on legacy Answer Bot resolutions, or has it moved to the newer automated-resolutions model for AI agents?
• For the Forethought-branded AI agents specifically, which parts of the pipeline run on Zendesk's own platform versus a separately operated system?
• What confirms a resolution was actually correct, rather than simply a customer declining to say otherwise?

Across both eras of the product, Zendesk's own documentation keeps the same basic shape: suggest an answer from a knowledge base, ask the customer to confirm, and route to a person when the customer says the suggestion did not work.