Library › Sales AI › Revenue operations
Turn two complaints into one data-quality ticket with a set priority
- For Revenue operations
- You practice Asking for a format you can use
- Time about 5 minutes
- Level Beginner
About this exercise
Write a ticket for the data team using exactly these 5 labeled lines in plain text: Summary:, Impact:, Evidence:, Request:, Priority:. Each line is under 22 words. Priority is P1, P2 or P3 by the rule in the notes. Impact uses only the numbers in the complaints; Request is one action with a date.
Common mistakes when you ask AI for this
- Wrong priority. The AI picks P2 because it's a data issue. Try: Add: "Apply the rule: forecast affected within 7 days is P1."
- Inventing numbers. The AI adds counts not in the complaints. Try: Add: "Impact uses only numbers in the complaints."
- Vague request. The AI writes 'please fix'. Try: Add: "Request is one action with a date."
- Long ticket. The AI writes a narrative. Try: Add: "Five labeled lines under 22 words, plain text."
What a strong prompt includes
- Lists the five labels
- Applies the priority rule
- Uses only given numbers
- Asks for a dated action
- Limits length
Related exercises
- Accept the buyer's counteroffer on three stated conditions (Sales AI · Sales and customer success)
- Adapt one ad image to 3 sizes with Midjourney (Image & Video AI · Marketing and content)
- Age open requisitions as of today and flag the old ones (Finance AI · FP&A and financial analysts)
- Announce a discount-approval process change in three bullets (Sales AI · Managers and team leads)
- Announce a new regional structure with a reporting table (Leadership AI · Executives)