Goal
Design a simple, consistent way to tag, prioritise, and route support tickets so the right team handles each one within target response times.
Inputs
- Sample tickets: [paste 20 to 50 ticket subjects or first lines, with personal details removed]
- Teams that handle tickets: [for example billing, technical, logistics, account]
- Current response time targets: [targets by priority, or "none yet"]
- Business hours and time zones: [details]
- Tools: [helpdesk name and whether it supports automation rules]
Output format
- Tag taxonomy: no more than 15 tags, in a table with Tag, Definition, Example ticket from the sample
- Priority matrix:
| Impact \ Urgency | High | Medium | Low |
Each cell shows P1 to P4 with a target first-response time.
- Routing rules: "If tag is X and keyword includes Y, assign to team Z at priority P"
- Edge cases: five ambiguous sample tickets with the correct tag and a reason
- Weekly review routine in 4 steps for keeping tags clean
Check before answering
- Every sample ticket fits at least one tag; list any that do not and propose a fix.
- Tags do not overlap: two agents tagging the same ticket choose the same tag.
- Security issues, payment failures, and legal threats always route to P1 or P2.
- Rules use keywords and fields the listed helpdesk can read, without needing manual review.






