Use case page

Tag incoming issues with customer tier extracted from email

Stop manually classifying customer tiers in support tickets. TriageFast extracts tier from email text and adds a tier tag to created issues in under 30 seconds.

The problem

The problem

Support teams spend time guessing customer tier from email signatures or account names, delaying routing and SLA handling.

Manual tagging is inconsistent and blocks automation for priority routing to engineering or account management.

The solution

How TriageFast solves it

Send the support email to TriageFast and get a structured triage that includes a customer_tier tag.

curl -s -X POST https://api.triagefast.com/v1/triage -H "Authorization: Bearer $TF_TOKEN" -H "Content-Type: application/json" -d '{"input_type":"email","email_body":"Customer: Acme Corp (Enterprise)\nIssue: Cannot access dashboard","outputs":["github"],"auto_tags":["customer_tier"]}'

Before

  • Agents manually read emails to infer customer tier
  • Tickets routed the same regardless of account value
  • Priority and SLAs set inconsistently

After

  • Customer tier auto-detected from email and added as a tag
  • Issues routed automatically to the right workflow and team
  • Consistent prioritization and SLA enforcement

Result

What developers get back

In under 30s TriageFast returns JSON with fields: type, severity, title, summary, tags, sentiment, and confidence — the tags array will include the detected customer tier (e.g., "enterprise").

Related integrations

FAQ

Can TriageFast extract the customer tier from a plain support email?

Yes — send the email as an input and the tags field will include the detected customer tier.

How quickly will the tier tag appear on created issues?

TriageFast processes triages in under 30 seconds and returns the tags field immediately.

Can I route issues differently by tier?

Yes — use the customer_tier tag to trigger different outputs like GitHub, Linear, Notion, or webhooks.

Start auto-tagging customer tier from email — try 100 triages free

Get an API key, choose an input channel, choose an output channel, and run one test message.