On this page · 11 sections
- What changed since July
- The dates, side by side
- Check what you are running
- Autoreplies: what customers will notice in January
- Essential agents: use the migration tool
- Bot builder agents: plan a manual rebuild
- What the new setup costs
- A six-week plan to 1 January
- For teams in India and the UK
- How eCorpIT can help
- References
Summary. Zendesk's current migration guide for the new AI agents experience gives support teams three dates to plan around. From January 2027, if you still use autoreplies with articles, those emails and web form replies keep going out but no longer recommend specific help centre articles. Also in January 2027, Zendesk migrates any AI agents - Essential you have not moved yourself, and from the start of February 2027 it does the same for legacy bot builder agents, both with some exceptions. All three features have been in maintenance since 31 August 2026 and will be removed no later than June 2027. In July 2026 the same guide said December 2026 and did not list autoreplies at all. A migration tool now exists for essential agents, but legacy bot builder flows are still a manual rebuild. The replacement bills per automated resolution: Suite Professional includes 10 per agent a month, then $1.50 each committed or $2.00 pay-as-you-go. With about six and a half weeks to 1 January, our advice is to replace autoreplies with an email AI agent first, migrate essential agents with the tool, and scope bot builder rebuilds now.
About this article. This is for support operations leads, Zendesk admins and CX managers in the US, UK and India who still run AI agents - Essential, bot builder or autoreplies with articles. We checked every date, menu path and price on 17 November 2026 against Zendesk's own help centre articles and announcements (read through Zendesk's public help centre API), an Internet Archive copy of Zendesk's pricing page dated 16 November 2026 (the live page refused automated access), and an archived July 2026 copy of the migration guide. Zendesk names months, not days, for its January and February 2027 changes. Prices change often; confirm yours on your order form. This is not legal advice, and no vendor paid for inclusion. Researched with AI assistance and checked against the primary sources listed in the references.
What changed since July
Zendesk's help centre records the current text of the migration guide as last edited on 27 October 2026. Comparing it with the copy the Internet Archive saved on 19 July 2026 shows three material changes.
- The removal date moved. The July version said the deprecated features would be removed from the product in December 2026. The current version says no later than June 2027.
- Autoreplies with articles joined the list. The July version covered AI agents - Essential, legacy bot builder functionality and default messaging responses. The current version covers Essential, legacy bot builder functionality (answers and intents included) and autoreplies with articles.
- A January 2027 consequence for autoreplies. If you do not migrate, autoreplies are still sent from January 2027 but without specific article recommendations.
The two autoreply help articles were edited on 13 November 2026 and now say the feature became legacy on 31 July 2025 and will be removed in 2027. The removal announcement keeps its own date table: announced 23 June 2026, development ended 31 August 2026, forced migration starts January 2027.
The dates, side by side
These dates come from Zendesk's migration guide, removal announcement and packaging announcement.
| Date | What happens | Applies to |
|---|---|---|
| 11 May to 12 June 2026 | New AI agent packaging rolled out; Essential and Advanced merged | All Suite and Support plans |
| 31 August 2026 | Development stopped except critical fixes and breaking changes | Essential, bot builder, autoreplies with articles |
| January 2027 | Autoreplies sent without article recommendations if not migrated | Email, web form, Web Widget (Classic) autoreplies |
| January 2027 | Unmigrated essential AI agents moved for you, with some exceptions | AI agents - Essential |
| Start of February 2027 | Unmigrated legacy AI agents moved for you, with some exceptions | Bot builder, answers, intents |
| No later than June 2027 | All three features removed from the product | Essential, bot builder, autoreplies with articles |
The announcement says it does not apply to customers who bought the AI agents - Advanced add-on, and asks everyone else to migrate essential agents before January 2027 and legacy agents before February 2027. Zendesk recommended migrating before 31 August 2026; that date has passed, so anything still on the old features is running on software that only receives critical fixes.
Zendesk does not say which exceptions it will leave out of the forced migration. Treat that as a reason to migrate yourself rather than wait: a forced move happens on Zendesk's schedule, not during your quietest hours.
Check what you are running
All the checks start in Admin Center under AI > AI agents > AI agents.
Essential or legacy agents. Under the Essential (legacy) heading, open each agent and look at its tabs. An essential agent has neither an Answers nor an Intents tab. A legacy bot builder agent has an Answers tab and may also have an Intents tab.
Email autoreplies with articles. Click Manage autoreplies. If that option does not appear, you are not using the feature. Otherwise click Get started with autoreplies and open the Email tab; any trigger listed there means you are using it.
Web form autoreplies with articles. From the same place, open the Web form tab, expand each brand and look for web forms whose autoreply toggle is on.
Web Widget (Classic) autoreplies. Click a brand to open its widget settings and check the autoreply with articles box on the Basics tab. If no brands appear, you have none. Zendesk's widget article points web messaging users to AI agents instead.
Write the results into a simple inventory: agent or trigger name, channel, brand, monthly volume and owner. Every later step depends on it.
Autoreplies: what customers will notice in January
Today an email autoreply with articles can include up to three recommended help centre articles, show the top one in full, and let the customer close the request from the article. On web forms, a pop-up suggests up to three articles straight after submission, with options to preview them or close the request.
From January 2027, unmigrated autoreplies still go out but without those specific recommendations. The likely effect is that fewer customers self-serve from the autoreply, so more requests stay open for agents. If your autoreply copy promises suggested articles below, update it now so customers are not sent an empty promise.
The replacement is an email AI agent
Zendesk's migration path is a new AI agent that answers from the same help centre content but writes a reply in the conversation instead of listing links. An email AI agent covers email, API and web form channels, and only one AI agent can be active on a given support address or web form at a time.
Creation runs in the AI agents workspace: Dashboard > Create AI agent > for Email. You pick one brand and its knowledge base, optionally add web crawlers, and need at least one connected knowledge source to continue. You then set a name, a one or two sentence business profile in English, a tone of voice, a default language and any languages for automatic translation.
Before you switch it on, tidy the help centre. Zendesk's getting-started guide puts content optimisation as step one, because the agent answers from that content. Articles that worked as link targets can be poor sources for a generated answer if they are long, out of date or contradict each other.
Essential agents: use the migration tool
When you have essential agents to move, a banner on the AI agents page in Admin Center opens the migration tool. It creates a new agent and carries across settings and instructions, greeting, escalation, feedback and fallback behaviour, connected knowledge sources, branding, default language and translation settings, and channel connections.
Six points matter when you plan the cut-over:
- One channel per agent. An essential agent deployed on messaging and email becomes two agents: a messaging agent (web, mobile and social messaging) and an email agent (email, web form and API). Later changes must be made in both.
- History stays behind. Past conversation logs, analytics, insights and conversation memory are not migrated.
- Messaging conversations break on activation. In-progress messaging conversations are interrupted and customers are redirected to your default messaging response. Email is not affected. Activate during a low-traffic window; Zendesk suggests the reporting dashboard to find one.
- No undo. Zendesk says a migration cannot be reversed, though a migrated agent can sit inactive while you test it and the essential agent keeps running until you activate.
- No sync back. If you edit the original essential agent after migrating, those edits are not copied to the new one. Zendesk treats that as a rollback and suggests starting the migration again.
- Go gradually. Agents can be migrated one at a time. Zendesk recommends starting with the lowest-traffic agents and finishing before the migration period ends to avoid a forced move.
The migration guide still says in its opening sections that a tool will come later in 2026, while its own migration section and the separate tool article describe the tool as available. We read that as the tool being live for essential agents.
Standard responses map to system replies: start of conversation becomes the welcome reply, after the agent replies becomes the collect BSAT reply, escalation becomes the escalation reply, and the cannot-answer response becomes the default reply. New agents also gain unsupported language and technical error replies, plus a failed escalation reply on messaging agents only. If you kept custom translations, note that the new experience needs a language-specific version of each system reply, so Zendesk recommends automatic translation instead.
Bot builder agents: plan a manual rebuild
For legacy agents built with bot builder, answers and intents, the guide says a migration tool will arrive later in 2026; until then the path is a rebuild. The concepts map as shown below, from the guide's own mapping tables.
| Concept | Bot builder | New AI agents experience |
|---|---|---|
| Where flows are built | Bot builder | Dialogue builder |
| Scripted flows | Answers | Dialogues |
| Understanding the request | Intents | Use cases |
| Send a message | Send message step | AI agent message block |
| Offer choices | Present options step | Customer message block |
| Suggest articles | Show help center articles step | Generative replies block |
| Call another system | Make API call step | Integration or action flow |
| Hand to a person | Transfer to agent step | Escalation block |
| Branch on data | Branch by condition step | Conditional block |
| Business hours | Add business hours condition step | Availability block |
Zendesk suggests listing your current answers and intents first, then creating matching use cases and dialogues. It also points to generative procedures, where you describe how a topic should be handled and the agent can adapt to unexpected questions, as an alternative to scripted dialogues. For many answer flows, or complex ones with lots of branches or integrations, Zendesk strongly recommends its AI Expert offering, which is a recurring service subscription.
Use the rebuild to prune. Answers that nobody triggers in your reporting do not need a dialogue. Flows that only collect details and escalate may be simpler as one procedure. Every Make API call step becomes an integration or action flow to rebuild and test, so count those first: they set the timeline. Our earlier piece on the Zendesk legacy AI agents forced migration covers the rebuild decision in more depth.
What the new setup costs
The new experience is metered in automated resolutions. Since 18 May 2026 these come in three tiers. An assisted escalation (the agent helped but a person finished) and a contained resolution (the customer did not ask for more help but an LLM check could not confirm the request was solved) do not count against your allowance. A verified resolution, which passes that check, does. On email, a conversation is judged 72 hours after the first email; on messaging, two hours by default and up to 72; on voice, at hang-up.
The Internet Archive copy of Zendesk's pricing page from 16 November 2026 lists these numbers.
| Plan | Annual price per agent a month | Included automated resolutions |
|---|---|---|
| Support Team | $19 | 5 per agent a month |
| Suite Team | $55 | 5 per agent a month |
| Suite Professional | $115 | 10 per agent a month |
| Extra resolutions, committed | $1.50 each | Bought in advance |
| Extra resolutions, pay-as-you-go | $2.00 each | No commitment |
Included resolutions are capped at 10,000 a year. Accounts moved to resolution allowances see the allowance as a currency pool and get financial and operational dashboards; Zendesk tells you before it upgrades your account. Zendesk also warns that resolution counts may change as you adopt the new capabilities, which can change your bill, and that existing overage settings carry over.
A worked example. Take 10 agents on Suite Professional: 10 x 10 = 100 included resolutions a month. Suppose the new email agent produces 600 verified resolutions a month. The extra 500 cost 500 x $1.50 = $750 a month committed, or 500 x $2.00 = $1,000 pay-as-you-go. At ECB reference rates for 16 November 2026, crossed and rounded to two decimals, $1 is ₹93.93 and £0.76, so $750 is about ₹70,448 (750 x 93.93) or £570 (750 x 0.76) a month committed. The volume is our assumption, and your contract price may differ, so check the order form. For how Zendesk's per-resolution cost compares with Intercom and Freshdesk, see our AI agent pricing comparison.
A six-week plan to 1 January
Zendesk gives a month, not a day, for the autoreply change, so plan to be done by 31 December.
- Week of 16 November. Run the checks above and build the inventory. Note which autoreplies drive the most self-service closures.
- Week of 23 November. Review the help centre articles your autoreplies recommend most. Fix stale or overlapping ones, because the email agent will answer from them.
- Week of 30 November. Create the email AI agent for your busiest brand. Test it against a sample of real past tickets and read every answer. Our guide to catching silent AI agent failures explains how to build that test set.
- Week of 7 December. Activate the email agent and disable the matching autoreply trigger. Run the migration tool on your lowest-traffic essential agent, test it, and activate in a quiet window.
- Week of 14 December. Migrate the remaining essential agents. Watch verified resolution counts and the allowance dashboard daily.
- Week of 21 December. Update any remaining autoreply copy, freeze changes over the holidays, and write the bot builder rebuild plan for January, ahead of the February forced migration.
For teams in India and the UK
Support teams in India often answer in English and one or more Indian languages. The new agents translate automatically into the languages Zendesk supports for automatic translation, and Zendesk recommends that over hand-kept custom versions of each reply. Test answer quality in each language you serve before you switch off autoreplies. Tickets still carry names, phone numbers and order details whichever tool answers them, so your obligations under the Digital Personal Data Protection Act 2023 do not change; our DPDP engineering playbook covers the controls. UK buyers should ask for sterling pricing on the order form, since the figures above are US list prices.
How eCorpIT can help
eCorpIT is a Gurugram-based technology organisation, founded in 2021, assessed at CMMI Level 5 and MSME certified, with senior-led engineering teams working across AWS, Microsoft and Google platforms. Our artificial intelligence and machine learning services team can audit your Zendesk automation, rebuild bot builder flows as dialogues or procedures, and test answer quality before you switch off autoreplies. Talk to us at /contact-us/.
Last updated: 17 November 2026.