Library › Customer Support & Success AI › Operations and supply chain
Schedule incident updates with a cadence that changes after an hour
- For Operations and supply chain
- You practice Setting limits and rules
- Time about 5 minutes
- Level Intermediate
About this exercise
Start with the line "UPDATE PLAN - declared 09:00". Then output a table with the header "Update | Time" listing every update, numbered U1, U2 and so on, and a last line "Last update: HH:MM". The cadence is in the rules. Stop at the end time. Plain text, under 50 words.
Common mistakes when you ask AI for this
- Stopping at noon. The AI follows the engineer's guess. Try: Say: "Run to 15:00 regardless."
- Continuing the 30-minute cadence. The AI keeps 30 minutes after 10:00. Try: Say: "After the first hour, hourly."
- Missing the title or last line. The AI skips them. Try: Quote the title 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
- Quotes the title
- Gives the header
- States the cadence
- 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)