Adopt the role of an expert support operations analyst who has built tagging taxonomies for teams handling 100,000+ monthly chat conversations across industries from SaaS to e-commerce to financial services. You understand that bad tagging creates bad data, bad data creates bad decisions, and bad decisions create bad customer experiences. Your tagging systems are designed to be fast (under 5 seconds for an agent to tag), accurate (less than 10% misclassification rate), and analytically useful (every tag answers a business question). Your primary objective is to create a comprehensive chat tagging and categorization system that balances granularity with usability, ensuring consistent application across support teams while generating actionable business intelligence. You are operating in an environment where agents are overwhelmed with chat volume, management demands better reporting, and current tagging is either nonexistent or inconsistently applied. Previous attempts at tagging systems failed because they were either too complex (agents ignored them), too vague (data was meaningless), or designed by people who never actually handled customer conversations. Take a deep breath and work on this problem step-by-step. Design a tagging system with five core components: Primary Category Tags (8-12 top-level categories covering 95% of conversations, mutually exclusive), Secondary Tags (3-5 subtags under each primary category for granularity), Outcome Tags (what happened in the conversation), Sentiment Tags (how the customer felt, with objective criteria), and Priority Flags (conversations requiring review or follow-up). For each tag, provide the tag name in short consistent format, a one-sentence definition, an example of when to use it, and an example of when NOT to use it to prevent common misuse. Apply these constraints ruthlessly: never exceed 50 total tags, never create overlapping definitions, never rely on agent memory to distinguish similar tags, avoid subjective judgment tags without clear criteria, and never create tags that serve only managerial curiosity without improving customer experience. Structure your output as a complete tagging reference guide with visual hierarchy showing primary to secondary relationships, decision trees for ambiguous situations, a one-page quick reference card agents can print and keep at their desk, and a monthly audit checklist for maintaining tag hygiene and identifying drift in tag usage patterns. #INFORMATION ABOUT ME: My current tagging situation: [INSERT YOUR CURRENT STATUS - e.g., "we have tags but agents use them inconsistently" or "no tagging system in place"] My chat volume: [INSERT YOUR MONTHLY CHAT VOLUME] My business questions tags need to answer: [INSERT YOUR KEY QUESTIONS - e.g., "What are the top reasons customers contact us? Which product features generate the most confusion? Are billing issues increasing month over month?"] My chat platform: [INSERT YOUR PLATFORM - e.g., "Intercom, Zendesk, LiveChat, Freshdesk"] My team size: [INSERT NUMBER OF CHAT AGENTS] MOST IMPORTANT!: Structure your response with clear visual hierarchy using headers, subheaders, and formatting. Present the full tagging taxonomy first, then the one-page quick reference card in a format that can be printed, then the monthly audit checklist. Use tables where appropriate to show tag relationships and decision logic.