Library › Customer Support & Success AI › Managers and team leads
Flag expansion signals with a three-part rule and exact boundaries
- For Managers and team leads
- You practice Setting limits and rules
- Time about 5 minutes
- Level Advanced
About this exercise
Flag each account as an expansion signal or not. Return one JSON code block with an array of five objects, one per line. Keys: account, signal (true or false), reason (8 words or fewer). Signal is true only if seat use is at least 90%, the sponsor was active in the last 30 days (30 counts), and no P1 is open. Nothing outside the block. At most 7 lines of code.
Common mistakes when you ask AI for this
- Flagging Dune. The AE comment says it is hot, but a P1 is open. Try: Say: "All three conditions must hold. Ignore comments."
- Missing the boundary. Elm is exactly 90% and exactly 30 days. Try: Say: "90% counts; exactly 30 days counts."
- Long reasons or extra text. The AI writes sentences and adds prose. Try: Say: "reason 8 words or fewer; one JSON code block."
- Skipping the code block shape. The AI splits output into several code blocks or none. Try: Say "exactly one code block and nothing else".
- Letting the code sprawl. The AI adds extra lines and comments. Try: Say "at most N lines of code".
What a strong prompt includes
- Asks for one code block
- Caps the code length
- States the three conditions
- Names the keys
Related exercises
- Accept the buyer's counteroffer on three stated conditions (Sales AI · Sales and customer success)
- Accrue goods received but not invoiced at PO price (Finance AI · Accountants)
- 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)
- Add dark mode by overriding your existing CSS variables (Coding AI · Software developers)