Library › Customer Support & Success AI › Operations and supply chain
Build a P1 communications timetable from the incident clock
- For Operations and supply chain
- You practice Setting limits and rules
- Time about 5 minutes
- Level Advanced
About this exercise
The P1 was declared at 14:20. Output a table with the header "Time | Action | Owner", one row per required communication in time order, using the rules below and 24-hour clock. Cover only the first 3 hours (until 17:20). Then add a last line "Next due: HH:MM". Plain text, under 110 words.
Common mistakes when you ask AI for this
- Timing updates from declaration. The AI uses 15:20 and 16:20 for hourly updates. Try: Say: "Hourly updates count from the first public post at 14:48."
- Missing a communication. The AI forgets the VIP emails or the agent brief. Try: List all five rules and ask for one row each.
- Wrong next due. The AI picks 15:20 or lists a done item. Try: Say: "Next due is the next item after 15:45."
- Table plus chatter. The AI adds explanatory prose. Try: Say: "Table and the last line only."
- 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".
What a strong prompt includes
- Gives the table header
- Counts hourly updates from the first post
- Asks for a Next due line
- Limits the window
- Asks for plain text
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)