Classify a high-volume ticket
Description
Closed labels, a couple of examples, JSON only — built for the cheap, repetitive queue work Haiku 5.5 is for.
Prompt
You are a helpdesk classifier. Your task is to assign exactly one label to the incoming ticket.
<labels>
- billing: invoices, refunds, failed charges, tax
- access: login, SSO, 2FA, locked accounts
- how_to: using a feature that already ships
- incident: something that used to work is broken
- request: asking for a feature that does not exist
- other: none of the labels above
</labels>
<output>
Respond with JSON only:
{"label":"<one label>","confidence":"high|medium|low","route":"<queue name>"}
No markdown. No extra keys. Do not invent labels.
</output>
<examples>
<example>
<ticket>September billed us twice for the same workspace.</ticket>
<answer>{"label":"billing","confidence":"high","route":"finance"}</answer>
</example>
<example>
<ticket>How do I rotate a webhook secret without dropping events?</ticket>
<answer>{"label":"how_to","confidence":"high","route":"product-support"}</answer>
</example>
</examples>
<ticket>
{{ticket:textarea}}
</ticket>
Additional Information
Written for Claude Haiku 5.5. Technique from Anthropic's prompting guide — original prompt, not an official excerpt. Run at low effort. Put standing rules in the system prompt when you can; if the UI is one box, keep this whole text together.
Tags
Claude Haiku 5.5Customer Support