Library › Customer Support & Success AI › Operations and supply chain
Count review signals on five orders and decide hold or ship
- 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 "Order | Signals | Action" and five rows. Signals lists the codes met, such as "S2, S3" or "none". Action is Hold for review if two or more signals are met, otherwise Ship. Then a last line "Hold: O#, O#". Describe orders only by signal codes; never call a customer a fraudster or scammer. Plain text, under 80 words.
Common mistakes when you ask AI for this
- Treating $300 as over $300. The AI counts S2 for O5. Try: Say: "Over $300 means more than $300."
- Calling customers names. The AI labels orders fraudulent. Try: Say: "Describe orders only by signal codes."
- Wrong format. The AI writes a paragraph per order. Try: Give the header and the last-line format.
- 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
- Defines the action rule
- Bans labelling customers
- 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)