Raw feedback
User message
I was charged twice for my plan this month — my card shows two $19 charges. I need a refund ASAP; support ticket #4521 didn't help.
Demonstrates converting a routed support email about billing into a Linear issue. Shows fields like severity, title, summary, tags, sentiment, and confidence.
What this shows
This example helps developers map messy billing reports from a support tool into structured triage data and automatically create a Linear issue.
Raw feedback
I was charged twice for my plan this month — my card shows two $19 charges. I need a refund ASAP; support ticket #4521 didn't help.
Triage output
{
"type": "billing",
"severity": "high",
"title": "Duplicate monthly charge on account",
"summary": "Customer reports being charged twice for the monthly plan and requests a refund.",
"tags": [
"billing",
"refund",
"duplicate_charge",
"payment"
],
"sentiment": "frustrated",
"confidence": 0.95
}Resulting issue
Duplicate monthly charge on account
Customer reports two $19 charges this month; support ticket #4521 did not resolve. Request: verify charges, refund the duplicate, and confirm back to customer. Source: routed support message.
Live example
Send the same raw message to TriageFast and get the structured result back through the normal ingest endpoint.
curl -X POST https://triagefast.app/api/v1/ingest -H "Authorization: Bearer tf_live_xxxx" -H "Content-Type: application/json" -d '{"source":"support_tool","context":"routed_workflow","raw_feedback":"I was charged twice for my plan this month — my card shows two $19 charges. I need a refund ASAP; support ticket #4521 didn't help."}'How it works
Step 1
Post the routed support message to the ingest endpoint.
Step 2
AI extracts type, severity, title, summary, tags, sentiment, and confidence in under 30s.
Step 3
TriageFast creates a Linear issue with the mapped fields and labels.
Related examples
Free plan includes 100 triages per month. No credit card required.