Ticket Routing Taxonomy Prompt

Help me design a ticket routing taxonomy for our support team.

Business type: [describe your product or service]
Team structure: [list your support teams or specialists — e.g. billing team, technical support, account management]
Most common ticket types: [list the categories of issues you receive]
Current pain points with routing: [what goes wrong today?]

Please create:
1. A ticket category taxonomy (main categories and subcategories)
2. Routing rules: which team or agent type handles each category
3. Priority logic: what factors determine P1 vs P2 vs P3?
4. Escalation triggers: when should a ticket automatically escalate?
5. Suggested tags to make filtering and reporting more useful