What this Zendesk agent handles
Knowledge bases decay when ticket resolutions do not feed back into public documentation. This agent reads resolved tickets, spots patterns, and drafts the help center updates your team can review before publishing.
The agent handles three main content jobs:
- New article creation. The agent identifies recurring issues from resolved tickets and drafts new help center articles with structured steps, screenshots references, and troubleshooting sections.
- Existing article updates. When a resolved ticket reveals a gap or outdated information in an existing article, the agent proposes an edit or addition to keep content current.
- Ticket cluster detection. The agent flags when multiple tickets on the same topic are resolved in a short period, signaling that a new help center article would likely deflect future volume.
How the agent works
The table below shows the trigger, inputs, outputs, and approval step so you can judge fit quickly.
| Agent stage | What happens | Output | Approval |
|---|---|---|---|
| Trigger | Runs on schedule, scanning recently resolved tickets for knowledge gaps | Content review starts | No approval for read phase |
| Inputs | Resolved tickets, existing help center articles, ticket cluster patterns | Draft article or article update proposal | No approval for data gathering |
| Proposed action | Create new article, update existing article, or flag ticket cluster for review | Draft content with title, sections, and metadata | Approval before anything is published |
| Operator review | Reviewer checks draft quality, edits for clarity, and approves or rejects | Approve, reject, or edit | Explicit approval required |
How to set up this Zendesk agent
Define content quality rules: what tone, structure, and detail level drafts should follow. Provide example articles for the agent to learn from.
Connect Zendesk with access to resolved tickets, existing help center articles, and the fields needed to detect recurring patterns.
Set thresholds for new article proposals: how many resolved tickets on a topic should trigger a draft, and what recency window to use.
Choose who reviews drafts, how edits are incorporated, and how feedback improves future versions.
Permissions and approval checks
- Read access should cover resolved tickets, ticket tags, and all published help center articles.
- Write scope should be limited to draft articles and article updates, not direct publishing without review.
- Draft proposals should include the source tickets used to generate the content, so reviewers can validate accuracy.
- Approval views should show both the proposed content and the existing article (for updates) side by side.
Frequently asked questions
Does the agent publish articles automatically or just draft them?
By default, the agent drafts updates and new articles for review. Teams can keep small edits fast while requiring approval before anything is published.
How does the agent decide when to create a new article versus updating an existing one?
The agent searches existing help center content for similar topics. If a close match exists, it proposes an update. If no match is found and the ticket pattern is recurring, it proposes a new article draft.
What happens if the agent proposes an article that is too technical or unclear?
All article drafts surface for review before publishing. You can edit the draft, reject it, or send it back with feedback. The agent learns from edits and feedback to improve future drafts.
Can the agent detect recurring ticket patterns that should become articles?
Yes. When similar issues keep appearing in resolved tickets, the agent can surface the pattern and draft the help center update your team should review.