Library › Customer Support & Success AI › Customer support teams

Set component statuses on a status page from engineer notes

  • For Customer support teams
  • You practice Setting limits and rules
  • Time about 5 minutes
  • Level Intermediate

About this exercise

Fill in the status page table with the header row exactly "Component | Status | Since" and five rows. Status is exactly Operational, Degraded or Outage. Outage means fully down; Degraded means working but slow or with some errors; otherwise Operational. Since is the start time, or "-" if Operational. Plain text, table only, under 50 words.

Common mistakes when you ask AI for this

  • Calling the API an outage. The engineer wrote basically down, but 80% of requests succeed. Try: Say: "Outage = fully down. Some errors = Degraded."
  • Marking Billing degraded. The delayed retry job tempts the AI. Try: Say: "If customers are not affected, Operational."
  • Wrong layout or times. The AI adds notes or uses 24-hour times. Try: Give the header, the order and time style.
  • 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 definitions
  • Gives the header

Practice this now ↑

Related exercises