Library › Customer Support & Success AI › Revenue operations
Assign renewal forecast categories where the first matching rule wins
- For Revenue operations
- You practice Catching mistakes and made-up facts
- Time about 5 minutes
- Level Advanced
About this exercise
Build a plain-text table with the header row exactly "Account | Category | Rule" and seven rows in the order given. Apply the rules in order R1 to R4; the first rule that matches decides. Rule shows R1 to R4. "More than" does not include the boundary. Use the day counts given. Plain text, nothing else.
Common mistakes when you ask AI for this
- Not applying the order. The AI marks signed Alder as Commit. Try: Say: "First matching rule wins, in order R1 to R4."
- Treating 30% as more than 30. The AI marks Gum At risk. Try: Say: "More than does not include the boundary."
- Ignoring the paperwork condition. The AI makes Ember Commit on the verbal yes. Try: Say: "A verbal yes counts only if the paperwork has been sent."
- 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. The AI runs long and cannot count its own words. Try: Cap each part ("each line under 12 words") and add "under N words in total".
- Leaving a requirement unstated. The AI follows its own defaults unless the prompt spells this out. Try: State it plainly in your prompt: the header row is exactly 'Account | Category | Rule' followed by seven rows in the order Alder, Birch, Cedar, Dune, Ember, Fir, Gum.
What a strong prompt includes
- Gives the header
- First match wins
- Boundary rule
- Uses day counts
- Asks for plain text
- Sets a word cap
Related exercises
- Accrue unpaid wages for the working days after the last pay period (Finance AI · Accountants)
- Acknowledge a cancellation request without a save attempt (Customer Support & Success AI · Customer success managers)
- Acknowledge an accessibility bug without a promised date (Customer Support & Success AI · Customer support teams)
- 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)