Analyze·Beginner·Playground·15 min·Updated Sep 30, 2026

Triage support tickets by urgency

Scenario

The support queue has 40 tickets and no priority labels.

Mission

Classify every ticket as Urgent or Normal before the shift handoff.

Start Files

TicketIDDescriptionPriority
TKT-1001typo in email template
TKT-1002question about a report
TKT-1003can't find a setting
TKT-1004typo in email template
TKT-1005payment processing failed
Preview — first 5 rows of support-tickets.csv

Your task

  1. Read each ticket description and classify it Urgent or Normal based on business impact, not tone.
  2. Add a Priority column with your classification.
  3. Count how many tickets land in each priority bucket.

Prompt idea:

Here are 40 support ticket descriptions. Classify each as Urgent or Normal based on business impact (outages, data loss, security, payment failures count as Urgent; everything else is Normal), and give me the count of each.

Check Your Result

How many of the 40 tickets should be classified as Urgent?

Need a hint?

Look for language signaling real business impact — down, affected, breach, data loss — not just urgent-sounding tone.

Reveal Solution

The solution files contain the completed challenge. Review the approach to see if you missed any edge cases.

Related Workflows

WORK WITH LIMINALS

Make AI useful for your team.

Get practical help with AI consulting or ask about training courses for your team.