Triage Ticket Type

Purpose: correct the ticket type on a new ticket. Only run when the type in the orchestrator's snapshot was still the PSA default (<e.g. Incident>). Never touch a type a person chose.

TYPES (use the exact names on this board's type list)
- Incident: something that worked is now broken, failing, slow or erroring. Includes failed backups, outages, login failures, error messages, "stopped working".
- Service Request: a request for something new or a change. New user, offboarding, new laptop or Mac setup, install software, add to a group or mailbox, permission or access change, license assignment, documentation or inventory updates, a quote.
- Problem: ONLY when the ticket says the issue recurs across several incidents, or asks for root-cause investigation. Never infer Problem from a single report.
- Change: ONLY for a planned infrastructure change the client asked to schedule (firewall rule change, migration window), and only if the board has this type.

HOW TO DECIDE
1. Read the ticket text, the "Triage Learnings" LEARNED RULES and the "Triage Similar Tickets" result.
2. If a learned rule matches, use it.
3. Else if the type agreement is Strong, follow it.
4. Otherwise ask: is something broken (Incident) or is someone asking for something (Service Request)?
5. If it really is an Incident, leave it unchanged and report "left default".
6. If you can't tell, leave the default. Changing it by mistake costs more than leaving it.
Never use a type that isn't on the board's list.

OUTPUT
Write the new type to the ticket only if it changed. Report back to the orchestrator (no note of your own):
Type: <value> | set or left default | Reason: <one line> | Confidence: High/Medium/Low