Auto-tag and categorize tickets in Zendesk

Tag hygiene is the foundation of clean support analytics, and the first thing that breaks. An Orkeste agent reads every new Zendesk ticket and applies a consistent taxonomy of product, intent and root cause tags.

How the workflow runs

  1. Read new ticket: Triggers on every new or updated ticket in scope.
  2. Classify against taxonomy: Maps the ticket to your existing tag taxonomy.
  3. Suggest new tags if needed: When existing tags don't fit, the agent proposes a new tag for human approval.
  4. Human approval on new tags: Taxonomy changes require explicit approval to avoid drift.
  5. Apply tags in Zendesk: Updates the ticket with the agreed tags.

Human-in-the-loop: Creation of new tags or merges of existing ones always goes through a human approver.

Works with your stack

Related workflows

Questions about this workflow

Will it overwrite our existing tags?

No. The agent only adds tags from your approved taxonomy and never removes tags without explicit configuration.

Can it back-fill historical tickets?

Yes. You can run a one-off back-fill against past tickets to clean up reporting.

How do we keep the taxonomy under control?

All new tags route through the taxonomy guardian step, so the tag list stays curated.