Zendesk · Agent Copilot

Auto Assist

An AI assistant that reads submitted tickets in the Zendesk Agent Workspace and presents the human agent with suggested replies, suggested ticket actions and written instructions. Approved suggestions are executed by the system, including ticket field updates, macros and custom API actions into external systems. Actions and action flows marked pre-approved in a procedure execute automatically without being shown to the agent.

Recorded characteristics

Function
Understands the contents of a submitted ticket and proactively presents suggestions in the Agent Workspace composer: suggested replies to the customer, suggested actions on the ticket, and written instructions for manual steps the agent must perform. Suggestions are generated from admin-authored procedures, help centre articles, similar solved tickets and connected external knowledge sources. When the agent approves a suggested action or action flow, the system carries it out. Documentation states auto assist does not operate on AI agent tickets.
Data access
Ticket content and conversation; standard ticket fields documented as readable (assignee email, assignee name, brand, priority, requester email, requester name, status, subject, type) and custom ticket fields; admin-authored procedures; public help centre articles matching the ticket brand and language; internal help centre articles exposed through selected user segments; similar solved tickets matching the ticket brand; connected external knowledge sources activated by an admin, documented as including Box, Confluence, Document360, Google Drive, Guru, Notion, SharePoint, web crawler content and other Zendesk instances.
Actions
Can take actions
External actions
Yes
Human confirmation
Conditional
Permission basis
Mixed
Administrative control
An administrator must turn auto assist on in Admin Center (AI > Agent copilot > Auto assist) by selecting "Show auto assist replies and actions in the agent composer", and defines which agent groups have access. Admins author and publish the procedures that define what auto assist may do, link specific actions, action flows and macros into those procedures, mark individual custom actions or action flows as pre-approved so they execute without agent approval, configure custom actions and their authenticating connections, select which help centre user segments and external knowledge sources may be used, and scope auto assist to channels using ticket triggers that apply the agent_copilot_enabled tag.
Default state
Disabled
Availability
Requires the Copilot add-on. Documentation for actions states availability on all Suites and on Growth, Professional, Enterprise or Enterprise Plus. No region restriction is established in the documentation reviewed. An updated auto assist experience including a confidence-based suggestion mode is documented as an early access programme requiring account enrolment, and is not treated here as generally available.
Licensing
Copilot add-on, purchased in addition to the base Zendesk plan.
External model or provider
Not established. Documentation states large language model technology is used but does not name the model or provider.
Limitations and uncertainty
Zendesk documentation states that suggestions require agent approval before being sent and that "agents are always in control of the replies they send to customers", while separately documenting pre-approved custom actions and action flows that are not shown to the agent and execute automatically at the relevant step of a procedure. These statements are recorded together rather than resolved; the confirmation requirement therefore depends on admin configuration. The identity under which actions execute is only partly established: ticket-side standard actions occur in the agent workspace, while custom actions authenticate through an admin-configured connection which Zendesk warns "might have greater access privileges than your agents and end users". Auto assist is documented as limited to approximately four suggested items at a time and as unable to see unsaved ticket field changes. Model, provider, data retention and region were not established from the documentation reviewed.

Evidence