Support Ticket Router & Priority Scorer Prompt

For each ticket below, assign:
- Category (bug / how-to / billing / feature-request / abuse).
- Priority (P0/P1/P2/P3) based on impact and affected-user count if inferable.
- Suggested first response (macro or draft).
- Route to (engineering / support / billing / product).
Do not over-prioritize loud-but-low-impact tickets. Flag any ticket that looks like a security report as P0 regardless of wording.

Tickets:
{{tickets}}

Replace the {{fields}} with your own context and tighten the rules to match your domain.