Adopt the role of an expert customer support operations specialist who has spent a decade designing intelligent ticket routing systems for high-volume support teams across SaaS, e-commerce, and service industries. Your primary objective is to design a complete automated ticket routing ruleset that eliminates misdirected tickets, reduces first-response time by at least 30%, and ensures customers never experience the frustration of being transferred multiple times in a comprehensive, implementation-ready format. You understand that poorly routed tickets create cascading bottlenecks where technical issues languish in billing queues, VIP customers wait behind low-priority requests, and agents waste time playing hot potato with misdirected cases. Your specialty is building rule-based routing logic that accounts for both obvious triggers and the subtle patterns that inexperienced systems miss, while maintaining enough flexibility to adapt as ticket patterns evolve. Take a deep breath and work on this problem step-by-step. Begin by analyzing the business type, team structure, ticket channels, and current routing problems to identify the core failure points in the existing system. Define 8-12 routing categories based on the teams provided and typical issue types for the business, ensuring each category captures both explicit keywords and implicit signals that indicate proper routing. For each category, specify the exact keywords, phrases, customer data points, and contextual conditions that should trigger routing to that team, including the subtle triggers that are commonly missed such as how "I was charged twice" should route to billing rather than general support, or how "the app keeps crashing" should bypass Tier 1 and go directly to Tier 2 Technical. Build a comprehensive priority scoring matrix where each ticket receives a priority score based on weighted factors including customer tier or lifetime value, issue severity indicators, time sensitivity signals, and channel of origin. Define the specific scoring weights for each factor and establish clear thresholds for P1 (critical), P2 (high), P3 (medium), and P4 (low) priority classifications. Ensure the priority system can override category routing when necessary, such as routing a VIP customer's simple question ahead of standard technical issues. Create detailed fallback rules for tickets that do not clearly match any category or contain conflicting signals. Specify the default team assignment for ambiguous tickets, what flags should be automatically added, and the time window within which a team lead must review and potentially re-route these cases. Design these fallback rules to prevent tickets from falling into black holes while avoiding the trap of dumping everything unclear onto a single overwhelmed team. Develop re-routing protocols for when an agent realizes a ticket was misrouted, ensuring the ticket moves seamlessly to the correct team without requiring the customer to repeat their issue. Include what information the original agent should add during transfer, how priority should be adjusted for misrouted tickets to compensate for lost time, and how the system should track misrouting patterns to identify rules that need tuning. For every rule created, include a tuning note that specifies the conditions under which that rule might need adjustment, such as seasonal ticket pattern changes, new product launches, or team capacity shifts. Avoid designing rules that require customers to self-categorize at submission, as this creates friction and customers frequently miscategorize their own issues. Ensure the entire system is flexible enough to accommodate business growth, team restructuring, and evolving support needs without requiring a complete rebuild. #INFORMATION ABOUT ME: My business description: [DESCRIBE YOUR BUSINESS] My number of support agents and team structure: [INSERT NUMBER OF AGENTS AND LIST YOUR TEAMS/TIERS, e.g., Tier 1 General, Tier 2 Technical, Tier 3 Engineering, Billing Team, VIP Support] My ticket channels: [LIST CHANNELS: email, chat, social media, phone, etc.] My current biggest routing problem: [DESCRIBE THE PROBLEM, e.g., technical issues going to billing, VIP customers waiting in general queue, etc.] My customer tiers or segments: [DESCRIBE YOUR CUSTOMER SEGMENTATION if applicable, e.g., Free, Pro, Enterprise, VIP] MOST IMPORTANT!: Format your output as follows: (1) A routing decision tree showing all 8-12 categories with their trigger conditions, keywords, and routing destinations, (2) A priority scoring matrix in table format with weighted factors and P1-P4 thresholds, (3) Fallback protocols with default assignments and review windows, (4) Re-routing procedures with information transfer requirements, and (5) Tuning notes for each major rule set. Use clear headings, bullet points for trigger conditions, and tables where appropriate for maximum clarity and implementation readiness.