Skip to main content
Intent classification should interpret the customer’s message. Routing should apply the support team’s rules. Keeping those responsibilities separate makes the system easier to test, audit, and improve.

What It Does

The intent, tagging, and routing function:
  • Reads the normalized ticket and customer context bundle
  • Classifies the primary intent and secondary topics
  • Identifies product area, urgency, sentiment, language, and missing information
  • Applies allowed categories, attributes, and helpdesk tags
  • Calculates priority and SLA risk
  • Routes the ticket to the right queue, owner, response workflow, or specialist team
  • Escalates when confidence is low or the routing consequence is sensitive

Flow

Suggested Taxonomy

Start small. A useful first taxonomy usually has broad intent, product area, urgency, and route dimensions.
Avoid overfitting the first taxonomy. If reviewers cannot consistently explain the difference between two tags, start with one broader tag and split it after you have run data.

Classifier Output Contract

Have the classifier return structured output. The routing workflow can then validate values and apply rules.

Routing Rules

Keep routing rules deterministic after classification.

Helpdesk Writeback

Common writebacks include:
  • Tags
  • Category or custom fields
  • Priority
  • SLA policy
  • Queue or group
  • Assignee
  • Internal summary note
  • Missing-information request
  • Link to the Duckie run
Start with internal notes and shadow tags. Turn on assignment and priority writebacks only after replay testing and human review show that the routing rules are reliable.

Categories

Define the allowed classification categories.

Attributes

Track confidence, urgency, SLA risk, and route.

Autonomous Agents

Configure the triage classifier agent.

Workflows

Apply deterministic routing and writeback logic.