Report the top contact reasons with counts from the tag export

About this exercise

Your support lead wants the top 3 reasons customers contacted you last week for Monday's standup. You want at most 3 bullets in plain text, each a reason with its ticket count and share of the total (like "Login issues: 120 of 600"), using the final export after the duplicate cleanup. Use only the export, and don't add causes or fixes.

Common mistakes when you ask AI for this

• Using the preliminary pull. The first numbers are bigger and come first, so the AI may report them. Try: Say: "Use only the final Nov 2 export."
• No denominator. A count without the total doesn't show how big the problem is. Try: Show it: "Format: Reason: N of 900."
• Adding a cause. The ops note invites the AI to explain late deliveries with an unconfirmed guess. Try: Add: "No causes or fixes."
• Not capping the list. The AI lists everything it finds, so the few points that matter get buried. Try: Say: "at most 3 bullets."
• Getting markdown back. AI defaults to bold labels and headings, which show up as stray symbols in the standup doc. Try: Ask for "plain text, no bold, no headings."

What a strong prompt includes

• Uses the final export
• Asks for counts out of the total
• Rules out causes
• Caps the list
• Asks for plain text

Practice this now ↑

Related exercises

• Accept a job offer and confirm the exact terms (Writing AI · Job seekers)
• Alert sales to a competitor's price change, facts only (Research AI · Product managers)
• Answer a 'where is my order' email with the real new date (Writing AI · Customer support teams)
• Answer a big discount ask with two priced options (Writing AI · Sales and customer success)
• Answer a buyer's HOA questions from the bylaws (Research AI · Real estate agents)