Library › Customer Support & Success AI › Operations and supply chain
Triage six tickets into a CSV with stacked priority rules
- For Operations and supply chain
- You practice Setting limits and rules
- Time about 5 minutes
- Level Advanced
About this exercise
Output exactly one CSV code block with the header "ticket,priority,owner" and one row per ticket, in ticket order. Priority, first match wins: P1 if payments fail for all users or customer data is permanently lost; P2 if one account is blocked from a core feature; otherwise P3. Owner: Billing for charge problems, Platform for system-wide outages or permanently lost data, Care for everything else. Write nothing outside the code block.
Common mistakes when you ask AI for this
- Obeying the shouting. The AI makes the URGENT avatar question P1. Try: Say: "Priority comes from the rules, not the tone."
- Treating restored data as lost. The AI sees 'empty folder' and picks P1 and Platform. Try: Say: "Only permanently lost data counts."
- Extra text around the CSV. The AI adds an explanation before and after. Try: Say: "Write nothing outside the code block."
- Wrong header or order. The AI renames columns or sorts by priority. Try: Give the header and say "in ticket order".
What a strong prompt includes
- Gives the exact header
- Says first match wins
- Asks for one code block only
- Notes tone is not a factor
Related exercises
- Accept the buyer's counteroffer on three stated conditions (Sales AI · Sales and customer success)
- Accrue goods received but not invoiced at PO price (Finance AI · Accountants)
- Acknowledge an accessibility bug without a promised date (Customer Support & Success AI · Customer support teams)
- Acknowledge an executive escalation within the hour (Customer Support & Success AI · Executives)
- Add dark mode by overriding your existing CSS variables (Coding AI · Software developers)