Library › Customer Support & Success AI › Operations and supply chain

Tag five tickets for sentiment and priority separately

  • For Operations and supply chain
  • You practice Setting limits and rules
  • Time about 5 minutes
  • Level Intermediate

About this exercise

Output a table with the header "Ticket | Sentiment | Priority" and five rows. Sentiment is Positive, Neutral or Negative, judged from the tone of the message. Priority comes only from what is broken: P1 if the customer cannot log in or pay, P2 if a feature is broken, otherwise P3. Plain text, under 60 words, nothing else.

Common mistakes when you ask AI for this

  • Letting tone set priority. The AI makes the angry invoice font complaint high priority. Try: Say: "Priority comes only from what is broken."
  • Mixing the two columns. The AI merges sentiment and urgency. Try: Say: "Sentiment from tone, priority from what is broken."
  • Missing the table. The AI writes explanations per ticket. Try: Give the header and say 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

  • Gives the header
  • Separates tone and priority
  • Defines P1 P2 P3
  • Asks for plain text
  • Sets a length limit

Practice this now ↑

Related exercises