Resolve service desk tickets faster with Copilot Chat
Use Copilot Chat to stay current on fixes and best practices instead of researching each unfamiliar ticket from scratch.
The support queue has 40 tickets and no priority labels.
Classify every ticket as Urgent or Normal before the shift handoff.
| TicketID | Description | Priority |
|---|---|---|
| TKT-1001 | typo in email template | |
| TKT-1002 | question about a report | |
| TKT-1003 | can't find a setting | |
| TKT-1004 | typo in email template | |
| TKT-1005 | payment processing failed |
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.
How many of the 40 tickets should be classified as Urgent?
Look for language signaling real business impact — down, affected, breach, data loss — not just urgent-sounding tone.
The solution files contain the completed challenge. Review the approach to see if you missed any edge cases.
Use Copilot Chat to stay current on fixes and best practices instead of researching each unfamiliar ticket from scratch.
Get practical help with AI consulting or ask about training courses for your team.