Zendesk Adds Draft and Rollback Controls to Copilot Procedures
Knowledge administrators can stage changes to auto assist procedures before they affect live suggestions and restore an earlier published version when needed.
Edited by Tyronne Panaino
Zendesk announced draft mode and version control for Copilot auto assist procedures on September 23, with a rollout window running from September 21 through September 25. The official Zendesk announcement says the feature is included for eligible accounts that have the Copilot add-on and auto assist turned on.
The change is aimed at knowledge administrators whose procedure edits influence suggestions shown to support agents. Previously, editing a published procedure applied the update directly to live suggestions. Under the new workflow, editing a published procedure creates a draft instead of immediately replacing the live version.
Procedure edits gain a staging state
Administrators can save and refine a draft while the published procedure continues to drive the live auto assist workflow. The procedure list now exposes statuses, supports filtering by status and lets an administrator edit or discard a draft. That separates preparation from publication inside Knowledge admin.
The practical implication is a smaller change window. A team can review an instruction update before it reaches agents rather than treating every saved edit as a live deployment. That is an operational inference from the staged workflow, not a claim that Zendesk independently validates the content of a procedure.
Version history adds a recovery path
Zendesk also says administrators can review earlier procedure versions and their performance data, then restore a previously published version. This provides a documented rollback path when an update produces unwanted suggestions.
Rollback is not the same as prevention. The announcement does not describe a mandatory approval step, automated quality threshold or independent safety test before a draft is published. Organizations still need to decide who can edit, review and publish procedures and what evidence is required before a change becomes live.
Eligibility and rollout remain account-specific
Zendesk says no customer action is required and describes the feature as automatically available to eligible accounts with auto assist enabled. The published rollout window ends on September 25, but the fetched evidence does not independently confirm that every eligible account received the controls at the same moment.
Administrators can verify the change by opening Knowledge admin and checking whether edits to a published procedure create a separate draft, whether procedure statuses can be filtered and whether prior versions are available for restoration. Those checks establish account availability more directly than the calendar date alone.
Why this matters for governed agent assistance
Procedures are operational instructions that shape the assistance a human agent sees. Moving them into a draft-and-publish lifecycle creates clearer separation between authoring and live behavior, while version history makes the previous state recoverable. The remaining governance question is whether each organization pairs those product controls with its own review roles, test cases and monitoring.
Status
Confirmed. Zendesk documents the draft, status, history and rollback controls and their scheduled rollout window. Internal confidence is medium because the availability and behavior claims come from one official vendor page without independent account-level verification.
Sources
Update note: Last reviewed 2026-09-25. We will revise this post if Zendesk changes eligibility, publishing controls or the procedure-version workflow.
Sources
Drafted with AI assistance from source briefs; reviewed for citation completeness and label accuracy.