Library › Customer Support & Success AI › Operations and supply chain
Write three status posts that do not name a cause too early
- For Operations and supply chain
- You practice Giving the right context
- Time about 5 minutes
- Level Intermediate
About this exercise
Write three status posts on three lines starting "Investigating:", "Identified:" and "Monitoring:", each under 22 words. Only the Identified post may name a cause, and only the confirmed one. The Monitoring post gives the next update time one hour after the failover finished. Plain text.
Common mistakes when you ask AI for this
- Naming the deploy. The AI repeats the unconfirmed 'yesterday's deploy' guess. Try: Say: "Only the confirmed cause; no speculation."
- Cause too early. The AI mentions the database in Investigating. Try: Say: "Investigating names no cause."
- No next update time. The AI says 'we will update soon'. Try: Say: "Give the next update as 12:30."
- 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
- Names the three labels
- Controls when a cause may appear
- Sets the next update time
- Asks for plain text
- Sets a length limit
Related exercises
- 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 input validation to a Java method with exact messages (Coding AI · Software developers)
- Add type hints that still run on Python 3.8 (Coding AI · Software developers)
- Age a returns queue in business days and flag the ones over the limit (Customer Support & Success AI · Customer support teams)