Library › Customer Support & Success AI › Customer support teams

Tag a day of tickets in a table, one primary tag each

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

About this exercise

Return a table with the header row exactly "Ticket | Tag | Urgent" and one row per ticket. Tag by the problem the customer wants fixed first. Use only these tags: Billing, Login, Shipping, Bug, How-to. Urgent is Yes only if the customer cannot log in or cannot pay; otherwise No. Plain text, no extra commentary, under 90 words.

Common mistakes when you ask AI for this

  • Tagging by the last issue. T-801 mentions billing and login; the AI picks login, the later one. Try: Say: "Tag by the problem the customer wants fixed first."
  • Marking everything urgent. The AI marks angry or time-pressed tickets Yes. Try: Define it: "Urgent = Yes only if they cannot log in or cannot pay."
  • Adding a summary or new tags. The AI adds an intro, a 'Payments' tag or notes under the table. Try: Say: "Header exactly Ticket | Tag | Urgent. Only the five tags. Nothing else."
  • 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
  • Gives the header row
  • Limits the tags

Practice this now ↑

Related exercises