Raw feedback
User message
I was charged twice this morning for my Pro subscription (order #1234). My account still shows as unpaid and I can't access Pro features. Please refund one charge and restore access.
Turn messy support emails about billing into a prioritized GitHub issue automatically. Demonstrates AI field extraction and routing to GitHub.
What this shows
Developers can skip manual categorization: TriageFast extracts billing details from an email and opens a focused GitHub issue so engineers can resolve charge and access problems quickly.
Raw feedback
I was charged twice this morning for my Pro subscription (order #1234). My account still shows as unpaid and I can't access Pro features. Please refund one charge and restore access.
Triage output
{
"type": "billing",
"severity": "high",
"title": "Double charge prevents Pro access",
"summary": "User was charged twice and lost access to paid features.",
"tags": [
"billing",
"payment-failure",
"refund",
"account-access"
],
"sentiment": "frustrated",
"confidence": 0.95
}Resulting issue
Double charge prevents Pro access
Summary: Customer reports being charged twice for Pro and unable to access paid features. Raw message: "I was charged twice this morning for my Pro subscription (order #1234). My account still shows as unpaid and I can't access Pro features. Please refund one charge and restore access." Steps to reproduce / triage notes: - Verify payments for order #1234 in payments dashboard and gateway logs. - Check account entitlement and subscription status tied to the customer's email. Expected: Single successful charge and Pro access granted. Actual: Two charges recorded and user locked out. Recommended actions: 1) Investigate duplicate transaction and issue refund if duplicate confirmed. 2) Restore Pro access and confirm with customer. 3) Add follow-up to payments logs and mark incident for billing review.
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 <TOKEN>'
How it works
Step 1
Route Payment Failure Email To Github Example feedback into TriageFast through email, API, or workflow forwarding.
Step 2
Type, severity, summary, tags, sentiment, and confidence are generated automatically.
Step 3
Structured output is routed into GitHub without manual rewriting.
Related examples
Free plan includes 100 triages per month. No credit card required.