Library › Customer Support & Success AI › Executives
Build a year-over-year table that marks better or worse correctly
- For Executives
- You practice Catching mistakes and made-up facts
- Time about 5 minutes
- Level Advanced
About this exercise
Build a year-over-year table with the header row exactly "Metric | Last year | This year | Change | Direction" and four rows. Change is a percent for the first three metrics (whole numbers, with sign) and points for NPS. Direction is Better or Worse; for resolution time, lower is better. Plain text, table only, under 70 words.
Common mistakes when you ask AI for this
- Marking resolution time Better. The analyst says more time per ticket is good. Try: Say: "Fewer hours is better; +25% is Worse."
- Using percent for NPS. The AI writes +15% for NPS. Try: Say: "NPS change in points: +6 points."
- Wrong table. The AI adds a column or notes. Try: Give the exact header; four rows; table only.
- 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 direction rules
- Names the NPS unit
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)