Library › Customer Support & Success AI › IT teams
Build a UTC incident timeline from a chat log with mixed time zones
- For IT teams
- You practice Catching mistakes and made-up facts
- Time about 5 minutes
- Level Advanced
About this exercise
Convert each event to UTC and list them oldest first, one per line in the form "HH:MM UTC - event" (event under 6 words), then a last line "Duration: N minutes" from the alert to resolution. Eastern Standard Time is UTC minus 5 and Pacific Standard Time is UTC minus 8 on Nov 5. Plain text, under 70 words.
Common mistakes when you ask AI for this
- Keeping the log order. The AI lists events as typed. Try: Say: "Oldest first after converting to UTC."
- Wrong offset. The AI adds 4 or 7 hours. Try: Say: "ET is UTC minus 5, PT is UTC minus 8."
- Duration from the customer report. The AI starts at 14:58. Try: Say: "Duration is from the alert to resolution."
- 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
- States the offsets
- Asks for oldest first
- Gives the line form
- Asks for plain text
- Sets a length limit
Related exercises
- Accrue unpaid wages for the working days after the last pay period (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)
- Age a returns queue in business days and flag the ones over the limit (Customer Support & Success AI · Customer support teams)
- Alert sales to a competitor's price change, facts only (Research & AI Search · Product managers)