Library › Customer Support & Success AI › IT teams

Convert a customer ticket into a JSON bug record without personal data

  • For IT teams
  • You practice Asking for a format you can use
  • Time about 5 minutes
  • Level Advanced

About this exercise

Return one JSON code block with exactly these keys: "title" (under 60 characters), "severity", "reported_on" (ISO date, year 2026), "steps" (array of exactly 3 short strings) and "customer_contact" (always null). Severity is "high" if checkout or payment is affected, "medium" if there is a workaround, "low" if cosmetic. Do not copy any email, phone number or name into the JSON. Nothing outside the code block.

Common mistakes when you ask AI for this

  • Trusting the CRITICAL subject. The AI sets severity high because the customer shouted. Try: Say: "Apply the severity rules to what actually happens."
  • Copying personal data. The AI includes the name, email or phone in the record. Try: Say: "No names, emails, phone numbers or codes."
  • Loose JSON shape. The AI adds keys, writes the date as Nov 4, or gives 5 steps. Try: List the exact keys and the date format.
  • Chatty extras. The AI explains the record before and after. Try: Say: "Nothing outside the code block."

What a strong prompt includes

  • Lists the exact keys
  • Gives the severity rules
  • Forbids personal data
  • Asks for ISO dates

Practice this now ↑

Related exercises