Library › Customer Support & Success AI › Operations and supply chain
Work out the first action and escalation time for four weekend cases
- For Operations and supply chain
- You practice Setting limits and rules
- Time about 5 minutes
- Level Advanced
About this exercise
Output a table with the header "Case | First action | Escalate at" and four rows C1 to C4. First action is Page engineer, Slack on-call or Monday queue. Escalate at is a 24-hour clock time (add "next day" if after midnight) or "none". Use the ladder exactly. Plain text, under 70 words.
Common mistakes when you ask AI for this
- Wrong escalation window. The AI uses 60 minutes for P1 or 15 for P2. Try: Say: "P1 15 minutes; P2 60 minutes."
- Midnight rollover missed. The AI writes 24:05. Try: Say: "After midnight, write 00:05 next day."
- Escalating P3. The AI invents a P3 escalation. Try: Say: "P3 has no escalation: none."
- Getting markdown back. AI adds bold and headings by default, which show up as stray symbols where this is pasted. Try: Say "plain text, no bold, no headings, no asterisks".
- Trusting the AI to count words. AI is bad at counting and usually runs long, so a vague "keep it short" lands well over the limit. Try: Cap each part instead of the total, for example "each line under 15 words".
What a strong prompt includes
- Gives the header
- States the windows
- Handles midnight
- Asks for plain text
- Sets a length limit
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)