ticket_id stringclasses 8
values | priority stringclasses 3
values | ticket_status stringclasses 2
values | csat_score int64 1 5 | classification stringclasses 2
values | action stringclasses 2
values |
|---|---|---|---|---|---|
CS7028 | High | Pending | 5 | CRITICAL | Escalate immediately |
CS7002 | Medium | Pending | 3 | FOLLOW_UP | Assign for follow-up |
CS7007 | Medium | Pending | 2 | FOLLOW_UP | Assign for follow-up |
CS7010 | Medium | Pending | 5 | FOLLOW_UP | Assign for follow-up |
CS7014 | Medium | Pending | 5 | FOLLOW_UP | Assign for follow-up |
CS7019 | High | Resolved | 1 | FOLLOW_UP | Assign for follow-up |
CS7020 | Low | Pending | 5 | FOLLOW_UP | Assign for follow-up |
CS7029 | Medium | Resolved | 3 | FOLLOW_UP | Assign for follow-up |
YAML Metadata Warning:empty or missing yaml metadata in repo card
Check out the documentation for more information.
Escalation Registry
This dataset tracks support ticket escalations for the support team.
Categories
- CRITICAL: High priority + Pending status - escalate immediately
- FOLLOW_UP: CSAT below 4 OR Pending status (non-critical) - assign for follow-up
- OK: All other tickets
Files
escalations.json- the escalation registry data
- Downloads last month
- 17