Convert support hours to three regions with a next-day rollover

About this exercise

Convert our support hours for customers. Build a table with the header row exactly "Region | Opens | Closes" and four rows: Eastern, Pacific, London, Sydney. Use the offsets in the notes. If a time falls on the next day for the region, add "(next day)" after it. Plain text, table only, under 45 words.

Common mistakes when you ask AI for this

• Using the same hours for every region. Marketing's draft says Sydney is 9 to 6. Try: Say: "Convert from UTC using the given offsets."
• Missing the next-day flag. The AI shows Sydney times without (next day). Try: Say: "Add (next day) when the time falls on the next day."
• Wrong table. The AI adds columns or notes. Try: Give the exact header and the four regions in order.
• 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

• Asks for plain text
• Sets a length limit
• States the offsets
• Asks for next-day flags

Practice this now ↑

Related exercises

• 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)
• Announce a feature sunset with the notice period worked out (Customer Support & Success AI · Customer success managers)
• Announce a feature to admins without hype (Customer Support & Success AI · Customer success managers)