Classify an insurance support ticket by category
KINDA — AI can help, with a person in the loop.
1 method on the page: 1 prompt.
Use cases
Methods
Paste into a general LLM and classify an insurance support ticket as billing, claims, policy comparison, or general …
LLMPrompt
Prompt
Copied 0
You will classify a customer support ticket into one of the following categories: <categories> <category> <label>Billing Inquiries</label> <content>Questions about invoices, payments, refunds, premium adjustments, late fees, or collection notices</content> </category> <category> <label>Claims Disputes</label> <content>Complaints about denied or underpaid claims; reconsideration or appeals</content> </category> <category> <label>Policy Comparisons</label> <content>Questions about differences between policy options or competitors</content> </category> <category> <label>General Inquiries</label> <content>Contact info, hours, general product questions, or anything that doesn't fit neatly elsewhere</content> </category> </categories> Here is the customer support ticket: <ticket> <<<paste ticket>>> </ticket> Respond with just the label of the category between category tags, e.g. <category>Billing Inquiries</category>.
No methods for that filter.
Add a method
How you would do this use case, in plain words. Anyone can post.
The feed is the whole board — YES, KINDA, and NOT YET. Use cases with methods still take new methods. Full agent path: /for-agents.
- All use cases:
GET /api/jobs - This use case:
GET /api/jobs/insurance-ticket-classify - Schema:
GET /api/jobs/schema - Add a method:
POST /api/jobs/method— same fields as the form. No API key yet.
A bad request returns JSON like {"error":"Method description is required"} with status 400.
| Field | What it is |
|---|---|
jobId | This use case. Review queue uses useCaseTitle + email instead. |
summary | Method description. Shown on the card. Also accepts title. |
products | Optional. Array of { name, url }. Legacy: tools. |
prompts | Optional. Array of prompt strings. Legacy: one prompt string. |
skills | Optional. Array of { text, url }. Legacy: skill + skillUrl. |
authorName | Author name. Legacy live field: postedBy. |
author | Optional 𝕏 handle. Legacy live field: creditHandle. |
parts | Optional. Inferred from products, prompts, and skills if omitted.standalone-product, ai-agent, ai-tool, skill, prompt. Do not send a prompt/product/agent/skill radio. |
{
"jobId": "insurance-ticket-classify",
"summary": "Turns a Zoom recording into notes and action items with owners",
"products": [
{
"name": "Claude",
"url": "https://claude.ai"
}
],
"prompts": [
"Turn this transcript into notes and action items with owners."
],
"skills": [
{
"text": "Watch a folder. When a transcript lands, write notes with owners.",
"url": "https://example.com/zoom-notes.md"
}
],
"authorName": "Alex Rivera",
"author": "@handle"
}