What this shows

This example shows why consistent triage matters: a single messy user message becomes a clear, actionable webhook issue for engineers.

Raw feedback

User message

App crashes when I tap my profile pic on iPhone 12 after the update. Happens every time and I lost my draft—super annoying.

Triage output

Structured result

{
    "type": "bug",
    "severity": "high",
    "title": "Crashes tapping profile picture on iPhone 12",
    "summary": "The app crashes reproducibly when tapping the profile picture on iPhone 12 after the latest update.",
    "tags": [
        "iOS",
        "crash",
        "profile",
        "regression"
    ],
    "sentiment": "frustrated",
    "confidence": 0.95
}

Resulting issue

webhook

iOS: Crash on profile picture tap (iPhone 12)

Steps to reproduce: 1) Open app on iPhone 12 2) Go to profile screen 3) Tap profile picture Observed: App crashes immediately; user reports draft data lost. Frequency: every attempt after latest update. App version: unspecified by user; likely v2.3.x. User impact: data loss and blocked workflow. Suggested labels and fields: include device info, crash logs if available, and assign to iOS team.

Live example

Use the API directly

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":"api","category":"mobile-bug","message":"App crashes when I tap my profile pic on iPhone 12 after the update. Happens every time and I lost my draft—super annoying."}'

How it works

Step 1

Send the message

POST the raw feedback to the ingest endpoint.

Step 2

TriageFast classifies it

AI extracts type, severity, title, summary, tags, sentiment, and confidence.

Step 3

Structured output appears in webhook

The formatted issue payload is sent to your webhook for automation or tracking.

Related examples

From raw iOS crash report to webhook issue