Tally feature requests from support tickets, with ticket IDs

About this exercise

Before roadmap planning, you want to know which features customers actually asked for in last week's support tickets. You want exactly 3 numbered lines for the top 3 requests, each with its count and the ticket IDs, like "Bulk export: 3 (T-102, T-108, T-111)". Count only explicit requests, not bug reports or praise, use only the tickets, plain text, nothing else.

Common mistakes when you ask AI for this

• Mixing bugs with requests. The export crash and late notifications look like feature asks to the AI. Try: Say: "Count only explicit feature requests, not bugs or praise."
• Counting the sales note. The prospect's ask is in your notes, so the AI may bump time tracking up. Try: Add: "Use only the tickets."
• No ticket IDs. Without IDs, you can't pull the tickets into the roadmap doc. Try: Show it: "Format: Feature: N (T-201, T-205)."
• Not saying how many. The AI decides the length itself and usually returns more lines than you can use. Try: Be exact: "exactly 3 numbered lines."
• Getting markdown back. AI defaults to bold labels and headings, which show up as stray symbols in the roadmap doc. Try: Ask for "plain text, no bold, no headings."

What a strong prompt includes

• Asks for counts and IDs
• Excludes bugs and praise
• Says to use only your sources
• Says exactly how many
• 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)