Library › Customer Support & Success AI › Operations and supply chain

Count real SLA breach causes and separate the false breaches

  • For Operations and supply chain
  • You practice Catching mistakes and made-up facts
  • Time about 5 minutes
  • Level Intermediate

About this exercise

Start with the line "BREACH REVIEW - week 44". Then output a table with the header "Cause | Tickets" listing only real causes, most tickets first, then two last lines "False breaches: N" and "Top cause: X". A breach caused by a pending-status error is a false breach and is not a real cause. Plain text, under 50 words.

Common mistakes when you ask AI for this

  • Counting false breaches as a cause. The AI lists Pending-status error with 2. Try: Say: "Pending-status errors are false breaches, not causes."
  • Wrong order. The AI keeps the ticket order. Try: Say: "Sort by tickets, most first."
  • Missing literal lines. The AI skips the title or last lines. Try: Quote the title line and the two last lines.
  • 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

  • Quotes the title
  • Gives the table header
  • Explains false breaches
  • Asks for plain text
  • Sets a length limit

Practice this now ↑

Related exercises