Expected: Zendesk Will Change AI-Agent Ticket Status and Assignment in November
A scheduled November rollout removes the bot assignee and changes new AI-agent tickets from Open to New, requiring some saved views to use Support type instead.
Edited by Tyronne Panaino
Zendesk plans to change how newly created AI-agent tickets are assigned and initialized in Support and Agent Workspace. The official announcement was published on September 21 and schedules an automatic rollout to all accounts from November 3 through November 5, 2026.
The change matters to support administrators because saved views and reports may depend on the current Assignee and Status fields. Zendesk advises teams using those fields to identify AI-agent tickets to switch their view logic to the Support type field before the rollout.
What is known
Zendesk says AI-agent tickets will no longer be assigned to an AI-agent user. The company expects that removal to create a clearer distinction between conversations handled by AI and tickets assigned to human agents in views and reports.
Zendesk also plans to change the initial status of newly created AI-agent tickets. They currently start as Open, while regular tickets start as New. Under the scheduled update, newly created AI-agent tickets will start as New as well.
Both changes alter field semantics rather than the underlying conversation content. A saved view that identifies AI work through a bot assignee may stop matching new tickets, while a queue filtered around the Open status may receive a different initial set. The exact effect depends on each account's current views, triggers, reports and downstream integrations.
What administrators can prepare now
Zendesk specifically directs customers whose AI-agent ticket views use Status or Assignee to use Support type instead. Administrators can inventory those views before November and check any reporting or automation that treats a bot assignee or Open status as the defining signal for an AI-handled conversation.
That review should include logic outside the visible ticket list when those same fields feed exports, dashboards or integrations. This is a practical preparation step inferred from the announced field changes; the source does not enumerate every downstream system that could depend on them.
What would confirm it
The next verifiable checkpoint is the November 3–5 rollout window. Confirmation requires eligible production accounts to show newly created AI-agent tickets without an AI-agent user assignee and with New as their initial status. Saved views using Support type should then continue to distinguish AI-agent tickets under the revised field model.
Until that behavior is observed, the schedule and final mechanics remain a vendor expectation. Zendesk could change the rollout dates, scope or implementation before November, and the fetched announcement does not provide an independent deployment record.
Status
Expectation. Zendesk has published a specific plan and date window, but the field changes are not yet established as live production behavior. Internal confidence is medium because the schedule comes from one official vendor page and remains forward-looking.
Sources
Update note: Last reviewed 2026-09-25. We will revise this post when the November rollout begins, completes or changes.
Sources
Drafted with AI assistance from source briefs; reviewed for citation completeness and label accuracy.