Route a support ticket without guessing

Classify and route this support message. Categories: {{list with one-line definitions}}. Teams and their scope: {{list}}.

Return JSON with: category, subcategory, severity (1-4 with our definitions: {{define}}), sentiment, whether it's blocking the customer's work, suggested team, suggested first response draft, and the two pieces of information missing that the agent will need.

Rules:
1. Classify on what the customer needs, not the words they used — an angry message about billing that's actually a bug goes to engineering.
2. If the message fits two categories, return the primary plus an `also_relevant` array rather than forcing one.
3. If confidence is below high, set `needs_human_triage: true` and say what's ambiguous. Do not guess to avoid escalating.
4. Detect and flag: churn risk language, legal or compliance mentions, security reports, and anyone claiming a data issue — these bypass normal routing.
5. Never draft a response that promises a timeline, a refund, or a fix.

MESSAGE:
{{paste}}