Automate support ticket triage and assignment

Support ticket triage identifies what the customer needs. Assignment sends the ticket to the team that can help. To automate both, define which requests belong to each team and set up a review queue for ambiguous, incomplete or sensitive requests.

Define your teams and triage rules

Start with groups that already have an owner in your helpdesk. List the requests each group handles and the situations that call for a handover. We used the following groups for the test.

Queue	Example request
Billing	Invoice copy, duplicate charge
Orders	Parcel tracking, delivery change
Access	Password reset, locked account
Technical	Export error, blank screen
Review	Suspected fraud, unclear request or multiple issues

1. Check escalation criteria first. Suspected fraud or an account takeover goes to a person under your incident process.
2. Find the groups that match the request. Assign the ticket if exactly one group matches. If no group or several groups match, send it to review with the reason.
3. Set priority separately. Use impact criteria such as the number of users blocked or the applicable service commitments. Technical issues and payment issues can both be urgent.

In Zendesk, a trigger can check conditions on a new ticket and set its group. Start with a narrow set of requests and check trigger order and existing assignment rules. Zendesk configuration example

Reproducible test on 30 French and English tickets

We ran keyword rules in Node.js 22.23.4 on 30 synthetic tickets, 15 in each language. Each ticket had an expected queue labelled before the run, including review for sensitive, ambiguous or underspecified cases. The script normalises the text, applies the rules in order and compares the decisions with the labels. The queues are simulated.

Download the script and labelled tickets (.mjs)

From the folder where you saved the file, run node support-ticket-routing-test.mjs. The script prints the results by language and lists the ticket IDs where the assigned and expected queues differ.

Measure	Result
Tickets assigned automatically	17 of 30 (57%)
Correct automatic assignments	16 of 17 (94%)
Tickets sent to review	13 of 30, including all 4 sensitive cases in the set
Decisions matching the labels, including review	24 of 30 (80%)

In French, all 7 automatic assignments were correct and 8 tickets went to review. In English, 9 of 10 automatic assignments were correct and 5 tickets went to review. Of the 13 reviews, 8 were expected and 5 had a specialist queue in the reference labels.

A misrouted ticket to inspect

Ticket EN-09 reports that the app stops responding on the invoice screen. The word “invoice” triggered Billing, although the failure belonged to Technical. Ticket FR-10, about a billing page that crashes, matched two groups and went to review. These results describe this synthetic set. On your own tickets, check whether the rules distinguish the topic mentioned from the action the customer needs.

Checklist for testing routing in your helpdesk

• Name an owner for each group and the review queue.
• Label a set of anonymised tickets by language, request type and expected group.
• Log the proposed queue and reason first, then compare them with the team’s decisions.
• Check that rerunning the same ticket preserves a person’s assignment.
• Track assignment coverage, errors by group and time spent on review.
• Test corrections on a separate set before enabling automatic assignment for a request type.

Copyable review note

Ticket · [link to the original request]
Review reason · [sensitive case, multiple groups or missing context]
Candidate groups · [matched groups or none]
Reviewer’s decision · [final group and reason]

If customers describe the same request in very different ways, an AI assistant can suggest a category and group based on the permitted context. Compare its suggestions with the rules on labelled tickets before deciding which cases to assign automatically. AI assistants for customer support