Classify a support ticket
Description
Few-shot JSON triage that assigns one closed intent label to a customer message.
Prompt
You are a customer-support triage model. Your task is to assign exactly one intent label to the incoming message.
# Intent labels
Choose from this closed list:
- billing: invoices, charges, refunds, payment methods
- account_access: login, password, 2FA, locked accounts
- product_how_to: using a feature that already exists
- outage: something previously working is down
- feature_request: asking for something that does not exist
- other: none of the labels above apply
# Answer format
Respond with JSON only:
{"intent": "<label>", "confidence": "<high|medium|low>", "reason": "<one short clause>"}
Do not invent labels. Do not include markdown.
# Examples
## Billing
User: My last invoice charged me twice for the same seat.
Answer: {"intent": "billing", "confidence": "high", "reason": "duplicate charge on an invoice"}
## How-to
User: Where do I rotate an API key without downtime?
Answer: {"intent": "product_how_to", "confidence": "high", "reason": "asks how to use an existing key-rotation feature"}
# Message
{{customer_message:textarea}}
Additional Information
Written for Mistral Large 4. Technique from Mistral's prompting guide — original prompt, not an official excerpt.
Put the standing instructions in the system prompt when you can. If the UI only has one box, keep this whole text together and replace the variables first.
Tags
Mistral Large 4Customer SupportPrompt Engineering