All documentation

Docs / How it works

Ticket tags and internal notes

The tags and private notes AutoKnowledgeBase adds to analyzed Zendesk tickets, how to report on them in Explore, and how to turn them off or silence notifications.

After analyzing a solved ticket, AutoKnowledgeBase writes the outcome back onto the ticket in Zendesk. Agents can see what happened without leaving the ticket, and you can report on it in Zendesk Explore.

Both features are on by default. You can turn either one off in Settings → Zendesk ticket feedback.

Tags

Every analyzed ticket gets akb_analyzed plus exactly one outcome tag:

TagMeaning
akb_analyzedAutoKnowledgeBase analyzed this ticket
akb_article_createdA draft article was created from this ticket
akb_article_updatedAn existing article got a draft update from this ticket
akb_already_coveredYour help center already covers this ticket
akb_not_kb_worthyThe ticket holds no knowledge other customers could reuse
akb_errorAnalysis failed for this ticket

What to know:

  • Tags are added, never replaced. Your existing ticket tags stay as they are.
  • Solved tickets stay solved. Only the ticket's updated timestamp changes.
  • The akb_analyzed tag stops repeat analysis. The trigger AutoKnowledgeBase created only fires for solved tickets without it, so writing the tags can't trigger a second analysis.
  • Tickets that weren't analyzed get no tags. For example, tickets solved while you were out of credits.

Reporting in Explore

Because every analyzed ticket has akb_analyzed and exactly one outcome tag, the two report cleanly against each other. For example, in a Zendesk Support tickets report:

  • Count tickets with akb_analyzed to see how many tickets were analyzed in a period.
  • Break that down by the outcome tags to see what share led to a new article, an update, or nothing.
  • Track akb_already_covered over time: a rising share means your help center covers more of what customers ask.

Internal notes

AutoKnowledgeBase can also post a short private note on the ticket. It's an internal comment, so the customer never sees it. The note:

  • Says what was decided
  • Links to the draft article or the proposed update in Zendesk
  • For "already covered", names the closest matching article and how similar it is
  • For "not worth documenting", gives the reason
  • Links to the ticket's page in your AutoKnowledgeBase dashboard

A note doesn't reopen a solved ticket.

Who the note is posted as

Notes are posted by the Zendesk user whose authorization AutoKnowledgeBase uses: the workspace owner, who is the first person to connect. Teammates signing in later don't change this. To have notes come from a dedicated integration user, connect AutoKnowledgeBase with that user first. If your workspace already exists, email support@autoknowledgebase.com. See Team access.

Stopping notification emails for notes

A note is still a comment, so your Zendesk triggers treat it like one. With Zendesk's default setup, the assignee may get a "comment updated" email for each note.

To stop that, edit your Notify assignee of comment update trigger in Zendesk Admin Center and add this condition under Meet ALL of the following conditions:

Tags → Contains none of the following → akb_analyzed

Apply the same condition to any other notification trigger that fires on comments.

Turning tags or notes off

In AutoKnowledgeBase, go to Settings → Zendesk ticket feedback and clear either option:

  • Add tags to analyzed tickets
  • Post an internal note explaining the outcome

The change applies to tickets analyzed from then on. Tags and notes already written stay on their tickets.

If you turn tags off, AutoKnowledgeBase doesn't add akb_analyzed, so Explore reports based on these tags stop counting new tickets.

Last updated November 21, 2026