JSON schema: classify a support ticket
# JSON schema: classify a support ticket code: q0zn5w | type: schema | language: en | licence: MIT | version: v1 description: JSON Schema to classify a support ticket: category, priority, sentiment, one-sentence summary and next action for the support team. page: https://contextetech.com/en/schemas/classify-support-ticket-q0zn5w mcp: connect https://contextetech.com/mcp then call load_resource with code "q0zn5w" (or ask "load q0zn5w") json: https://contextetech.com/api/resources/contextetech--classify-support-ticket python: pip install contexte && contexte get q0zn5w citation (required by the licence): contextetech. (2026). JSON schema: classify a support ticket (Version 1) [Output schema]. Contexte Tech. https://contextetech.com/en/schemas/classify-support-ticket-q0zn5w
JSON Schema to classify a support ticket: category, priority, sentiment, one-sentence summary and next action for the support team.
Read the customer's message and classify it. Priority is high when the customer is blocked or threatens to cancel.
JSON Schema
{
"type": "object",
"required": [
"category",
"priority",
"summary"
],
"properties": {
"summary": {
"type": "string",
"description": "One sentence"
},
"category": {
"enum": [
"billing",
"technical",
"shipping",
"account",
"other"
],
"type": "string"
},
"priority": {
"enum": [
"low",
"normal",
"high"
],
"type": "string"
},
"sentiment": {
"enum": [
"positive",
"neutral",
"negative"
],
"type": "string"
},
"next_action": {
"type": "string",
"description": "What the support team should do"
}
}
}Output example
{
"category": "shipping",
"priority": "high",
"sentiment": "negative",
"summary": "Package marked as delivered but never received.",
"next_action": "Open a carrier claim and offer a replacement."
}- Identifier
- contextetech--classify-support-ticket
- File
- classify-support-ticket.schema.json
- Format
- JSON (application/json)
- Size
- 723 bytes
- Encoding
- UTF-8
- Estimated tokens
- ≈ 201
- Commercial use
- Allowed
- Personal data
- None
- Version
- 1.0
- Published on
- October 2, 2026 at 9:54 PM
- Updated on
- October 16, 2026 at 11:19 PM
- Storage
- in database
Statistics
Likes : 0 · Comments : 0
Click a counter to show or hide it, hover the chart for details. One view per visitor per day, bots excluded; counting started on 30 September 2026.
Estimated cost
- Input tokens per call
- ≈ 410
| Model | Per call | Per month |
|---|---|---|
| GPT-6 Luna · OpenAIbest price | €0.00004 | €0.04 |
| DeepSeek Flash · DeepSeek | €0.00011 | €0.11 |
| Mistral Large · Mistral AI | €0.00018 | €0.18 |
| DeepSeek V4 Pro · DeepSeek | €0.00048 | €0.48 |
| GPT-6 Sol · OpenAI | €0.00072 | €0.72 |
| Claude Sonnet 5.5 · Anthropic | €0.00072 | €0.72 |
| Claude Opus 5.5 · Anthropic | €0.00144 | €1.44 |
| Self-hosted open-source model (Ollama, vLLM) | €0 in API fees (server cost only) | |
Input cost only, excluding the model's answer. Providers' public standard prices (Mistral AI, DeepSeek, OpenAI, Anthropic) converted from USD to euros at the ECB rate of October 13, 2026. Estimate: 1 token ≈ 3.6 characters.
Common to all 3 regions
Created by the author, no outside source.
Commercial use allowed · credit the author · changes allowed.
Text or data only: no access to files, network or commands.
Hosted in France (Scaleway, Paris). No transfer outside the EU.
European Union · 5/5
No personal data.
No training data: no summary required.
United States · 5/5
No personal data.
No training data: no documentation to publish.
China · 5/5
No personal data.
No training data; AI-generated content published in China must be labelled (2025).
Indicative summary as of 30/09/2026, not a legal certification. Method and sources →
Content quality
The detailed criteria are for members.
Every criterion, the points removed and a tip to fix each one.
Content analysis
The detailed criteria are for members.
Every criterion, the points removed and a tip to fix each one.
Computed from the content of the resource, by rules, without AI. The score is in the Quality tab.
MCP contexte
https://contextetech.com/mcp
load q0zn5w
Add the URL as a connector in your AI apps' settings, then send the request above.
API
import json, urllib.request url = "https://contextetech.com/api/resources/contextetech--classify-support-ticket" fiche = json.load(urllib.request.urlopen(url)) print(fiche["title"] or fiche["name"])
classify-support-ticket.schema.json
{
"type": "object",
"required": [
"category",
"priority",
"summary"
],
"properties": {
"summary": {
"type": "string",
"description": "One sentence"
},
"category": {
"enum": [
"billing",
"technical",
"shipping",
"account",
"other"
],
"type": "string"
},
"priority": {
"enum": [
"low",
"normal",
"high"
],
"type": "string"
},
"sentiment": {
"enum": [
"positive",
"neutral",
"negative"
],
"type": "string"
},
"next_action": {
"type": "string",
"description": "What the support team should do"
}
}
}Anthropic API (Python)
import json, anthropic
schema = json.load(open("classify-support-ticket.schema.json"))
client = anthropic.Anthropic()
resp = client.messages.create(model="claude-sonnet-5", max_tokens=1024,
tools=[{"name": "extraire", "description": "Renvoie les données extraites", "input_schema": schema}],
tool_choice={"type": "tool", "name": "extraire"},
messages=[{"role": "user", "content": "your input here"}])
print(resp.content[0].input)OpenAI format (response_format)
{
"type": "json_schema",
"json_schema": {
"name": "classify-support-ticket",
"schema": {
"type": "object",
"required": [
"category",
"priority",
"summary"
],
"properties": {
"summary": {
"type": "string",
"description": "One sentence"
},
"category": {
"enum": [
"billing",
"technical",
"shipping",
"account",
"other"
],
"type": "string"
},
"priority": {
"enum": [
"low",
"normal",
"high"
],
"type": "string"
},
"sentiment": {
"enum": [
"positive",
"neutral",
"negative"
],
"type": "string"
},
"next_action": {
"type": "string",
"description": "What the support team should do"
}
}
},
"strict": true
}
}
Community
No comments yet. Share your feedback, it will help the next person.